From your daily enquiries to a tested agent.
Bring one recurring enquiry to the first conversation. We agree the task, required access, person responsible and test plan before proposing a launch date.
Request a callAgree the scope before building.
A useful first project has a specific job: answer common questions, collect booking requests or route callers to your team.
We review the information and connections that task needs, then agree what is included, who is responsible and how you will judge the result. Any missing access is part of that discussion.
Setup and launch steps.
You approve the business information and review the results before the agent handles customer conversations.
-
01
Show us how you answer today
Tell us who contacts you, what they ask, which languages they use and what happens when your team is busy.
We identify a task to start with and the information needed to assess it.
-
02
Build around your business information
Your services, prices, hours and booking rules provide the starting point. You review the content and how the agent introduces itself.
Together we try common questions, unfamiliar requests, failed connections and handoffs. Approved information still needs testing: AI can make mistakes.
-
03
Review the results before launch
Check the agreed tasks, any unresolved errors and what happens when the agent needs help. You approve the launch when the required checks are complete.
Records, access and export requirements are agreed as part of the same scope.
-
After launch
Review outcomes and keep information current
The support contact, review schedule and process for changing prices, hours or services are agreed before launch.
What affects the schedule.
Business information, system access and time to review the results all affect when the agent can start.
-
Current answers
Provide prices, hours, services and the questions you answer every day. Identify anything the agent must leave to your team. If the answers are not written down, we can draft them with you.
-
Someone who can approve
Name the person who can approve the information, test results and launch. They need time to review errors as well as successful examples.
-
Access to your systems
Phone routing, calendar permissions and messaging accounts need to support the chosen task. If a connection cannot do what is needed, we revise the scope before launch.
Questions about the process
When can a pilot start?
The date follows the scope, access review and test plan. We do not promise a fixed number of days before those are known.
Who writes the answers?
You provide the business facts. We can prepare a draft for you to correct and approve as part of the agreed setup.
What if an answer is wrong?
We agree how to report it, inspect the available records and pause or correct the affected response. The tests include questions the agent should pass to a person.
Do I need to change my phone or systems?
We check whether your current setup supports the chosen task. Any required change is included in the scope for your review.
How much time will you need from me?
Start with the 20-minute call. You will also provide information, arrange access and review tests; the time needed depends on the scope.
How do I change information after launch?
Use the agreed change process. Updates are reviewed and tested before taking effect, especially when they affect prices, bookings or transfers.