You provide the source of truth.
Your services, hours, locations, FAQs and approved policies. Specify which questions need staff, which details an enquiry needs, and who should receive it.
How it works
From your business knowledge
to a useful conversation.
See what you provide, how the assistant answers and acts, and when your team joins. A practical guide to the service we are building.
Product preview · In development01 / BEFORE THE FIRST CONVERSATION
A setup shaped around
your business.
- 01
Agree the journey
Choose the questions it should answer and what needs your team.
- 02
Prepare your knowledge
Supply your website, FAQs, service information and policies.
- 03
Review & approve
Check answers, boundaries and enquiry fields before use.
- 04
Install & test
Add the website widget, test the journey and agree launch readiness.
Illustrative workflow · Product in development
We define the workflow together.
For the proposed Custom service, our team handles the agreed configuration, website installation, testing and handover. Integrations, support and ongoing usage are scoped in your quote.
Explore Custom service ↗THE AUTOMATION, EXPLAINEDA clear path from
A clear path from
question to resolution.
Explore each step to see what happens—and where your team stays in control.
Your approved business informationServices · Opening hours · FAQs · Policies
How setup works ↗Visitor asks for a person, or the task exceeds permission?Ask for clarification or hand over to a person.
STEP 01
A visitor asks
The visitor starts the conversation. Voice requires microphone permission; written chat offers another way to ask. The assistant is clearly introduced as AI.
Read the detailSTEP 02
The assistant helps
The intended assistant uses your services, FAQs and policies. It answers routine questions directly and clarifies what the visitor needs. Tasks must stay within the business-approved permissions.
Read the detailSTEP 03
The task is handled
The intended assistant can answer directly or use an authorised booking connection. It must check availability, obtain the visitor’s confirmation, save the action and verify success before confirming it. The current preview simulates these steps.
Read the detailSTEP 04
A person, when needed
If the visitor asks for a person, or the task is outside the assistant’s permissions, offer a handover. Ask them to hold only when a team member can join; otherwise explain the follow-up option. Relay the team’s reply in the visitor’s language.
Read the detailInteractive illustration of the intended service. This diagram does not run AI or send enquiries.
02 / THE VISITOR STARTS
Talk naturally.
Or type instead.
A clear introduction, then a choice.
The visitor chooses to start; the assistant introduces itself as AI. Voice asks for microphone permission. Written chat is the intended alternative when speaking is inconvenient or voice is unavailable.
Connection, listening and error states should be visible. The planned experience includes a transcript and a clear way to end the conversation or request a person.
Read about language support ↗03 / INFORMATION BEFORE AUTOMATION
A helpful answer.
An approved action.
Can the assistant resolve this within the agreed permissions?
Explain the approved answer.
For example, share opening hours or a published service policy. Ask a follow-up question when the request is unclear.
Complete and verify the action.
Check live availability, ask the visitor to confirm, save the booking and verify the system’s success response. If any step fails, explain the problem and offer alternatives or a person.
Planned behaviour, not a live integration. The website demo uses fictional availability and simulated confirmations. AI can make mistakes; approved information still needs testing.
04 / WHEN A PERSON IS REQUESTED
A useful enquiry.
With the context attached.
The assistant helps first. If the visitor asks for your team, it explains the handover and asks permission to share the relevant context. A task outside its authority can also require a person.
Explore data & trust ↗- Request
- A visitor wants a site visit
- Useful context
- Preferred day and service needed
- Contact
- The details they agree to share
- Team summary
- A concise English summary
- Next action
- Check availability and reply
Delivery must be verified before the assistant says the enquiry has reached your team. Notification channels will be confirmed during setup.
05 / PEOPLE WHEN NEEDED
AI handles the everyday.
Your team handles the exceptions.
Review and respond
When someone asks for a person, your team receives the context and replies. The assistant relays the response. A live hold requires staff availability; otherwise it offers an honest follow-up option.
Keep information current
When your services, hours or policies change, review the assistant’s knowledge. The owner dashboard and update process are planned product features.
Stay within agreed limits
Voice allowances, session caps and a clear limit message are planned. Exact top-up and fallback behaviour will be confirmed before subscriptions open.
Find the right starting point.
The service is in development. Tell us about your website and the workflow you want to simplify; we can discuss fit and proposed setup scope.