For independent restaurants in Australia
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. Here's what sits behind each of those moments.
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 Australian-accent voice and the greeting you configured. Caller disclosure is built into the greeting.
Soulid identifies intent (order, booking, overflow-table 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
The voice Soulid uses on the phone is selected at onboarding. Australian English is the default for Australian venues — trained on Australian speech patterns, comfortable with the way customers actually order here, and confident with place names from Parramatta to Prahran to Paddington.
If your customer base benefits from a different voice (New Zealand, Canadian, or North American English), that's available too. The interface and all written copy stay Australian English regardless.
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 — see escalation below.
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. Customers waiting for a table get a text update when it's ready. 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, function-room 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.
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
No tech overhaul, no new behaviour to teach customers. The bulk of setup is telling us how your venue runs today.
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
In practice, yes — provided the experience is clear, natural, and helpful. Soulid discloses on the greeting that it's answering the call, reads back every order before confirming, and hands off to a person if the caller asks or gets stuck. Most Australian customers want their order taken quickly and correctly; that's what the flow is built for.
Yes. Multi-site operators run one configuration across venues with a shared dashboard. Each venue keeps its own number, menu, and staff notification setup. The owner gets a single view of both venues plus a per-venue drilldown.
We work around your current telco setup. Most venues use a simple call-forwarding rule on the existing line — we configure which calls Soulid answers and which (if any) keep going to an existing destination. No porting is required.
The greeting includes call-recording disclosure by default, aligned to the Australian Privacy Principles and the Privacy Act 1988. Transcripts and (where enabled) audio sit in the dashboard, accessible to the owner and configured staff. Full detail lives at /privacy/#australia.
Book a 15-minute demo and we'll walk you through the exact flow on your existing phone number.