Resources
Practical Guides to Call Handling
Forty working guides covering what an AI receptionist is, whether you need one, how to design and implement call handling, the Singapore data obligations that apply, and how to measure whether any of it worked. Written to be used rather than to sell.
What these guides are for
Most material published about AI call handling is written to sell it. These guides are written to help you make a decision and then implement it properly, which are different objectives.
Several are useful even if you never automate anything. Measuring missed calls, reducing no-shows and designing a consistent phone script are all improvements you can make with your existing team and no software at all.
Where a guide touches on regulation, we describe the general position and point you towards your own advisers. We are not lawyers, and a guide is not advice on your specific obligations. Where we cite research, the publisher and year are named on the page.
New to this? Read what is an AI receptionist first. It explains what happens on a call, what the technology will not do, and how it differs from voicemail and phone menus.
Start here: understanding what this is
Six explainers answering the questions people actually ask first, including the ones that count against automation.
Deciding whether to do it at all
Establish where enquiries are being lost before choosing anything. These guides use your own figures rather than industry averages, and two of them conclude that some businesses should wait.
Designing the call handling
The decisions to settle before anything is built: what each call type should end in, what gets said, and what must always reach a person.
Implementing it
What a deployment involves in sequence, from routing your number through to testing scenarios before a customer hears them.
Data protection and Singapore obligations
Recording calls and storing customer details brings obligations under the Personal Data Protection Act and the Do Not Call provisions. These guides describe the general position; confirm what applies to your business with your own advisers.
Measuring and improving
Responsiveness is a capability to be measured against your own starting point rather than a product to switch on. These guides cover what to track and what to do with it.
How the technology works
Background for anyone who wants to understand what sits behind the conversation, including the vocabulary suppliers use and what the technology still gets wrong.
Common questions
Do I need to be a customer to use these?
No. Several guides describe improvements you can make with your existing team and no software at all.
Where should I start?
What is an AI receptionist if the concept is new, or reducing missed calls if you already know you have a problem and want to size it.
Are the figures in these guides benchmarks?
We avoid publishing benchmarks. The methods use your own data, because industry averages rarely describe any particular business. Where we cite published research, the publisher and year are named.
Is this legal or regulatory advice?
No. Where regulation is relevant we describe the general position and suggest confirming your obligations with your own advisers.
How often are they updated?
When practice changes materially. Technology guidance dates faster than the operational material.
Can we share these internally?
Yes. They are written to be circulated to whoever is making the decision.
Where to go next
Work through one with us
If a guide raises a question about your own operation, we are happy to go through it, whether or not it leads anywhere commercial.