What is an escalation path?

Escalation path
An escalation path is the defined sequence of what happens when a call cannot be handled at the current step, naming who it goes to next and what happens if they are unavailable.

What escalation path means in practice

Every phone setup has one, whether or not anyone wrote it down. The undocumented version is usually voicemail.

A good path names people and situations rather than describing a principle. Who, for what, and by when.

The last step is the one people forget. What happens when nobody at all is available needs an answer that is better than an endless ring.

What people get wrong

One property manager's path, written down

Say you manage 140 rental units. Here's your path for an urgent maintenance call at night, as it appears on a single printed page. Step one: the assistant confirms the address and the problem, and tells the tenant to call 911 first if there's fire, gas or a medical issue.

Next comes a transfer to Luis, the on-call tech, which rings for 25 seconds. If Luis doesn't answer, step three transfers to Andre, the backup, for another 25. When neither picks up, the fourth step is to tell the tenant that a message is going to the manager right now, text the summary to your cell, and log the time. The page also lists what counts as urgent: no heat below 40 degrees outside, active water leak, no working toilet in the unit, lockout, and a broken exterior door. It carries a date and Luis's and Andre's rotation weeks. Ask any vendor how many fallback steps its system supports before you design yours.

Why a path goes stale

An escalation path is a list of people and phone numbers, and both change. Someone gets a new cell number, goes on vacation or leaves the company. Meanwhile the path keeps sending 2 am emergencies to a phone in a drawer.

Nobody notices, since the path only runs when something has already gone wrong, and that might be once a month. So it needs an owner and a schedule like any other piece of equipment. Put one person in charge of it. Review it on the first of every month, and again whenever anyone on it is hired, leaves or takes time off. Print the date on it so that a stale copy is obvious.

Vacations cause the most trouble. When your on-call tech is away for a week, the quick fix is to forward his cell to someone else, and then nobody remembers to undo it. Change the path itself for that week, and put the change-back date on your calendar.

How GreetKeeper handles it

GreetKeeper follows the chain you configure: try to resolve, transfer if a rule says so, take a message if the transfer fails, and text the on-call phone for anything you marked urgent.

A transfer that rings out returns the caller to the assistant rather than dropping them, which is the branch most setups get wrong.

The transcript records which step fired and what the caller had said at that point, so you can see whether the rules are catching what you meant.

Escalation questions

How many steps should there be?

Three or four covers most small businesses. Longer chains mainly add ways for a caller to end up somewhere nobody is watching.

Who should be last in the chain?

Whoever would rather be interrupted than lose the call, which in a small business is usually the owner. Make that an explicit decision rather than a default.

Should urgency change the path?

Yes, and that is most of the value. Define the urgent situations specifically, or the rule catches ordinary inquiries and you stop trusting the alerts.

Hear it take one of your calls

Two minutes, your own scenario, no card.