The questions people actually ask

An AI receptionist built to answer your business phone line, speaking only sentences a named person at your business has already approved.

A machine takes a message. This is built to answer the question — in your words, from your own document — and, when it has no approved answer for what was asked, to note what they rang about and offer to have someone ring them back. It does not write their message down for you.

No. There is no menu, no keypad and no hold. The line picks up and speaks, the caller says what they rang about in their own words, and it answers. There is no keypad handling anywhere in the software to switch on.

Always, before anything else. This one is not a setting: if that sentence is missing, the line refuses to take calls at all.

It has nothing to make anything up with. There is no fallback wording anywhere in the answering path — it either finds a sentence a person approved, or it has none, and those are the only two outcomes.

It says so and asks whether there is anything else — the call carries on. Only after several questions in a row it cannot answer does it offer to have someone ring them back on the number they called from, and ring off. If it has no number to use it asks them to ring back instead. It does not guess, and it does not improvise something close. What it keeps for you is the number and what they rang about — never their words.

One named person at your business, per answer, with the date recorded. Never the software. The reviewer list refuses “assistant”, “machine” and “AI” as a signature.

About two seconds, and it needs no deployment. Withdraw it and a running line stops saying it on the next call.

Every approved answer carries an expiry date, and it is mandatory. When it lapses the line stops using it and hands those callers to a person instead — it never keeps saying something because nobody got round to re-checking it.

No, and we would rather say so than imply it. There is no screening step and no urgency scoring in the product — not switched off, not built. What it does instead is answer everyone courteously and hand anything it has no approved answer for to a person.

Not today. You can draw a transfer step on the canvas, and the line will not perform it — the software refuses, by name, rather than pretending. It offers to have someone ring the caller back instead, and if they would rather not, the call carries on.

Both, in different ways. A caller who speaks Chinese is asked — in Cantonese — whether they would like Cantonese or Mandarin, and the disclosure is given again in the one they choose. One who answers in English stays in English; one who names neither, or says nothing, gets Mandarin. Mandarin since 26 August and Cantonese since 11 September, each with answers where the business has approved one in that language. In tests, not yet on a call from a real caller.

No. There is no customer register and no job or matter history in the product, so it will say it cannot see their records rather than guess at one.

Not yet, and this is the honest one. Calls have run on it — but ours, from one handset, to one computer of ours. That is a demonstration, not a service you could point a number at, and we are not going to describe it as one until it is.

A working line whose governance is finished and whose hosting is not. The part that is hard to get right — never saying anything a person did not approve — is built, tested and provable today.

Two plans are published, and their prices are on the pricing page. That page also says, plainly, that nobody has paid them yet and that the call allowances are estimates rather than measurements.

Not today, and there is no date. We do intend to — the decision that governs this says adding a country should be a setting and a reviewed script rather than a code change — and that setting is now built, but a lawyer in the new country has to approve what the caller is told before we would launch there. That one is not ours alone to finish, which is why nobody here will give you a quarter.

Some of it offshore, and we will not claim otherwise. Region-locking is designed and not yet built, so anyone who needs a data-residency guarantee in writing does not have one from us yet.