How do I route calls by what the caller needs?

Phone menus are the old way to do this, and callers pick whichever option sounds closest rather than the one that fits. A caller with a leaking pipe and a billing question presses 1 and lands in sales.

Routing on the caller's number breaks just as easily. People ring from a mobile one day and the office the next, and withheld numbers match nothing at all.

A spoken reason works for every caller, including the ones you've never met. "Rooftop unit four is down at Lakeside Mall" tells you it's commercial and urgent before anyone on your side is rung.

List the five or six reasons people actually call. Your last month's voicemails or call notes will show them: new quote, existing job, emergency, billing, supplier, job applicant.

Give each reason one destination. A person's number for live transfers, the on-call phone for emergencies, and a message for everything that can wait until morning.

Add a backup for each live transfer. A second number catches the call when the first person is on a ladder, and a full message catches it when neither answers.

Test each route with a real call, saying the reason the way a customer would. Then read the summaries to check every call landed where you meant it to.

Say you run a heating and cooling company with a commercial division and a residential one. Three calls come in on a Wednesday.

The first caller says, "I'm the facilities manager at Lakeside Mall, and rooftop unit four is down." He's phoning from his personal cell, which isn't in anyone's table. Because the assistant asked what he needed, the call goes to the commercial service desk with the unit number already noted.

The second says her air conditioning is blowing warm. Her call comes from her employer's main line, a number shared by 200 people, and she's routed to residential dispatch on the strength of what she said.

The third is a parts supplier calling about a back-ordered compressor, from a call center number that changes weekly. A message goes to purchasing and nobody's afternoon is interrupted.

A number-based table would have recognized none of them.

A few callers are worth recognizing by number, and the list should fit on a sticky note. Your largest account's main line is one. The alarm monitoring company that calls about your own building is another, and perhaps the owner's family. If your phone system can send specific caller IDs straight to a person before any forwarding happens, set those up there and leave everything else to the conversation.

Treat caller ID as a hint and never as proof. Numbers can be spoofed with little effort. A call that appears to come from a customer's number shouldn't, on that basis alone, get account details, a changed appointment or a gate code. Identity needs a question only the real customer can answer, asked by whoever takes the call.

Review the list every quarter. People change jobs and companies change carriers, and a rule for a number that now belongs to a stranger is worse than having none.

If recognizing existing customers matters to you, send each call to your own system through the webhook. The caller's number and summary arrive there, so your team sees the match with the reason attached.

GreetKeeper routes by what the caller needs and transfers to your team when a caller asks or the reason matches a rule. If the first number doesn't answer, it tries a second number you nominate.

The caller's name, number and reason travel with every transfer and land in the summary, so whoever picks up already knows why the phone rang. For urgent calls, the on-call person also gets a text with the details.

Each number can have its own hours, greeting and calendar under one account. A branch line or an ad tracking line can follow its own rules. Routing is included on every plan from $49 a month.