Voice Desk
An AI telephone assistant that can answer approved questions, capture an enquiry and bring your team in when needed.
See the call examples ↗Systems & automation for food & drink
Less chasing.
More time
for service.
Pick up the enquiry. Keep the details together. Give your team a clear next step.
Voice Desk, practical automation and AI opportunity audits, designed around how your business actually works.
THE WORK BEHIND THE WELCOMEIllustrative example
A busy service.
A useful handover.
A group dinner enquiry
The phone rings while the team is serving.
Voice Desk→Shared enquiry→Team follow-up
Ready for a person to review
Dinner for eight.
Occasion, preferred time and callback details gathered. Availability still to confirm.
Awaiting team confirmationA sample workflow, not a live call or customer record.
Three ways we can help
Start with the job
you need done.
Automation & integrations
Connect forms, inboxes, booking tools and shared records so routine work has a clear route through the business.
See the workflow examples ↗AI opportunity audit
A guided review of what happens now, what deserves attention and which changes would be worth testing.
See what you receive ↗01 / Voice Desk
A helpful first response.
Even when you are busy.
For calls during service, after hours or when the team cannot pick up. The scope and handover are agreed with you.
Voice Desk can handle routine questions from approved business information, gather the details of a request and transfer or arrange a callback. Booking confirmation is only possible where an agreed booking integration supports it.
Choose a call example
Illustrative text conversations. No microphone, recording or live telephone connection is used.
Sample conversation
A table for eight
Caller
“Could we bring eight people for dinner next Friday?”
Voice Desk
“I can take the details for the restaurant team to check. What time would you prefer, and what is the occasion? The team will confirm whether they can accommodate you.”
What happens next
Enquiry ready for the team
- Request
- Dinner for eight
- When
- Next Friday; preferred time to collect
- Next step
- Collect callback details and ask the team to check availability
No reservation confirmed. Availability comes from the venue’s booking system or team.
Sample conversation
An answer from approved information
Caller
“What time do you close on Sunday?”
Voice Desk
“Our current Sunday hours are 9am to 3pm. Would you like me to ask the team about anything else before your visit?”
What happens next
A straightforward question answered
- Source
- Approved opening-hours record
- Example answer
- Sunday, 9am–3pm
- Next step
- Offer staff help if the question goes beyond the approved information
Fictional opening hours for this example. A live service needs maintained business information.
Sample conversation
A question for the team
Caller
“One of our group has a severe allergy. Can they eat the Sunday roast?”
Voice Desk
“I cannot confirm whether a dish is suitable. I can ask a member of the team to speak with you about ingredients and preparation before you make plans.”
What happens next
Human follow-up required
- Request
- Discuss a dietary requirement
- Response
- No ingredient or suitability claim made
- Next step
- Transfer to an available person or arrange a callback
The assistant does not guess about allergens or promise that a meal is suitable.
Set up around your business
We agree the greeting, approved information, hours of operation, escalation rules and where enquiries should go.
A clear route to a person
Uncertain answers, special requests and sensitive questions go to the team. Transfer and callback arrangements are tested before launch.
02 / Automation & integrations
Less copying.
Fewer loose ends.
Give a repeated job a clear path from the first request to the person who needs to act. We check what your existing software can already do, then build the connections that are useful.
Choose a workflow example
Illustrative workflows. These examples do not connect to your software or send any data.
From a cake enquiry to a useful brief.
A birthday cake request arrives with a collection preference, portion size and flavour idea.
- 01
Capture the enquiry
Put the agreed details into one shared enquiry record.
- 02
Spot what is missing
Flag a missing date or unclear design request for the team.
- 03
Prepare the next reply
Draft a message asking for the missing detail, ready for review.
- 04
Keep approval with the bakery
A person agrees the design, feasibility, quote and collection arrangements.
The useful outcome
A clear brief and a reply ready to review.
No cake ordered and no price promised.
Where AI fits
AI can help summarise a free-text request. Moving known fields between a form and an enquiry record usually needs ordinary automation.
Keep a table change out of the cracks.
A customer asks to change a table from four people to six.
- 01
Find the right booking
Match the request to the authoritative booking record.
- 02
Check the change
Look up capacity through a supported integration, or ask the team to check.
- 03
Put it in front of the right person
Show the requested change and anything still needing confirmation.
- 04
Confirm and update together
After approval, update the booking and notify the people delivering the service.
The useful outcome
One proposed change, visible to the team.
The original booking stays in force until the change is confirmed.
Where AI fits
A booking connection and clear rules do most of the work. AI may help interpret a message, but it does not invent availability.
Give repeated questions a quicker answer.
The team keeps answering similar questions about group meals and private events.
- 01
Keep one approved source
Organise current menus, opening hours, group arrangements and policies.
- 02
Find the relevant information
Retrieve the approved details for the enquiry.
- 03
Prepare a helpful draft
Create a reply with the source information available to the team.
- 04
Review before sending
Ask a person to check exceptions, availability, prices and anything uncertain.
The useful outcome
A draft reply with the relevant facts beside it.
No message sent automatically in this example.
Where AI fits
AI can be useful for varied wording and draft replies when the source information is reliable. A short template may be enough for a frequent, fixed question.
The exact connections depend on your software, available integrations and access permissions. We confirm those before quoting a build.
03 / AI opportunity audit
Know what is
worth changing.
Bring us the work that feels harder than it should. We talk it through with the people doing it, review examples and test the assumptions before recommending a system.
- A clear picture of the current process and where it breaks down.
- A shortlist of worthwhile improvements, with effort and dependencies explained.
- Advice on whether AI, ordinary automation or a process change fits.
- A practical first step, agreed measures and a walkthrough of the findings.
Audit scope and fees are agreed before paid work begins. The free check is a preliminary demonstration; your recommendations are emailed to you.
Illustrative audit recommendation / bakery
Start with the enquiry brief.
- The issue to examine
- Cake requests arrive in separate messages, with dates and portion sizes often missing.
- The first improvement
- Use one enquiry form and a shared record. Make missing details visible to the team.
- Does it need AI?
- The first connection probably does not. AI-assisted summaries may help later if free-text requests remain time-consuming.
- What to measure
- Time spent clarifying each enquiry, unanswered requests and the proportion progressing to an agreed order.
- Who stays in control?
- The bakery team approves designs, quotes and collection arrangements.
Fictional example of the kind of recommendation an audit can produce, not a finding about your business.
Build it. Connect it. Keep it useful.
Automate the routine.
Escalate the important.
We can take care of setup, testing, documentation and training, then provide ongoing support where you need it.
Talk through a system ↗Agree the job
Choose the task, the useful outcome and the person responsible.
Build & test
Try normal requests, unclear inputs and connection failures before going live.
Hand over clearly
Give your team instructions, training and a reliable fallback. Human approval where consequences matter.
Support & improve
Review failures, keep approved information current and agree improvements as the business changes.
Before we start
A few practical questions.
Do we need to replace our existing software?
Often the starting point is something you already use. We check its features and supported connections before suggesting a replacement.
Can Voice Desk book tables or take orders?
That depends on the agreed scope and your booking or ordering system. Without a tested connection that can confirm availability and acceptance, it captures a request for the team to confirm.
Does every improvement need AI?
No. A shared record, a better form or ordinary automation may solve the problem. AI is useful when a defined task benefits from interpreting varied information or drafting a response.
Who sets it up and looks after it?
VSL can design, configure and test the system, train your team and provide ongoing support. Responsibilities and support arrangements are agreed in the project scope.
How much does it cost?
We scope and quote the work around your requirements, software and call or task volumes. Any third-party subscriptions and ongoing support are made clear before you commit.
Start with one thing
What keeps getting
in the way?
A ringing phone during service. A booking change nobody saw. The same details typed into three places. Tell us where your team loses time.
Book a free 20-minute call ↗
No technical brief needed. We can help you work out the starting point.