[{"data":1,"prerenderedAt":751},["ShallowReactive",2],{"site-schema":3,"article-zh-tw-logistics-app-development-guide":106,"article-related-zh-tw-logistics-app-development-guide":733},{"@context":4,"@graph":5},"https:\u002F\u002Fschema.org",[6,85,97],{"@type":7,"@id":8,"name":9,"alternateName":10,"description":17,"knowsAbout":18,"legalName":27,"foundingDate":28,"numberOfEmployees":29,"taxID":30,"url":31,"logo":32,"founder":33,"contactPoint":35,"address":49,"location":55,"sameAs":75},"Organization","https:\u002F\u002Fjoinx.co\u002F#organization","JoinX哲煜科技",[11,12,13,14,15,16],"JoinX","TWJOIN","哲煜科技","哲煜科技股份有限公司","TWJOIN 哲煜科技","twjoin.com","JoinX 哲煜科技（原品牌名 TWJOIN）是 2016 年在台北成立的軟體開發公司，80+ 人自有團隊，承接客製系統、APP、AI 導入與 IoT 開發，以及軟體外包與既有系統接手維運，服務 220+ 客戶、完成 520+ 專案。",[19,20,21,22,23,24,25,26],"軟體外包","客製化系統開發","APP 開發","AI 導入","AI Agent 開發","IoT APP 開發","ERP 系統整合","既有系統接手維運","JoinX Co., Ltd.","2016-04-28",80,"43774383","https:\u002F\u002Fjoinx.co","https:\u002F\u002Fjoinx.co\u002Fimages\u002Flogo-with-name.png",{"@id":34},"https:\u002F\u002Fjoinx.co\u002F#person-jack-lee",[36],{"@type":37,"contactType":38,"url":39,"telephone":40,"email":41,"areaServed":42,"availableLanguage":45},"ContactPoint","customer service","https:\u002F\u002Fjoinx.co\u002Fcontact-us","+886-2-8771-9095","service@joinx.co",[43,44],"TW","JP",[46,47,48],"zh-Hant","en","ja",{"@type":50,"streetAddress":51,"postalCode":52,"addressLocality":53,"addressRegion":54,"addressCountry":43},"PostalAddress","民生東路二段170號8樓","104","台北市中山區","台灣",[56,63,69],{"@type":57,"name":58,"address":59},"Place","JoinX 台中辦公室",{"@type":50,"streetAddress":60,"postalCode":61,"addressLocality":62,"addressRegion":54,"addressCountry":43},"台灣大道二段360號21樓C室","40453","台中市北區",{"@type":57,"name":64,"address":65},"JoinX 高雄辦公室",{"@type":50,"streetAddress":66,"postalCode":67,"addressLocality":68,"addressRegion":54,"addressCountry":43},"民族一路80號2樓之一","807","高雄市三民區",{"@type":57,"name":70,"address":71},"JoinX 東京辦公室",{"@type":50,"streetAddress":72,"postalCode":73,"addressLocality":74,"addressCountry":44},"東五反田5-22-37 Office Circle N 五反田 9樓","141-0022","東京都品川區",[76,77,78,79,80,81,82,83,84],"https:\u002F\u002Fwww.crunchbase.com\u002Forganization\u002Ftwjoin","https:\u002F\u002Fwww.facebook.com\u002FJoinX.TW","https:\u002F\u002Ftw.linkedin.com\u002Fcompany\u002F%E5%93%B2%E7%85%9C%E7%A7%91%E6%8A%80","https:\u002F\u002Fwww.youtube.com\u002Fc\u002Fjoinstuido%E5%93%B2%E7%85%9C%E7%A7%91%E6%8A%80","https:\u002F\u002Fmedium.com\u002Ftwjoin","https:\u002F\u002Fwww.104.com.tw\u002Fcompany\u002F1a2x6bjomb","https:\u002F\u002Fclutch.co\u002Fprofile\u002Fjoinx","https:\u002F\u002Fwww.goodfirms.co\u002Fcompany\u002Ftwjoin","https:\u002F\u002Ftwjoin.com",{"@type":86,"@id":34,"name":87,"alternateName":88,"jobTitle":89,"worksFor":90,"url":91,"sameAs":92},"Person","李秉哲","Jack Lee","創辦人暨執行長",{"@id":8},"https:\u002F\u002Fjack88.joinx.co\u002F",[93,94,95,96],"https:\u002F\u002Fwww.instagram.com\u002Fjack88.podcast\u002F","https:\u002F\u002Fwww.threads.net\u002F@jack88.podcast","https:\u002F\u002Fjoinx.co\u002Fjack88\u002F","https:\u002F\u002Fwww.linkedin.com\u002Fin\u002Fjacklee-taiwan\u002F",{"@type":98,"@id":99,"url":31,"name":9,"alternateName":100,"publisher":101,"inLanguage":102},"WebSite","https:\u002F\u002Fjoinx.co\u002F#website",[11,13,9],{"@id":8},[103,104,105],"zh-Hant-TW","en-US","ja-JP",{"id":107,"title":108,"body":109,"category":697,"cover":698,"dateModified":699,"description":700,"extension":701,"faq":699,"hasCoverTitle":702,"locale":703,"meta":704,"navigation":705,"need":706,"path":707,"seo":708,"seoDescription":699,"seoTitle":699,"sources":709,"stem":723,"takeaways":724,"time":730,"type":731,"__hash__":732},"content\u002Fzh-tw\u002Farticle\u002Flogistics-app-development-guide.md","物流 APP 怎麼開發？司機端、貨主端與後台功能、費用與時程（2026）",{"type":110,"value":111,"toc":675},"minimark",[112,120,129,134,137,205,208,212,215,317,320,323,327,330,333,349,352,356,359,440,448,451,455,458,534,541,544,548,551,590,593,597,600,605,611,617,627,631,637,640,644,647,651,654,658,661,665,668,672],[113,114,115,119],"p",{},[116,117,118],"strong",{},"物流 APP 不是一支給司機用的 APP 而已，而是司機、貨主與調度三端共用同一張配送單的系統。"," 開發時先讓派單、司機回報、簽收與客服查件這條線跑通，其他功能再依營運需要分版加入。",[113,121,122,123,128],{},"這篇的角度是「物流 APP 要怎麼開發」：每一端要做哪些功能、費用與時程怎麼估、開發要怎麼分階段。如果你還在決定要買現成的 WMS、TMS，還是自己開發，建議先看",[124,125,127],"a",{"href":126},"\u002Farticle\u002Flogistics-management-system-guide\u002F","物流管理系統怎麼選","，確定要自建之後再回來看這篇。",[130,131,133],"h2",{"id":132},"物流-app-要開發哪幾端","物流 APP 要開發哪幾端？",[113,135,136],{},"通常是三端：司機用的 APP、貨主下單與查件的入口，以及調度、客服與財務共用的管理後台。三端看的是同一張配送單，只是每個角色能看、能改的欄位不同。",[138,139,140,159],"table",{},[141,142,143],"thead",{},[144,145,146,150,153,156],"tr",{},[147,148,149],"th",{},"端",[147,151,152],{},"誰在用",[147,154,155],{},"主要工作",[147,157,158],{},"常見形式",[160,161,162,177,191],"tbody",{},[144,163,164,168,171,174],{},[165,166,167],"td",{},"司機端",[165,169,170],{},"自有司機、合作車隊",[165,172,173],{},"看今日任務、更新狀態、簽收拍照、回報異常",[165,175,176],{},"原生或跨平台 APP",[144,178,179,182,185,188],{},[165,180,181],{},"貨主端",[165,183,184],{},"委託配送的企業或個人",[165,186,187],{},"下單或匯入、查件、下載簽收紀錄、看對帳單",[165,189,190],{},"網頁、LINE，量大再做 APP",[144,192,193,196,199,202],{},[165,194,195],{},"調度後台",[165,197,198],{},"調度、客服、財務、主管",[165,200,201],{},"派單與改派、處理異常、計價對帳、看報表",[165,203,204],{},"網頁後台",[113,206,207],{},"三端的資料要以「配送單」為中心串起來：貨主建立的單，調度派給司機，司機回報的簽收與異常寫回同一張單，客服和財務再從同一張單查詢與請款。只要有一端另外開表格記錄，查件時就又要回頭打電話問人。",[130,209,211],{"id":210},"司機-app-要有哪些功能","司機 APP 要有哪些功能？",[113,213,214],{},"司機 APP 的核心是今日任務、狀態回報、電子簽收與異常回報四項。設計原則是單手就能完成、能少打字就少打字，因為司機是在搬貨、停車的空檔操作手機。",[138,216,217,230],{},[141,218,219],{},[144,220,221,224,227],{},[147,222,223],{},"功能",[147,225,226],{},"為什麼需要",[147,228,229],{},"第一版要不要做",[160,231,232,243,253,263,273,284,295,306],{},[144,233,234,237,240],{},[165,235,236],{},"今日任務與站點順序",[165,238,239],{},"司機一打開就知道今天要跑哪些站",[165,241,242],{},"要",[144,244,245,248,251],{},[165,246,247],{},"狀態回報（取件、配送中、送達）",[165,249,250],{},"客服不用打電話問貨到哪裡",[165,252,242],{},[144,254,255,258,261],{},[165,256,257],{},"電子簽收與拍照",[165,259,260],{},"簽收紀錄直接對到這張單，不用回站再整理紙本",[165,262,242],{},[144,264,265,268,271],{},[165,266,267],{},"異常回報（拒收、短少、破損、無人收件）",[165,269,270],{},"部分完成的配送也能留下實收數量與原因",[165,272,242],{},[144,274,275,278,281],{},[165,276,277],{},"開啟導航",[165,279,280],{},"交給既有地圖 APP 導航，不必自己做地圖",[165,282,283],{},"建議",[144,285,286,289,292],{},[165,287,288],{},"離線暫存與補傳",[165,290,291],{},"地下室、偏遠路段訊號不穩時不會掉資料",[165,293,294],{},"依路線決定",[144,296,297,300,303],{},[165,298,299],{},"位置回報",[165,301,302],{},"讓調度看到車輛大概位置",[165,304,305],{},"依需求，要處理權限與耗電",[144,307,308,311,314],{},[165,309,310],{},"貨物交接",[165,312,313],{},"改派或轉運時記錄誰交給誰、交了多少",[165,315,316],{},"有轉運流程再做",[113,318,319],{},"位置回報要特別規劃。APP 在背景持續取得位置時，Google Play 要求開發者說明用途並通過審查，Apple 的審查指南也要求清楚告知使用者為什麼需要位置資訊。很多物流業者其實只需要「狀態回報時順便記下位置」，不需要全天候追蹤，這樣審查、耗電與司機的接受度都比較單純。",[113,321,322],{},"司機的位置、收件人姓名、地址、電話與簽收照片都是個人資料，後台的查詢權限、保存期間與刪除方式要依《個人資料保護法》規劃，例如合作車隊的司機只看得到派給自己的單。",[130,324,326],{"id":325},"貨主端要做-app-還是網頁","貨主端要做 APP 還是網頁？",[113,328,329],{},"多數情況先做網頁或 LINE 查件就夠。貨主端的使用頻率比司機低，做成網頁不用下載，也不用經過商店審核；等到下單量大、需要推播通知時，再做成 APP。",[113,331,332],{},"貨主端常見的功能：",[334,335,336,340,343,346],"ul",{},[337,338,339],"li",{},"線上下單，或用 Excel 範本批次匯入。",[337,341,342],{},"依單號查詢配送狀態、簽收照片與異常原因。",[337,344,345],{},"下載簽收紀錄與每月對帳單。",[337,347,348],{},"多個帳號分權限，例如分公司只看自己的單。",[113,350,351],{},"如果貨主是企業客戶，而且自己有 ERP 或電商平台，與其要求對方登入你的網頁，不如提供 API 讓對方系統直接建單與查詢。這時貨主端的重點就從畫面變成串接文件與測試環境。",[130,353,355],{"id":354},"調度後台要有哪些功能","調度後台要有哪些功能？",[113,357,358],{},"調度後台負責把單派出去、把異常收回來、把錢算清楚。功能可以分成派單、異常處理、計價對帳與管理四塊，第一版先做派單與異常，計價對帳可以先匯出 Excel 給財務。",[138,360,361,374],{},[141,362,363],{},[144,364,365,368,371],{},[147,366,367],{},"功能塊",[147,369,370],{},"主要內容",[147,372,373],{},"第一版建議",[160,375,376,387,397,408,419,430],{},[144,377,378,381,384],{},[165,379,380],{},"派單與改派",[165,382,383],{},"訂單匯入、依區域與時段派給司機或合作車隊、改派紀錄",[165,385,386],{},"必做",[144,388,389,392,395],{},[165,390,391],{},"異常處理",[165,393,394],{},"拒收、短少、破損的通知與後續處理，補送任務連回原單",[165,396,386],{},[144,398,399,402,405],{},[165,400,401],{},"計價與對帳",[165,403,404],{},"依合約計價、對帳單、請款狀態",[165,406,407],{},"可先匯出 Excel",[144,409,410,413,416],{},[165,411,412],{},"司機與車輛管理",[165,414,415],{},"司機資料、班表、車輛資料",[165,417,418],{},"依車隊規模",[144,420,421,424,427],{},[165,422,423],{},"報表",[165,425,426],{},"每日配送量、異常比例、各司機完成數",[165,428,429],{},"先做最常用的兩三張",[144,431,432,435,438],{},[165,433,434],{},"權限",[165,436,437],{},"調度、客服、財務、合作車隊各看各的資料",[165,439,386],{},[113,441,442,443,447],{},"派單規則是最容易低估的一塊。同一個區域，可能還要考慮收貨時段、車型與司機熟悉的路線；第一版建議由系統列出待派單、由調度人員確認，等規則穩定後再評估自動派單。派車與路線規劃的做法，可參考",[124,444,446],{"href":445},"\u002Flogistics-system\u002F","物流系統開發","。",[449,450],"article-cta",{},[130,452,454],{"id":453},"物流-app-開發費用與時程大概多少","物流 APP 開發費用與時程大概多少？",[113,456,457],{},"依 JoinX 整理的台灣 APP 委外行情，司機 APP 加管理後台多半是功能型 APP，約 NT$120–300 萬、3–6 個月；只在既有系統旁補一支司機回報 APP，NT$15 萬起；三端齊備又要串多個系統的平台，依範圍估價。",[138,459,460,476],{},[141,461,462],{},[144,463,464,467,470,473],{},[147,465,466],{},"範圍",[147,468,469],{},"常見內容",[147,471,472],{},"預估費用",[147,474,475],{},"參考時程",[160,477,478,492,506,520],{},[144,479,480,483,486,489],{},[165,481,482],{},"單一功能司機 APP",[165,484,485],{},"只做任務清單、狀態回報與簽收，資料寫回既有系統",[165,487,488],{},"NT$15 萬起",[165,490,491],{},"依功能而定",[144,493,494,497,500,503],{},[165,495,496],{},"第一版驗證（MVP）",[165,498,499],{},"司機 APP 加精簡後台，跑通一條配送線",[165,501,502],{},"約 NT$50–120 萬",[165,504,505],{},"6–12 週",[144,507,508,511,514,517],{},[165,509,510],{},"司機 APP＋管理後台",[165,512,513],{},"派單、改派、簽收、異常處理、權限、報表",[165,515,516],{},"約 NT$120–300 萬",[165,518,519],{},"3–6 個月",[144,521,522,525,528,531],{},[165,523,524],{},"三端平台",[165,526,527],{},"再加上貨主端、計價對帳與多個系統串接",[165,529,530],{},"依範圍估價",[165,532,533],{},"依範圍分階段上線",[113,535,536,537,447],{},"影響金額最大的是三件事：要串接的既有系統數量（ERP、電商平台、GPS 車機，每個整合點約 NT$5–20 萬）、是否需要離線與背景定位，以及司機 APP 做原生還是跨平台。另外要算進 Apple 開發者帳號每年 US$99、Google Play 一次性 US$25 的註冊費，以及上線後的維運。APP 的分級價格與維護費，可參考",[124,538,540],{"href":539},"\u002Farticle\u002Fapp-development-cost-2026\u002F","APP 開發費用",[113,542,543],{},"以上是預算規劃的起點，不是固定報價，實際費用依需求定價。",[130,545,547],{"id":546},"物流-app-開發要怎麼分階段","物流 APP 開發要怎麼分階段？",[113,549,550],{},"先選一條代表性的配送線跑通，再擴大範圍。以下是 JoinX 規劃物流 APP 時的順序，每一步都用實際的派車表與簽單來確認，而不是只看理想流程。",[552,553,554,560,566,572,578,584],"ol",{},[337,555,556,559],{},[116,557,558],{},"跟司機走一趟。"," 記下每一站實際怎麼交貨、在哪裡會卡住，把司機 APP 的操作步驟壓到最少。",[337,561,562,565],{},[116,563,564],{},"畫出配送單的狀態。"," 從建單、派單、取件、配送中、送達到部分簽收、退回、補送，先定義清楚每個狀態由誰改、改了通知誰。",[337,567,568,571],{},[116,569,570],{},"做原型給司機試用。"," 先用可點擊的畫面讓司機試按，確定好用再寫程式。",[337,573,574,577],{},[116,575,576],{},"開發第一版。"," 只做跑通一條配送線所需的功能：派單、司機回報、簽收、異常與客服查件。",[337,579,580,583],{},[116,581,582],{},"選固定路線試行。"," 找熟悉流程的司機先用，測試正常配送，也測試拒收、短少與改派。",[337,585,586,589],{},[116,587,588],{},"依營運需要分版擴充。"," 第一版穩定後，再依序加入貨主端、計價對帳、報表或系統串接。",[113,591,592],{},"開發流程採用 SDD + TDD：先把規格寫清楚，再用測試確認每個狀態轉換都符合規格。交付前，JoinX 會自行完成原始碼掃描與弱點掃描（白箱）；如需黑箱測試，由第三方執行，JoinX 可協助聯繫、推薦廠商，並修補後交付。",[130,594,596],{"id":595},"joinx-做過哪些物流-app-與系統","JoinX 做過哪些物流 APP 與系統？",[113,598,599],{},"JoinX 開發過快遞業者的物流管理系統與司機 APP，也為物流業者開發過發報系統。兩個專案都是依業者自己的營運流程設計，而不是套用現成產品。",[601,602,604],"h3",{"id":603},"欣晨快遞物流管理系統與司機-app","欣晨快遞：物流管理系統與司機 APP",[113,606,607,610],{},[116,608,609],{},"起點："," 欣晨快遞需要一套貼合自身營運流程的物流管理系統，讓後台管理與司機的現場作業接在同一套系統裡。",[113,612,613,616],{},[116,614,615],{},"我們做的："," 開發物流管理系統，並搭配司機使用的 APP。第一版上線後，沒有一次把所有功能做完，而是依營運需要分階段擴充。",[113,618,619,622,623,447],{},[116,620,621],{},"合作多久："," 2025 年起開發，至今已擴充到第五版。完整過程可參考",[124,624,626],{"href":625},"\u002Fcase-studies\u002Fsin-chen\u002F","欣晨快遞案例",[601,628,630],{"id":629},"物流業者發報系統","物流業者：發報系統",[113,632,633,636],{},[116,634,635],{},"做法："," 2020 至 2023 年為物流業者開發發報系統。依保密約定，這個案例只揭露產業與系統類型。",[130,638,639],{"id":639},"常見問題",[601,641,643],{"id":642},"司機-app-要做原生還是跨平台","司機 APP 要做原生還是跨平台？",[113,645,646],{},"看司機用的裝置與需要的手機功能。司機多半自備手機、iOS 和 Android 都有時，跨平台可以用一套程式碼同時支援兩邊；需要大量背景定位、藍牙掃描器或長時間離線時，原生開發比較好掌握耗電與穩定度。",[601,648,650],{"id":649},"貨主端一定要做-app-嗎","貨主端一定要做 APP 嗎？",[113,652,653],{},"不一定。貨主查件的頻率通常不高，網頁或 LINE 查件就能滿足大部分需求，也不用經過商店審核。下單量大、需要推播通知，或貨主本身有系統要直接建單時，再做成 APP 或提供 API。",[601,655,657],{"id":656},"物流-app-開發要多久","物流 APP 開發要多久？",[113,659,660],{},"司機 APP 加管理後台的第一版，常見是 3–6 個月；只跑通一條配送線的驗證版，約 6–12 週。之後再依營運需要分版擴充，例如欣晨快遞的物流管理系統與司機 APP 從 2025 年起開發，分階段擴充到第五版。",[601,662,664],{"id":663},"已經有物流系統可以只做司機-app-嗎","已經有物流系統，可以只做司機 APP 嗎？",[113,666,667],{},"可以。如果既有系統的派單功能夠用，只是司機回報與簽收還靠紙本或群組，可以只做司機 APP，把狀態與簽收寫回既有系統，NT$15 萬起。能不能寫回，要先確認既有系統的 API 或資料交換方式。",[601,669,671],{"id":670},"物流-app-上線後還要花哪些錢","物流 APP 上線後還要花哪些錢？",[113,673,674],{},"主要是維運、伺服器與商店帳號。維運通常是每年開發費用的一定比例，包含修正問題、配合 iOS 與 Android 改版更新，以及依營運需要調整流程；Apple 開發者帳號每年 US$99，Google Play 註冊費一次性 US$25。",{"title":676,"searchDepth":677,"depth":677,"links":678},"",2,[679,680,681,682,683,684,685,690],{"id":132,"depth":677,"text":133},{"id":210,"depth":677,"text":211},{"id":325,"depth":677,"text":326},{"id":354,"depth":677,"text":355},{"id":453,"depth":677,"text":454},{"id":546,"depth":677,"text":547},{"id":595,"depth":677,"text":596,"children":686},[687,689],{"id":603,"depth":688,"text":604},3,{"id":629,"depth":688,"text":630},{"id":639,"depth":677,"text":639,"children":691},[692,693,694,695,696],{"id":642,"depth":688,"text":643},{"id":649,"depth":688,"text":650},{"id":656,"depth":688,"text":657},{"id":663,"depth":688,"text":664},{"id":670,"depth":688,"text":671},"技術分享","\u002Fimages\u002Fblog\u002Flogistics-app-development-guide.webp",null,"物流 APP 通常要做三端：司機用的 APP、貨主下單查件的入口，以及調度人員用的後台。第一版先讓「派單、司機回報、簽收、客服查件」這條線跑通，再依營運需要分版擴充。司機 APP 加管理後台多半落在功能型 APP 的級距，約 NT$120–300 萬、3–6 個月；只在既有系統旁補一支司機回報 APP，NT$15 萬起。本文整理三端的功能清單、費用與時程、開發步驟，以及 JoinX 的物流專案做法。","md",false,"zh-tw",{},true,"派單系統","\u002Fzh-tw\u002Farticle\u002Flogistics-app-development-guide",{"title":108,"description":700},[710,713,716,719,721],{"name":711,"issuer":712},"《個人資料保護法》","法務部",{"name":714,"issuer":715},"Google Play 開發人員政策：位置資訊權限","Google",{"name":717,"issuer":718},"App Store 審查指南","Apple",{"name":720,"issuer":718},"Apple Developer Program 註冊說明",{"name":722,"issuer":715},"Play Console 開發者帳號註冊費說明","zh-tw\u002Farticle\u002Flogistics-app-development-guide",[725,726,727,728,729],"物流 APP 通常分三端：司機 APP、貨主入口與調度後台，三端讀寫同一張配送單。","司機 APP 的核心是今日任務、狀態回報、電子簽收與異常回報，操作步驟要壓到單手就能完成。","貨主端多半先做網頁或 LINE 查件就夠，下單與查件頻率高、需要推播時再做成 APP。","司機 APP 加管理後台約 NT$120–300 萬、3–6 個月；只補一支司機回報 APP 串既有系統，NT$15 萬起。","欣晨快遞的物流管理系統與司機 APP 2025 年起開發，依營運需要分階段擴充到第五版。","2026\u002F11\u002F04","blog","RSA8uRsfR3t6cN6EfagNzg0zSDC1mo7wQSwun7fXa-s",[734,739,745],{"slug":735,"title":736,"time":737,"cover":738,"need":706},"dispatch-system-development-guide","派工系統怎麼規劃？設備維修、工程服務與外勤作業的開發重點","2026\u002F09\u002F10","\u002Fimages\u002Fblog\u002Fdispatch-system-development-guide.webp",{"slug":740,"title":741,"time":742,"cover":743,"need":744},"pos-system-guide","POS 系統怎麼選？套裝、雲端 POS 與客製 POS 的差異、硬體、串接與費用（2026）","2026\u002F11\u002F12","\u002Fimages\u002Fblog\u002Fpos-system-guide.webp","POS 系統",{"slug":746,"title":747,"time":748,"cover":749,"need":750},"ai-customer-service-voice-agent","AI 語音客服怎麼導入？Voice Agent 的架構、適合場景、廠商評估與費用","2026\u002F11\u002F10","\u002Fimages\u002Fblog\u002Fai-customer-service-voice-agent.webp","AI 客服",1794558642257]