鼎呼 DineCall AI 博客
探索 AI 电话接听、餐饮运营,以及真实餐厅如何使用鼎呼 DineCall AI。
电话订单如何进入你的系统
这是档案的最后一页,收着两篇解释底层机制的文章。第一篇讲清楚一通电话订单是怎么进入你的收银系统:DineCall AI 与你已经在用的 POS 并行运行,餐厅保留自己原有的对外电话号码,一套开放且有文档的订单 API 把订单送进指定 POS 终端。
最值得读两遍的是那份数据结构——它把一段对话变成厨房能直接执行的订单。订单事件触发一个标准 JSON webhook,带着订单编号、来源、状态、通话语言、时间戳,顾客的姓名、电话号码以及是否是老客,订单类型,以及每一道菜的中英文名称、数量、价格和规格。小计、税和总额一并送出。这一整套内容不需要任何人再手工敲一遍。
第二篇是一份实地记录:四家餐厅,四种部署方式,以及它们各自的不同之处。一间厨房,一条原有的线路,稳定的晚餐高峰;一间既要订桌也要点单的餐厅;一家来电大多是提问的场所;一家用两种语言接同一条电话的面馆。同样的产品,四种配置——而每一种情形下面都是同一套设计:房间忙不过来时有人接电话,并且把说过的话记下来,记成别的业务可以继续使用的形式。
两个细节把这两篇文章接在一起。一是速度:语音转文字与文字转语音的系统经过调优,让来电者在 800 毫秒内听到回应,这才让整段对话像一通电话,而不是一张填不完的表。二是 AI 停下来的那个点:当它对听到的内容信心低于 70%,或者来电者要求找经理时,它会用电话和后台通知提醒前厅员工——线路忙时则记录一条回电工单。
- Revenue
The Phone Is Ringing. Nobody Is Picking Up.
Every missed call is a transaction that did not happen. Here is what that actually costs — and why the math on AI phone answering is simpler than most restaurants realize.
阅读更多 → - Case Studies
Three Restaurants, Three Phones, None of Them Ringing Out
Hao's Lamb Restaurant, Royal Beef, and Hao's Tapas Kitchen each have their own phone line. DineCall built the website and answers all three — and the oven that needs a head start never misses a call.
阅读更多 → - Integration
AI Phone Orders and Your POS: How the Integration Actually Works
Your POS is not going anywhere. DineCall works alongside it — the AI handles the phone channel while your existing system keeps running exactly as it does today.
阅读更多 → - Case Studies
Four Restaurants, Four Deployments: AI Phone Answering in the Wild
King Do, Yuan's Garden, Dimsum Caddy, and Lao Cai each have a different setup. Here is what each one actually runs on DineCall — and why their setup looks the way it does.
阅读更多 →
显示 49–52,共 52 篇