For independent restaurants in New Zealand
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 voice you selected at onboarding and the greeting you configured. Caller disclosure for the New Zealand rollout is built into the opening flow.
Soulid identifies intent — order, booking, 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. New Zealand English is available for New Zealand venues — comfortable with the way customers actually order here, and confident with place names from Auckland and Wellington through Christchurch and regional towns.
If your customer base benefits from a different voice, Australian, Canadian, and North American English are available too. The interface and written copy remain in Australian English regardless — a product-level decision we're open about.
Every call opens with caller disclosure aligned to the New Zealand rollout. The live addendum at /privacy/#new-zealand makes it explicit where wording is final and where legal review is still underway, instead of pretending the paperwork is finished.
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.
Calls, orders, reservations, and revenue captured update live in the dashboard, but the workflow still reaches the team through the tools they already use.
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 transfers 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. Hours respect New Zealand local time, including daylight-saving changes.
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 customer behaviour to teach. The bulk of setup is telling us how your venue already runs, then confirming the flow with test calls.
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. We keep the rollout practical and staged rather than over-promising a fantasy launch window.
Phase 1 scope
We're explicit about scope so nothing on the page implies capability we don't ship yet.
How it works — FAQ
The voice accent is selectable at onboarding — Australian, New Zealand, Canadian, or North American English. Pick whichever feels right for your venue's brand and customer base.
Yes. The goal is to keep the customer experience simple by using the number they already call.
We align the New Zealand rollout to the NZ Privacy Act 2020, including caller disclosure and a published privacy addendum. The live detail, including what is still under legal review, sits at /privacy/#new-zealand.
Yes. The value comes from handling both customer demand and the resulting workflow in one system.
Soulid confirms details back to the customer before finalising the action, and the team can review the workflow after submission. Where the call clearly needs a person, Soulid escalates instead of pushing through.
Book a 15-minute demo and we'll walk you through the exact flow on your existing phone number.