Everything it does, and everything it doesn’t

Always on

On every call, with nothing to switch on

Says it is an AI, before anything else

Not a setting. If that sentence is missing the line refuses to take calls at all.

No menu, no keypad, no hold

There are no numbers to press — the software has no way to read them. Your caller just says what they rang about.

Speaks only sentences a named person approved — word for word

Not its own words about your documents — the sentence your business wrote, read out as written. If two approved answers both fit, it declines rather than picking one.

Every answer carries its approver, its date and its expiry

One named person per sentence. The approver list refuses “assistant”, “machine” and “AI” as the name of who approved it — it has to be a person.

Withdraw a sentence and it stops saying it in about two seconds

While the line is running. Nothing has to be re-installed and nobody has to wait for an update.

When nothing matches, it says so rather than guessing

Its words: “I’m sorry, I don’t have an answer for that one. Is there anything else I can help with?” There is no fallback wording for it to reach for.

Hears goodbye and stops asking

Measured against 47 Australian ways of ending a call, so it does not keep going after someone has said they’re done.

Stops rather than looping

Two separate limits — too many questions it could not answer in a row, and too long overall. It ends the call politely instead of going round again.

It keeps a record of the call, not a recording of it

What was asked and what happened is written down. The audio is not kept, and neither is a word-for-word transcript.

Writes down every question it could not answer

As a counted work list, most common first, naming which of your own rules refused each one.

You see the whole call on one screen before a caller hears it

Every step of the call laid out, with a label on each one saying what it is allowed to do. One thing to be clear about: drawing the call is how you see and approve it, not how you build it. Three things you draw actually change what happens — whether it can book a meeting, offer a callback, or mention that you’re closed. If you draw a branch, the picture records it, but the call does not follow it.

Yours to switch on

Built, and off until you switch it on

Each one waits on a decision, or a connection, from you.

Ask to be rung back

Off until you turn it on. It uses the number the phone network gives us, never digits the caller reads out — those get misheard.

Connect it to your calendar

The dialogue for offering times, confirming one and booking it is built and tested. What is not built is the link to your actual calendar, so today this is the groundwork rather than a booking service. Which calendar your business uses decides how that link gets built.

Announce a closure without being asked

Three settings: the days of the week you’re open, a list of public holiday dates, and a one-off closure that overrides both. The weekly pattern and the holiday list work out the reopening day together — shut on Christmas Day and again on the Monday after, a caller on the Friday is told you reopen on the Tuesday. All three are configuration rather than a screen, and anything left unset or unreadable means the line answers as normal rather than telling a caller you’re shut.

Read a number back one digit at a time, and wait for a yes

Nothing is done with a number a caller says out loud until they have heard it read back and said yes.

Not today

Not today — not “not yet”

None of these has a date. Naming one would be a promise rather than a description.

Transfer a live caller to a person’s phone

You can draw a transfer step, and the line will not do it — it says so plainly rather than pretending, and offers to have someone ring the caller back instead.

Rank calls by urgency, or screen out wrong numbers

There is no screening step and no urgency scoring in the product. Not switched off: not built.

Look up a customer’s account, job or file history

There is no customer register and no job or matter store, so it says it cannot see their records rather than guessing at one.

Route a caller by topic

Bookings to one person, accounts to another. Decided and not built.

Take a message in the caller’s own words

It notes what they rang about and offers to have someone ring them back on the number they called from. It does not write their message down for you.

Speak a live fact — a balance, a lodgement status

Anything that changes during the day is held back until we have built the rule for what happens when it goes out of date. A number that was right this morning is the most dangerous thing a phone line can say.

Never

It will never do these

Deliberate decisions not to build. The reasons are more useful than the features would be.

Take a card payment

Taking card details brings a whole set of banking security obligations onto a line built to keep as little as possible. The two do not belong together.

Notice that a caller is distressed

A machine that notices distress and does nothing about it is worse than one that never claimed to notice. If that matters on your line, it needs a person, not a feature.