Emergency trades
A forced lock at two in the morning does not go into a queue. An urgency rule transfers at once, and everything else waits until morning without waking anybody.
When a human has to take over, the call is handed across — and when nobody is free, the callback is assigned to somebody rather than left hanging.
7 days, 20 answered calls, no card
A useful receptionist also knows when to stop. Some calls have to reach a human voice right away: a real emergency, an important client, a situation nobody planned for. The rest of the time, transferring is the worst reflex — it interrupts a busy person over a question that fitted in a message.
This function draws that line. You decide what triggers a transfer, toward whom, during which hours, and what happens when nobody picks up. Everything else becomes an assigned callback: a name, a reason, a deadline, and a request staying visible until somebody handles it.
A callback assigned to nobody is handled by nobody. That is why assignment belongs to the function rather than to a board people may or may not check.
Whatever triggers a transfer is written down: a word in the conversation, a type of request, an identified client, a time range. Outside that rule, the conversation carries on.
Whoever receives the call also receives the context: who is calling, about what, what has been collected. They do not restart a conversation from zero.
A transfer that does not land becomes an assigned callback, with an owner and a deadline. The caller knows what happens next before hanging up.
A callback is a request like any other: it has a state, a deadline, and it stays in the queue until somebody closes it.
Transferring a call, creating an assigned callback and routing belong to a base. A callback dialled by the receptionist itself is part of the Lead capture and sales follow-up add-on.
What gets added on purpose: spreading requests across several teams with response targets and overflow rules — that is the advanced team routing add-on, which has its own page.
A forced lock at two in the morning does not go into a queue. An urgency rule transfers at once, and everything else waits until morning without waking anybody.
Anything touching a person's condition is routed to a practitioner or to emergency services, under practice rules. The receptionist does not settle that question.
A water leak in a building transfers to whoever is on call. A receipt request waits, carrying an assigned callback and its date.
You decide what deserves interrupting somebody. The receptionist does not transfer to shed a difficult question.
A transfer extends the current conversation: it creates no second base call.
Whatever you wrote down: a word in the conversation, a type of request, an identified client, a time range. Outside that rule, the conversation carries on.
The rule reads as a list of triggers: an emergency, a final price asked for, a big project, a technical question, work starting within two weeks, an address outside your service area. You keep the ones that serve you and add your own, in plain words. A renovation contractor adds a visit to schedule and a commercial client or a property manager, and spells out that a big project means a full basement or bathroom, or several rooms: those calls are handed over at once, and if nobody picks up, the callback is assigned to the owner.
No. They receive the context with the call — who is calling, about what, what has been collected — and they do not restart the conversation from zero.
A transfer that does not land becomes an assigned callback, with an owner and a deadline, and the caller knows what happens next before hanging up. A callback assigned to nobody is handled by nobody: that is why assignment belongs to the function.
No. A transferred conversation stays counted once.
Yes, with the Lead capture and sales follow-up add-on; your base carries the transfer, the assigned callback and the routing.
Spreading work across teams, or back to what happens before a transfer.
Transfer and callback