For independent restaurants in the United States
A customer rings your existing number. Soulid answers in under three seconds, handles the order or booking, confirms the detail to the customer, fires the alerts, and logs the whole thing in the dashboard. Disclosure and escalation rules are set for the launch geography before traffic goes live.
The flow
Five moments sit between a ringing phone and a happy customer. Soulid runs all of them.
Customer dials your existing number. The call reaches Soulid through the existing telco route — no new number for the customer to learn.
In under three seconds, with the voice you selected at onboarding and the greeting tuned for the launch state's disclosure requirements.
Soulid identifies intent (order, booking, overflow request, or a configured question), asks for the detail it needs, and handles follow-ups naturally.
Soulid reads back the detail, captures the order or books the table, and triggers the right staff alerts. Complex cases escalate to a human.
Customer gets an SMS. The kitchen gets a printed ticket. The manager gets a WhatsApp alert. The dashboard updates live.
What happens on the call
Every task maps to one of the three pillars: revenue capture, operational automation, or real-time visibility.
Voice and accent
North American English is available at onboarding for United States venues — natural on the phone and tuned for the way customers actually order in market. Canadian, Australian, and New Zealand English are also available where they suit the venue better.
The written interface and public website stay in Australian English across every market. We keep that consistent and say it plainly rather than pretending each market has a different written voice.
United States rollout keeps the greeting and workflow aligned to the launch state's consent expectations. Where a state requires explicit two-party or all-party disclosure, that wording is reviewed before traffic goes live. The live placeholder sits at /privacy/#united-states.
Soulid isn't designed to pretend to be human. It's designed to sound natural enough that customers focus on their order, not on the fact that they're talking to a system. Where customers want a person, the flow hands off.
What your team sees
The point of Soulid isn't another dashboard to watch. It's fewer manual handoffs — so the team can stay on the floor and in the kitchen.
The right staff member gets a WhatsApp alert the moment an order or booking comes in — not five minutes later when someone checks the phone at the pass.
Tickets land on your existing receipt printer, formatted for the kitchen. Nobody is rewriting a handwritten docket from a bad phone line.
Phone duty isn't a person anymore. Front-of-house stays with tables. The chef stays on the line. The manager stops being the phone's default fallback.
A live manager dashboard view sits here showing call activity, order log, reservation calendar, and revenue captured. Final screenshot is blocked pending asset approval. The dashboard is live today for every pilot venue.
What the owner sees
Open a short dashboard view between covers and see calls answered, orders in, reservations confirmed, and revenue captured for the shift in progress.
Every order and booking gets an SMS confirmation so customers have the detail in writing. Less "is my order coming?" for the team to answer.
A short WhatsApp lands at close: total calls handled, orders booked, revenue recovered, missed-call patterns worth knowing. You read it, not reconstruct it.
Escalation and human fallback
Soulid handles the routine. It does not try to handle everything. The flow is built so customers never dead-end.
Large group bookings with specific requirements, private-dining enquiries, or anything outside the configured scope transfer to a staff member you nominate.
Soulid recognises when a caller is getting irritated or the conversation isn't progressing, and hands off to a human before the customer gives up.
If a call arrives outside the venue's hours and no after-hours coverage is configured, Soulid politely ends the call with the venue's hours and an SMS callback option. United States venues set hours against their local time zone — Eastern, Central, Mountain, or Pacific.
Once an order is placed, changes go to a human so nothing moves without the team's awareness. Cart updates before the order is finalised are automatic.
Setup and onboarding
Usually about a day once the key inputs are ready. If printer setup or escalation testing needs extra work, we say that upfront rather than inventing a faster timeline.
Share your menu, operating hours, reservation rules, and staff notification contacts. We configure Soulid around how the venue already runs.
Call forwarding is set on your existing line so Soulid answers inbound calls. Kitchen printer and WhatsApp alerts are wired to the right staff.
Your team runs live test calls covering common orders, reservations, and edge cases. We tune the wording and escalation paths with you before go-live.
Traffic flips. Soulid handles inbound calls from the next service. A Soulid launch contact is on standby through the first week.
Phase 1 scope
We're explicit about scope so nothing on the page is implying capability we don't ship yet.
How it works — FAQ
Soulid keeps a live placeholder at /privacy/#united-states and does not push live traffic into a launch geography until the greeting and workflow match that state's consent expectations. Two-party-consent states get explicit handling in the greeting and workflow rather than a generic script.
Yes. Each venue runs on its own local hours, so a Pacific venue and an Eastern venue can sit under the same operator without sharing the wrong opening or closing times.
Usually about a day once menu, operating hours, and notification rules are confirmed. If printer setup or escalation testing needs more work, we say that before launch rather than over-promising.
Soulid confirms the detail back to the customer before finalising the action, and the team can review the order or booking inside the workflow after submission. Where a call becomes messy or frustrated, it escalates to a human.
Yes. That's the default. Customers keep ringing the number they already know.
Book a 15-minute demo and we'll walk you through the exact flow on your existing phone number.