[{"data":1,"prerenderedAt":1094},["ShallowReactive",2],{"project-line-rag-saas":3,"related-line-rag-saas":397,"project-nav-line-rag-saas":967},{"id":4,"title":5,"body":6,"caseDescription":369,"caseStudy":370,"caseType":369,"category":371,"completedDate":372,"description":346,"extension":373,"featured":374,"links":375,"meta":376,"navigation":374,"order":377,"path":378,"projectType":379,"published":374,"seo":380,"shortDesc":381,"stem":382,"tags":383,"techStack":389,"thumbnail":395,"__hash__":396},"projects/projects/line-rag-saas.md","RAG 智慧客服知識庫 SaaS",{"type":7,"value":8,"toc":345},"minimark",[9,13,21,28,31,35,38,41,45,67,70,74,92,99,103,117,123,129,132,176,179,217,220,224,227,231,234,238,241,245,248,252,255,258,275,278,281,298,301,324],[10,11,12],"h2",{"id":12},"專案簡介",[14,15,16,17,20],"p",{},"這是一套給台灣企業使用的 ",[18,19,5],"strong",{},"。店家只要把既有的 PDF、DOCX、TXT 文件上傳到後台，系統就會自動整理成 AI 看得懂的知識庫；顧客則直接在通訊軟體上發問，AI 會根據店家自己的文件內容，給出繁體中文回答。",[14,22,23,24,27],{},"目前第一個上線的通路是 ",[18,25,26],{},"LINE","，但系統從一開始就把「聊天通路」和「知識庫大腦」分開設計，之後如果客戶有需要，也能擴充到 IG 私訊等其他平台，不會被綁死在單一通路上。",[14,29,30],{},"如果 AI 找不到足夠可靠的答案，不會硬掰，而是引導顧客確認是否需要轉接真人客服，讓自動回覆和真人服務可以順暢接手。",[10,32,34],{"id":33},"為什麼做這個專案","為什麼做這個專案？",[14,36,37],{},"很多企業的客服知識分散在官網、PDF、內部文件和員工經驗裡，客人一問問題，客服就要重複翻資料、複製貼上，忙的時候還容易漏回訊息。",[14,39,40],{},"我想做的是一套更貼近台灣使用情境的系統：不用顧客額外下載 App，也不用店家從零打造客服平台，而是接在顧客最熟悉的通路上（目前是 LINE），把既有文件變成能即時回答的客服助手，未來也能隨業務成長延伸到其他社群平台。",[10,42,44],{"id":43},"可以幫企業解決什麼問題","可以幫企業解決什麼問題？",[46,47,48,52,55,58,61,64],"ul",{},[49,50,51],"li",{},"把常見問題交給 AI 先回覆，減少客服人員重複作業",[49,53,54],{},"回答只根據企業自己的文件內容，不會憑空亂答",[49,56,57],{},"客服人員可在後台查看對話紀錄、AI 引用的來源與待轉接案件",[49,59,60],{},"一套系統可以同時服務多個企業客戶，彼此資料完全獨立",[49,62,63],{},"文件更新後可以重新整理知識庫，內容保持一致",[49,65,66],{},"未來要擴充到 IG 等其他通路時，不需要重做整套知識庫系統",[10,68,69],{"id":69},"使用流程",[71,72,73],"h3",{"id":73},"企業後台",[75,76,77,80,83,86,89],"ol",{},[49,78,79],{},"管理員登入後台並建立商家資料",[49,81,82],{},"上傳 PDF、DOCX 或 TXT 文件",[49,84,85],{},"系統自動整理文件，建立可供 AI 檢索的知識庫",[49,87,88],{},"後台可查看文件狀態、對話紀錄、客服轉接與 LINE 設定",[49,90,91],{},"平台管理員可管理各企業客戶的用量與帳號狀態",[14,93,94],{},[95,96],"img",{"alt":97,"src":98},"文件管理","/images/rag2.png",[71,100,102],{"id":101},"顧客端目前為-line","顧客端（目前為 LINE）",[75,104,105,108,111,114],{},[49,106,107],{},"顧客在 LINE 官方帳號中提出問題",[49,109,110],{},"AI 從企業自己的知識庫中找出相關內容",[49,112,113],{},"產生繁體中文回答給顧客",[49,115,116],{},"如果內容不夠可靠，或顧客主動要求，會引導轉接真人客服",[118,119,120],"blockquote",{},[14,121,122],{},"目前只串接 LINE，但這一層是獨立設計的，未來可以視需求擴充到 IG 私訊等其他管道，共用同一套知識庫和轉接邏輯。",[14,124,125],{},[95,126],{"alt":127,"src":128},"使用者畫面","/images/rag3.jpeg",[10,130,131],{"id":131},"主要功能",[46,133,134,140,146,152,158,164,170],{},[49,135,136,139],{},[18,137,138],{},"文件知識庫","：支援上傳、整理、更新與刪除文件，知識庫隨時保持最新",[49,141,142,145],{},[18,143,144],{},"智慧客服回覆","：接收顧客訊息，AI 根據文件內容產生回答",[49,147,148,151],{},[18,149,150],{},"回答有憑有據","：每個回答都會保留引用的文件來源，方便後台檢視",[49,153,154,157],{},[18,155,156],{},"真人客服轉接","：AI 沒把握或顧客要求時，引導確認後轉接真人",[49,159,160,163],{},[18,161,162],{},"客服工作台","：可查看對話紀錄、手動回覆、處理轉接案件",[49,165,166,169],{},[18,167,168],{},"多租戶架構","：多個企業共用同一套平台，資料完全彼此隔離",[49,171,172,175],{},[18,173,174],{},"營運管理","：用量限制、發送額度、操作紀錄、帳號啟用與停權",[10,177,178],{"id":178},"系統特色",[75,180,181,187,193,199,205,211],{},[49,182,183,186],{},[18,184,185],{},"從 LINE 起步，通路可擴充","：先符合台灣客戶最熟悉的使用習慣，未來可加入 IG 等其他社群平台",[49,188,189,192],{},[18,190,191],{},"文件驅動回答","：AI 只根據企業自己的內容回答，降低亂答風險",[49,194,195,198],{},[18,196,197],{},"多租戶 SaaS 架構","：同一套平台可服務多個商家，資料與權限互不干擾",[49,200,201,204],{},[18,202,203],{},"安全優先","：帳號權限、資料隔離、用量控管都納入設計",[49,206,207,210],{},[18,208,209],{},"可營運後台","：不只是聊天機器人，還包含文件、客服、設定與帳號管理",[49,212,213,216],{},[18,214,215],{},"穩定部署","：採用雲端服務架設，維運與更新都較有彈性",[10,218,219],{"id":219},"開發挑戰",[71,221,223],{"id":222},"_1-避免-ai-憑空回答","1. 避免 AI 憑空回答",[14,225,226],{},"客服系統不能只求「看起來會回答」，答錯時更要有保護機制。系統會檢查找到的資料是否夠可靠，內容不足時就走安全回覆或轉真人，而不是讓 AI 自由發揮。",[71,228,230],{"id":229},"_2-多租戶資料要完全隔離","2. 多租戶資料要完全隔離",[14,232,233],{},"這類 SaaS 最怕的風險是 A 客戶看到 B 客戶的文件或對話。系統在每一層查詢和檢索邏輯裡，都明確依照企業身分做資料區隔。",[71,235,237],{"id":236},"_3-通路串接的穩定性","3. 通路串接的穩定性",[14,239,240],{},"LINE 訊息需要快速、安全地處理，並避免因為重試而重複回覆或扣錯額度。這一層特別獨立出來設計，未來要加其他通路時，只需要新增對應的串接方式即可。",[71,242,244],{"id":243},"_4-文件更新後知識庫要跟著同步","4. 文件更新後知識庫要跟著同步",[14,246,247],{},"文件被替換、更新或刪除時，知識庫內容也要同步清理更新，避免顧客拿到過期或錯誤的資訊。",[71,249,251],{"id":250},"_5-後台要能真的拿來營運","5. 後台要能真的拿來營運",[14,253,254],{},"客服後台不是單純展示資料的 dashboard，而是要能處理文件管理、對話查看、轉接、帳號設定等日常營運工作，讓非技術人員也能上手操作。",[10,256,257],{"id":257},"成果與收穫",[46,259,260,263,266,269,272],{},[49,261,262],{},"完成一套可作為 SaaS 基礎的智慧客服平台，目前以 LINE 為第一個上線通路",[49,264,265],{},"建立從文件整理、AI 檢索、回答到真人轉接的完整服務流程",[49,267,268],{},"將多租戶資料隔離、用量控管、安全防護都納入產品設計",[49,270,271],{},"系統架構拆分清楚，方便未來擴充其他通路而不用重寫核心邏輯",[49,273,274],{},"更熟悉 AI 產品中「回答品質、資料安全、營運流程」三者之間的取捨",[10,276,277],{"id":277},"適用對象",[14,279,280],{},"這套系統適合：",[46,282,283,286,289,292,295],{},[49,284,285],{},"有大量 FAQ、產品文件或服務規範的企業",[49,287,288],{},"需要客服自動化的電商、零售、教育、醫療、美業與服務業",[49,290,291],{},"想先用 AI 處理常見問題，再把複雜問題交給真人的團隊",[49,293,294],{},"需要多品牌、多分店或多客戶資料隔離的 SaaS 情境",[49,296,297],{},"未來希望從 LINE 擴充到 IG 等其他社群通路的長期客戶",[10,299,300],{"id":300},"可客製方向",[46,302,303,306,309,312,315,318,321],{},[49,304,305],{},"LINE 官方帳號流程與訊息樣式設計",[49,307,308],{},"擴充 IG 私訊或其他社群平台的串接",[49,310,311],{},"客服後台品牌風格與權限角色",[49,313,314],{},"文件格式、知識庫分類與審核流程",[49,316,317],{},"回答語氣、禁答規則與真人轉接條件",[49,319,320],{},"CRM、訂單、會員或內部系統串接",[49,322,323],{},"租戶方案、用量計費與告警規則",[118,325,326,331,334],{},[14,327,328],{},[18,329,330],{},"聯絡方式",[14,332,333],{},"如果你想把 LINE、IG 等社群客服、文件知識庫或 AI 問答整合到自己的業務流程，歡迎聯絡我討論。",[14,335,336,339,340],{},[18,337,338],{},"Email:"," ",[341,342,344],"a",{"href":343},"mailto:contact@spencerku.me","contact@spencerku.me",{"title":346,"searchDepth":347,"depth":347,"links":348},"",2,[349,350,351,352,357,358,359,366,367,368],{"id":12,"depth":347,"text":12},{"id":33,"depth":347,"text":34},{"id":43,"depth":347,"text":44},{"id":69,"depth":347,"text":69,"children":353},[354,356],{"id":73,"depth":355,"text":73},3,{"id":101,"depth":355,"text":102},{"id":131,"depth":347,"text":131},{"id":178,"depth":347,"text":178},{"id":219,"depth":347,"text":219,"children":360},[361,362,363,364,365],{"id":222,"depth":355,"text":223},{"id":229,"depth":355,"text":230},{"id":236,"depth":355,"text":237},{"id":243,"depth":355,"text":244},{"id":250,"depth":355,"text":251},{"id":257,"depth":347,"text":257},{"id":277,"depth":347,"text":277},{"id":300,"depth":347,"text":300},null,false,"網頁應用","2026.07","md",true,{"demo":369,"github":369,"figma":369},{},6,"/projects/line-rag-saas","SaaS 產品開發",{"title":5,"description":346},"讓企業把文件變成智慧客服，目前主打 LINE，未來可擴充至 IG 等平台，支援多租戶與真人轉接","projects/line-rag-saas",[384,385,386,387,388],"LINE Bot","RAG","SaaS","多通路客服","AI 客服",[390,391,392,393,394],"Next.js + React","Supabase","Gemini AI","LINE Messaging API","Cloudflare Pages","/images/rag1.png","x1FIQVaBD2kdDRItg_5V9IOLwLkLDRqFTBI35x9I4_c",[398,592],{"id":399,"title":400,"body":401,"caseDescription":569,"caseStudy":374,"caseType":570,"category":371,"completedDate":571,"description":346,"extension":373,"featured":374,"links":572,"meta":573,"navigation":374,"order":574,"path":575,"projectType":576,"published":374,"seo":577,"shortDesc":578,"stem":579,"tags":580,"techStack":586,"thumbnail":416,"__hash__":591},"projects/projects/line-ordering-system.md","LINE 點餐系統",{"type":7,"value":402,"toc":559},[403,405,408,411,417,421,432,436,450,453,464,470,474,491,495,527,529,540,542],[10,404,12],{"id":12},[14,406,407],{},"這是一套給餐飲店使用的 LINE 點餐系統。顧客不需要下載新 App，只要打開 LINE 就能點餐；店家則可以在後台即時看訂單、改菜單、查營運數據。",[14,409,410],{},"我希望解決的是「接單混亂、資訊不同步、人工確認太花時間」這三個最常見問題。",[14,412,413],{},[95,414],{"alt":415,"src":416},"LINE 點餐前台","/images/line-ordering-1.png",[10,418,420],{"id":419},"這套系統適合誰","這套系統適合誰？",[46,422,423,426,429],{},[49,424,425],{},"便當店、自助餐、小吃店",[49,427,428],{},"飲料店、甜點店、咖啡店",[49,430,431],{},"想從電話接單改成線上接單的店家",[10,433,435],{"id":434},"可以幫店家解決什麼問題","可以幫店家解決什麼問題？",[46,437,438,441,444,447],{},[49,439,440],{},"尖峰時段不再靠人工抄單，降低漏單機率",[49,442,443],{},"顧客可自己查訂單狀態，減少重複詢問",[49,445,446],{},"菜單可即時更新，不用一直回覆「今天賣完了嗎」",[49,448,449],{},"每日營收與熱銷品一眼看懂，做決策更快",[10,451,452],{"id":452},"顧客使用流程",[75,454,455,458,461],{},[49,456,457],{},"在 LINE 開啟點餐頁面",[49,459,460],{},"選餐、加入購物車、填寫取餐資訊",[49,462,463],{},"送出訂單後，隨時查看最新狀態",[14,465,466],{},[95,467],{"alt":468,"src":469},"店家後台訂單看板","/images/line-ordering-2.png",[10,471,473],{"id":472},"店家後台可以做什麼","店家後台可以做什麼？",[46,475,476,479,482,485,488],{},[49,477,478],{},"用看板方式管理訂單進度（待確認、製作中、待取餐）",[49,480,481],{},"快速搜尋訂單與顧客電話",[49,483,484],{},"新增/修改菜單、調整價格、上傳餐點圖片",[49,486,487],{},"一鍵切換「上架中 / 已賣完 / 已下架」",[49,489,490],{},"查看營收趨勢與熱銷品排行",[10,492,494],{"id":493},"這套系統的實用特色白話版","這套系統的實用特色（白話版）",[46,496,497,503,509,515,521],{},[49,498,499,502],{},[18,500,501],{},"不怕重複送出","：顧客網路不穩重按，也不會重複出單",[49,504,505,508],{},[18,506,507],{},"尖峰更穩定","：高峰時段仍能維持有序接單",[49,510,511,514],{},[18,512,513],{},"狀態清楚","：店家與顧客看到同一份訂單進度",[49,516,517,520],{},[18,518,519],{},"通知可補發","：若通知一時失敗，系統會自動再試",[49,522,523,526],{},[18,524,525],{},"權限分工","：老闆和店員看到的功能不同，避免誤操作",[10,528,257],{"id":257},[46,530,531,534,537],{},[49,532,533],{},"完成「顧客點餐 + 店家管理」的可運作 MVP",[49,535,536],{},"將常見人工流程（接單、改單、查單）整理成標準化操作",[49,538,539],{},"建立可擴充的基礎，未來可再加會員、優惠、外送範圍與金流",[10,541,300],{"id":300},[46,543,544,547,550,553,556],{},[49,545,546],{},"品牌色系與頁面風格",[49,548,549],{},"外送規則與服務範圍",[49,551,552],{},"會員機制與優惠活動",[49,554,555],{},"多分店管理",[49,557,558],{},"串接第三方支付",{"title":346,"searchDepth":347,"depth":347,"links":560},[561,562,563,564,565,566,567,568],{"id":12,"depth":347,"text":12},{"id":419,"depth":347,"text":420},{"id":434,"depth":347,"text":435},{"id":452,"depth":347,"text":452},{"id":472,"depth":347,"text":473},{"id":493,"depth":347,"text":494},{"id":257,"depth":347,"text":257},{"id":300,"depth":347,"text":300},"將菜單、訂單與顧客操作整合到 LINE 使用情境，建立完整的點餐流程。","點餐流程 / 管理後台","2026.04",{"demo":369,"github":369,"figma":369},{},5,"/projects/line-ordering-system","個人專案",{"title":400,"description":346},"讓顧客在 LINE 就能快速點餐，店家用同一套後台管理訂單與菜單","projects/line-ordering-system",[581,582,583,584,585],"LINE 點餐","餐飲數位化","訂單管理","菜單管理","營運報表",[587,588,391,589,590],"LINE LIFF","React + TypeScript","Tailwind CSS","Recharts","CA1L7YAy-GABA5FYGOc5eTefuEbfpBRki-MhQH0M_i8",{"id":593,"title":594,"body":595,"caseDescription":948,"caseStudy":374,"caseType":949,"category":371,"completedDate":950,"description":346,"extension":373,"featured":374,"links":951,"meta":952,"navigation":374,"order":347,"path":953,"projectType":576,"published":374,"seo":954,"shortDesc":955,"stem":956,"tags":957,"techStack":961,"thumbnail":713,"__hash__":966},"projects/projects/line-reservation-system.md","LINE 預約管理系統",{"type":7,"value":596,"toc":934},[597,599,606,609,623,625,628,630,634,654,660,664,708,714,720,722,754,757,760,792,795,798,830,833,836,868,871,873,876,893,896,916],[10,598,12],{"id":12},[14,600,601,602,605],{},"這是一個完整的預約管理系統，讓小型店家可以透過 ",[18,603,604],{},"LINE 聊天機器人"," 提供預約服務。客戶只要加 LINE 好友，就能在對話中輕鬆完成預約，不需要下載額外的 App 或註冊帳號。",[14,607,608],{},"系統分為兩個部分：",[46,610,611,617],{},[49,612,613,616],{},[18,614,615],{},"LINE Bot（給客戶用）","：透過對話完成預約、查詢、取消",[49,618,619,622],{},[18,620,621],{},"管理後台（給店家用）","：視覺化日曆、客戶管理、預約統計",[10,624,34],{"id":33},[14,626,627],{},"看到很多小店家還在用 Excel 表格或手寫記錄預約，不僅容易出錯，客戶也要打電話或傳訊息才能預約。而 LINE 是台灣最普及的通訊軟體，幾乎人人都有，所以決定開發一個結合 LINE 的預約系統，讓預約變得更簡單。",[10,629,131],{"id":131},[71,631,633],{"id":632},"給客戶的功能line-bot","給客戶的功能（LINE Bot）",[46,635,636,642,648],{},[49,637,638,641],{},[18,639,640],{},"簡單預約","：在 LINE 對話中選擇服務和時間就完成預約",[49,643,644,647],{},[18,645,646],{},"查詢預約","：隨時查看自己的預約記錄",[49,649,650,653],{},[18,651,652],{},"取消預約","：不能來的話可以直接在 LINE 取消",[14,655,656],{},[95,657],{"alt":658,"src":659},"LINE Bot 預約介面","/images/line-reservation-1.png",[71,661,663],{"id":662},"給店家的功能管理後台","給店家的功能（管理後台）",[46,665,666,672,678,684,690,696,702],{},[49,667,668,671],{},[18,669,670],{},"日曆檢視","：一眼看清所有預約，可以切換日、週、月檢視",[49,673,674,677],{},[18,675,676],{},"預約管理","：手動確定、取消預約",[49,679,680,683],{},[18,681,682],{},"客戶資料","：查看每位客戶的預約歷史和聯絡資訊",[49,685,686,689],{},[18,687,688],{},"服務設定","：管理提供的服務項目和時間長度",[49,691,692,695],{},[18,693,694],{},"時段管理","：設定哪些時段開放預約",[49,697,698,701],{},[18,699,700],{},"報到功能","：客戶到店時可以快速打卡報到",[49,703,704,707],{},[18,705,706],{},"數據統計","：查看預約數量、客戶人數等統計資料",[14,709,710],{},[95,711],{"alt":712,"src":713},"管理後台dashborad","/images/line-reservation-3.png",[14,715,716],{},[95,717],{"alt":718,"src":719},"管理後台日曆檢視","/images/line-reservation-2.png",[10,721,178],{"id":178},[75,723,724,730,736,742,748],{},[49,725,726,729],{},[18,727,728],{},"無需註冊","：客戶只要有 LINE 就能使用，不用記帳號密碼",[49,731,732,735],{},[18,733,734],{},"即時通知","：透過 LINE 自動發送預約確認",[49,737,738,741],{},[18,739,740],{},"防止衝突","：系統會自動檢查時段是否已被預約",[49,743,744,747],{},[18,745,746],{},"響應式設計","：手機、平板、電腦都能順暢使用後台",[49,749,750,753],{},[18,751,752],{},"資料安全","：使用 Token 認證，保護客戶資料",[10,755,756],{"id":756},"技術架構",[14,758,759],{},"這個系統使用現代化的前後端分離架構：",[46,761,762,768,774,780,786],{},[49,763,764,767],{},[18,765,766],{},"前端（管理後台）","：Vue.js 建構互動介面，Tailwind CSS 設計美觀外觀",[49,769,770,773],{},[18,771,772],{},"後端（API 服務）","：Laravel 處理商業邏輯和資料庫操作",[49,775,776,779],{},[18,777,778],{},"LINE 整合","：透過 LINE Messaging API 收發訊息",[49,781,782,785],{},[18,783,784],{},"資料庫","：MySQL 儲存所有預約和客戶資料",[49,787,788,791],{},[18,789,790],{},"日曆套件","：FullCalendar 提供專業的日曆顯示",[10,793,794],{"id":794},"遇到的挑戰",[14,796,797],{},"在開發過程中遇到幾個主要挑戰：",[75,799,800,806,812,818,824],{},[49,801,802,805],{},[18,803,804],{},"LINE Webhook 即時訊息處理","：需要快速回應 LINE 伺服器，避免逾時",[49,807,808,811],{},[18,809,810],{},"預約衝突檢查與時段管理","：確保同一時段不會被重複預約",[49,813,814,817],{},[18,815,816],{},"前後端分離的 Token 認證機制","：保護 API 安全",[49,819,820,823],{},[18,821,822],{},"管理後台的權限控制","：不同角色有不同操作權限",[49,825,826,829],{},[18,827,828],{},"客戶資料與預約記錄的關聯設計","：資料庫結構要設計得清楚易維護",[10,831,832],{"id":832},"開發心得",[14,834,835],{},"這是我第一個整合第三方服務（LINE API）的完整專案，過程中學到：",[75,837,838,844,850,856,862],{},[49,839,840,843],{},[18,841,842],{},"API 整合","：學會如何串接 LINE Messaging API，處理 Webhook 即時訊息",[49,845,846,849],{},[18,847,848],{},"前後端分離","：理解前端和後端如何透過 API 溝通",[49,851,852,855],{},[18,853,854],{},"資料庫設計","：規劃客戶、預約、服務等資料表的關聯",[49,857,858,861],{},[18,859,860],{},"狀態管理","：使用 Pinia 管理複雜的應用程式狀態",[49,863,864,867],{},[18,865,866],{},"使用者體驗","：思考如何讓非技術人員也能輕鬆操作系統",[14,869,870],{},"最大的挑戰是處理預約衝突和時區問題，需要仔細檢查每個時段的狀態，確保不會重複預約。另外，LINE Bot 的對話流程設計也花了不少時間，要讓對話感覺自然又能完成預約。",[10,872,277],{"id":277},[14,874,875],{},"這個系統適合：",[46,877,878,881,884,887,890],{},[49,879,880],{},"美容美髮沙龍",[49,882,883],{},"按摩 SPA 店家",[49,885,886],{},"健身教練",[49,888,889],{},"醫療診所",[49,891,892],{},"任何需要預約制的服務業",[10,894,895],{"id":895},"未來規劃",[46,897,898,901,904,907,910,913],{},[49,899,900],{},"整合電子支付與自動對帳",[49,902,903],{},"多店家版本（連鎖店管理）",[49,905,906],{},"客戶評價系統",[49,908,909],{},"更豐富的數據分析報表",[49,911,912],{},"自動化行銷訊息（生日優惠等）",[49,914,915],{},"SaaS訂閱化",[118,917,918,922,925,931],{},[14,919,920],{},[18,921,330],{},[14,923,924],{},"如果你對這個專案有興趣、想試用或合作，歡迎透過以下方式聯絡我：",[14,926,927,339,929],{},[18,928,338],{},[341,930,344],{"href":343},[14,932,933],{},"我很樂意分享更多專案細節，或討論如何將此系統應用於你的業務中。",{"title":346,"searchDepth":347,"depth":347,"links":935},[936,937,938,942,943,944,945,946,947],{"id":12,"depth":347,"text":12},{"id":33,"depth":347,"text":34},{"id":131,"depth":347,"text":131,"children":939},[940,941],{"id":632,"depth":355,"text":633},{"id":662,"depth":355,"text":663},{"id":178,"depth":347,"text":178},{"id":756,"depth":347,"text":756},{"id":794,"depth":347,"text":794},{"id":832,"depth":347,"text":832},{"id":277,"depth":347,"text":277},{"id":895,"depth":347,"text":895},"整合顧客預約、店家管理與 LINE 通知，減少人工確認與訊息往返。","預約流程 / LINE 整合","2025.11",{"demo":369,"github":369,"figma":369},{},"/projects/line-reservation-system",{"title":594,"description":346},"透過 LINE 聊天機器人讓客戶輕鬆預約，搭配完整後台管理","projects/line-reservation-system",[384,958,959,960,589],"Vue.js","Laravel","FullCalendar",[962,963,393,960,589,964,965],"Vue 3 + Vite","Laravel 12","MySQL","Pinia (狀態管理)","eWZ91M7ttnXOmL5gM7_cmn_9ZpA02TFc3OkTSQjfKdg",{"prev":968,"next":369},{"id":399,"title":400,"body":969,"caseDescription":569,"caseStudy":374,"caseType":570,"category":371,"completedDate":571,"description":346,"extension":373,"featured":374,"links":1089,"meta":1090,"navigation":374,"order":574,"path":575,"projectType":576,"published":374,"seo":1091,"shortDesc":578,"stem":579,"tags":1092,"techStack":1093,"thumbnail":416,"__hash__":591},{"type":7,"value":970,"toc":1079},[971,973,975,977,981,983,991,993,1003,1005,1013,1017,1019,1031,1033,1055,1057,1065,1067],[10,972,12],{"id":12},[14,974,407],{},[14,976,410],{},[14,978,979],{},[95,980],{"alt":415,"src":416},[10,982,420],{"id":419},[46,984,985,987,989],{},[49,986,425],{},[49,988,428],{},[49,990,431],{},[10,992,435],{"id":434},[46,994,995,997,999,1001],{},[49,996,440],{},[49,998,443],{},[49,1000,446],{},[49,1002,449],{},[10,1004,452],{"id":452},[75,1006,1007,1009,1011],{},[49,1008,457],{},[49,1010,460],{},[49,1012,463],{},[14,1014,1015],{},[95,1016],{"alt":468,"src":469},[10,1018,473],{"id":472},[46,1020,1021,1023,1025,1027,1029],{},[49,1022,478],{},[49,1024,481],{},[49,1026,484],{},[49,1028,487],{},[49,1030,490],{},[10,1032,494],{"id":493},[46,1034,1035,1039,1043,1047,1051],{},[49,1036,1037,502],{},[18,1038,501],{},[49,1040,1041,508],{},[18,1042,507],{},[49,1044,1045,514],{},[18,1046,513],{},[49,1048,1049,520],{},[18,1050,519],{},[49,1052,1053,526],{},[18,1054,525],{},[10,1056,257],{"id":257},[46,1058,1059,1061,1063],{},[49,1060,533],{},[49,1062,536],{},[49,1064,539],{},[10,1066,300],{"id":300},[46,1068,1069,1071,1073,1075,1077],{},[49,1070,546],{},[49,1072,549],{},[49,1074,552],{},[49,1076,555],{},[49,1078,558],{},{"title":346,"searchDepth":347,"depth":347,"links":1080},[1081,1082,1083,1084,1085,1086,1087,1088],{"id":12,"depth":347,"text":12},{"id":419,"depth":347,"text":420},{"id":434,"depth":347,"text":435},{"id":452,"depth":347,"text":452},{"id":472,"depth":347,"text":473},{"id":493,"depth":347,"text":494},{"id":257,"depth":347,"text":257},{"id":300,"depth":347,"text":300},{"demo":369,"github":369,"figma":369},{},{"title":400,"description":346},[581,582,583,584,585],[587,588,391,589,590],1787125902567]