Deciding who a call is put through to, what happens when nobody answers, and what to do within two minutes if your calls stop arriving.
A clear rule for what happens when a call has to reach you right away: who is called, in what order, and what happens if nobody picks up. A transfer that rings into the void is worse than taking a message.
And a procedure for the day it breaks — an outage at a vendor, forwarding switched off by mistake, a number that changed. The first thing to do does not depend on us: it happens from your handset.
Allow ten minutes for the settings, and bookmark this page for the rest.
Transferring is a choice, not a default: several businesses prefer taking a message with an immediate alert, which rings nobody into the void.
An emergency by your rule, a caller who insists, a specific kind of request. Everything else stays with message-taking and a written summary.
One person, then a second, then message-taking. During on-call hours, the person on call replaces the ordinary list.
The assigned callback: the request is created, a person becomes responsible for it, and the callback due shows in the inbox. The caller gets an answer even when no human could take the call.
Dial the cancel code from the forwarded handset: your line returns immediately to its previous behaviour. You take your own calls again while we look.
The time you noticed the problem is the single most useful thing. The workspace keeps the history of calls received: that is what tells whether the break sits with us or with your phone carrier.
A transfer puts the caller through to a person. When that person picks up, it is the best possible answer. When they do not, the caller has heard one more ring tone and still has no answer — and now feels they were passed around.
Taking the message with an immediate alert gives everybody an answer: the caller knows what happens next, you get the summary straight away, and you call back when you can actually talk. Many businesses end up preferring that setup, and it is not a retreat.
When nobody picks up, the request is created, someone on your team becomes responsible for it, and the call-back due appears in the inbox beside the conversation that produced it. It does not disappear until it is handled.
Voicemail, by contrast, drops a message somewhere nobody watches and assigns it to no one. The difference is measured in call-backs that get lost, not in the quality of the recorded greeting.
First remove forwarding from the handset concerned, then call your line directly. If it rings normally, the break is downstream and the exact time lets us place it. If it does not ring, the fault is at your phone carrier.
The on-call list replaces the ordinary list during the hours you declared. Changing who is on call needs no change to forwarding or to your instructions: it is a setting of its own.
The call stays in your log with its time and number, even with no request created. That is often enough to call back, and it is how you notice that one number has tried several times.
That is the worst outcome for the caller, because it feels like being sent nowhere. Put message-taking as the last step of the list: it catches what the numbers do not.
For activities declared sensitive, retention at the voice provider is switched off: the recording can be missing by design, not by failure. The written request and the summary stay available.
The transfer list points at a number nobody watches any more. Check the list, and add message-taking as the last step: it catches everything that falls through.
Your urgency rule is too broad. Rewrite it from a real case rather than in categories — a precise rule fires less and gets listened to more.
Remove the forwarding, then test your line directly. If it rings normally, the break is downstream; write to us with the time. If it does not ring, call your phone carrier.
For lines of work declared sensitive, retention at the voice provider is switched off: the recording may be missing by design. The written request is still there.
What owners ask when the call chain breaks.
Dial the forwarding cancel code from the forwarded handset. Your calls come straight back to you, and that move depends neither on your account nor on us.
The time you noticed the problem, and the number called. The history of received calls then shows whether the break is on our side or at your phone carrier.
No, it is a choice. Several businesses prefer message-taking with an immediate alert, which gives the caller an answer without ringing a handset nobody is watching.
Write your urgency rule from a real call that made you drop everything, rather than in general categories. A precise rule fires less often and gets listened to more.
«Water running right now» fires better than «urgent plumbing problem».
Calls that arrived before forwarding was removed stay in your workspace, with their transcript and their request. Nothing is lost on the side already handled.
Yes. Call your own line from another phone, or run a test call from your browser: the browser one touches neither your line nor your count.
Every task has its own.
What touches the line itself.
