One question, one useful answer
Explain the main point first, then add the details a caller is likely to need. Avoid combining several unrelated policies in one long article.
A LITTLE GUIDANCE GOES A LONG WAY
Get to know
Get to know
YourCallHandler.
Start with the essentials, explore the roadmap and find the right approach for your team.
Getting started
How an AI assistant fits into your business
Explore the four steps from business context to customer conversations.
Explore Integration guideConnect the tools your team relies on
See what is planned for WHMCS, Shopify and WooCommerce.
Explore Service optionsManaged or bring your own keys?
Compare the two approaches and understand provider responsibility.
Explore Product overviewGive your assistant useful context
Learn about agents, approved knowledge and controlled access.
Explore Your questionsFind a clear answer
Read common questions about availability, setup and live calling.
Explore Let’s talkHave a workflow in mind?
Tell us about your business and the calls you want to handle.
Explore Explore the productAbout
Your Call Handler is being built to connect useful conversations with the way your business works.
Explore Explore the productUse Cases
Explore the roles you can prepare for an assistant, from a first enquiry to a support question.
Explore Explore the productAI Receptionist
Prepare an assistant to introduce your business, understand an enquiry and explain where the caller should go next.
Explore Explore the productCustomer Support
Prepare customer support around approved information and the checks your team uses before accessing private records.
Explore Explore the productSales Enquiries
Prepare an assistant to explain your offering and collect the context your sales team needs for a useful conversation.
Explore
A PRACTICAL STARTING POINT
Turn everyday questions into useful knowledge.
Begin with your team’s experience. Collect the questions that recur in calls and support tickets, then write short answers using the language your customers use. Give every article a descriptive title so its purpose is easy to recognise.
Keep a simple review routine: who owns the answer, when it was last checked and what should happen if the policy changes. The development application supports manual articles and draft or approved states; website imports and live retrieval are not yet available.
Keep public and private information separate
General service information can support a public answer. Customer-specific data needs a verified identity and an authorised live tool, rather than a pasted knowledge article.
Name the escalation route
If an answer depends on a person, explain which team handles it and what information helps them respond. Keep that route consistent with the agent instructions.
THE LANGUAGE OF YOUR ASSISTANT
A few terms, explained plainly
Understand the building blocks before deciding how to configure them.
Agent and knowledge base
An agent is a configured assistant with a role, greeting and instructions. Its knowledge base is the business information intended to help it answer questions. Draft configuration and article approval are separate from enabling a live telephone workflow.
BYOK and managed services
BYOK means bring your own keys: you configure your own provider credentials and pay those providers directly. All-in-one is the planned managed option. Both still need a verified, tested voice connection before callers can use the assistant.
Verification and authorisation
Verification establishes that a caller meets the business identity checks. Authorisation decides what information or tasks that verified caller can access. Knowing a customer name is not sufficient by itself to permit sensitive account actions.
YOUR NEXT CONVERSATION STARTS HERE
Less missed calls.
Talk to us
Less missed calls.
More possibilities.
Build an assistant around the way your business works.