What a Phone Order Looks Like as Data
Every call DineCall AI takes produces a structured JSON payload — the full order, the caller, the language, the total. Here is what is inside it, and what you can do with it.
A voicemail is a recording. A note on a pad is a human artifact. What DineCall AI produces when it takes a phone order is neither. It is a structured JSON payload — machine-readable, sent by webhook, and ready to route into whatever system needs it.
What the payload contains
Every order event generates a webhook with a full order record. From the published specification (dinecall-facts.ts §4), the payload includes:
An order ID (for example: DC-1042-998). The source: phone_ai. The order status: sent_to_kitchen. The language of the call (for example: zh-Hans for Mandarin). A timestamp. The customer object — phone number, name, and a isRegular flag for recognized returning callers. The order type (e.g. pickup). The items array — each item with English name, Chinese name, quantity, unit price, and any modifiers. And a subtotal, tax, and total.
The published example payload:
Salt & Pepper Shrimp 椒盐虾, quantity 2, with an Extra Spicy modifier, at $15.50 each. Beef Chow Fun 干炒牛河, quantity 1, at $11.50. Subtotal: $42.50. Tax: $3.82. Total: $46.32. All of it in the same payload, from a call that was answered in Mandarin.
Why the structure matters
A voicemail tells the kitchen nothing directly. A pad note requires a human to read it and type it in somewhere. A JSON payload with a standard schema can be consumed by whatever is listening — a kitchen display, a POS terminal, a custom dashboard, an inventory tracker.
The isRegular flag in the customer object is worth noting separately. When a returning customer calls, the AI recognizes their phone number and marks isRegular: true.
Where the payload goes
The webhook fires on order events. What receives it depends on the restaurant's setup.
DineCall has confirmed integrations with: POS KING, Square, Toast, Clover, SpotOn, NCR Aloha, Shift4, RestoSuite, Olo, and OpenTable. For restaurants running one of these, the order ticket can land inside the existing POS workflow directly — the kitchen board the team already watches shows the AI order alongside everything else, with no new screen to check.
For restaurants with custom integrations — an in-house kitchen display, a BI tool, a delivery aggregator — the webhook is an open endpoint. The payload schema is the contract. Any system that can receive an HTTP POST with a JSON body can consume it.
What about the data security
Payments are processed through Stripe, PCI-DSS compliant. DineCall does not store raw card data. Call recordings are encrypted at rest (AES-256) and in transit (TLS 1.3). The customer record in the webhook payload contains a phone number and name, not payment credentials.
What this replaces in practice
Before a webhook-driven integration, the phone order path in most restaurants looks like this: a server picks up, writes the order on a pad, walks it to the kitchen, and someone enters it into the POS. The order exists as handwriting, then as a POS entry.
With DineCall, the webhook fires at the moment the order is confirmed on the call. The POS — if wired — has the entry already. The pad note does not exist. There is no second entry, no transcription error, no "I thought you said no onion."
FAQ
Q: Can I receive the webhook payload in my own system? A: Yes. The webhook fires on order events and is delivered to your endpoint. The payload schema is published in the integration documentation. Any system that can consume JSON over HTTP can receive it.
Q: Does the webhook fire in real time? A: Yes. The payload is sent at the moment the order is confirmed on the call.
Q: Does the isRegular flag appear for every returning caller? A: Yes. When the AI recognizes the caller's phone number from a prior call, it sets isRegular: true and includes the customer's name in the payload.
Q: What POS systems does DineCall integrate with? A: POS KING, Square, Toast, Clover, SpotOn, NCR Aloha, Shift4, RestoSuite, Olo, and OpenTable. For other systems, the ordering API covers the integration path — the technical team confirms the wiring during onboarding.
Q: Is there an extra charge for webhook access or API integration? A: No. The webhook and API are included in the flat monthly fee, and there is no setup fee.