Category: Smart Receptionist & AI · Last updated 16 Nov 2026
Getting your Smart Receptionist ready: what we need from you
The checklist we work through with you to set up the Smart Receptionist: voice, knowledge base, routing, details to collect and testing.
We set the Smart Receptionist up for you, and setup is included in every pack. The better the information you give us, the better it performs from day one. This article is a checklist of what we'll ask for and what to think about.
1. How it should sound
- Name - Should it introduce itself with a name ("Hi, this is Alex from Riverside Dental") or just the business name?
- Voice - We'll offer a few voice options. Pick one that suits your brand.
- Tone - Formal, friendly, brisk? A couple of example sentences in your own words help us match your style.
- Greeting - What it says when it answers. Keep it short.
2. What it should know
The Smart Receptionist answers questions from a knowledge base we build with you. Good sources are:
- Your website pages (we can pull these in directly)
- An FAQ document, even a rough one
- Price lists, service menus or brochures
- Opening hours, addresses, parking and access notes
- Anything your receptionist answers ten times a day
Start with the top ten. Write down the ten questions callers ask most, with the answers you'd want given. That alone covers most calls. We can add more over time, and the call transcripts will show us what's missing.
It's just as important to tell us what it should not answer. For example, it shouldn't quote prices for custom work, give medical advice or confirm a booking it can't see.
3. Where calls should go
For each kind of request, tell us the destination:
| Caller wants | Send to |
|---|---|
| Sales | Sales ring group |
| An existing booking | Reception, extension 100 |
| Accounts or invoices | Jo, extension 105 |
| A specific person by name | That person's extension |
| Anything urgent after hours | On-call mobile |
| Something it can't help with | Take a message, email to admin@ |
Also tell us what to do when the destination doesn't answer: try someone else, take a message, or offer to have someone call back.
4. What details to collect
Before it transfers or takes a message, the Smart Receptionist can gather details and pass them on. Common ones are the caller's name, a callback number, a customer or job reference, and a one-line reason for the call. Tell us which matter to you.
5. Hours and handover
- Should it answer all calls, or only overflow and after hours?
- Should callers always be able to say "I'd like to speak to a person" and be transferred? (We recommend yes.)
- After hours, should it take messages, ring an on-call number, or both?
6. Connecting your systems
If you'd like the Smart Receptionist to look things up or take actions, such as checking an appointment, logging a job or creating a lead, tell us which software you use. We'll check whether it has an API and work with you (or your software vendor) to connect it. Have your API documentation handy if you have it.
7. Test and launch
- We build it Greeting, knowledge base, routing rules and any integrations.
- You test it We give you a test number. Call it, try the questions your customers ask, and try to trip it up.
- We adjust We fix anything it got wrong and add what it didn't know.
- Go live We point your number (or your overflow and after-hours rules) at it.
- We keep tuning We review transcripts with you after the first week and the first month, and whenever you tell us something's changed.
Keeping it current
When your hours, prices, staff or services change, send us the update and we'll change the knowledge base, usually the same day. Ongoing changes are included in your pack.
Related Articles
- Smart Receptionist & AIWhat is the Smart Receptionist?An AI receptionist that answers your calls in plain language, answers questions and puts callers through. We set it up for you.
- Smart Receptionist & AICall and voicemail transcriptionVoicemail-to-text, live call transcripts with summaries and action items, and how to turn them on.
Was this article helpful?
Your feedback helps us improve our support content.