Phone etiquette for a business that answers its own calls

A caller decides whether they've reached a competent business before you finish your first sentence. Three things have to be in it: the business name, a human name, and an offer to help.

"Good morning, Cedar Street Dental, this is Maya — how can I help?" does all three in about four seconds. "Hello?" does none of them and makes the caller ask whether they've dialed correctly, which is a bad way to start.

The business name first matters more than it sounds. People dial several numbers in a row when they're shopping around, and they genuinely lose track. Leading with the name saves them the question.

Two things to avoid: a greeting so long the caller forgets why they rang, and a scripted singsong that signals a call center. The written greeting exists so that nobody has to improvise at 8:58am — not so it can be recited. Our phone script generator will build one for your business, and there's more on the exact wording in how to answer the phone professionally.

Hold is where most calls are lost, and the fix is three small habits.

Ask, then wait for the answer. "Can I put you on hold for a moment?" followed by an actual pause. Announcing hold and pressing the button in the same breath is the single most irritating thing a business phone does.

Give a real estimate. "About two minutes" sets an expectation the caller can plan around. "One moment" means nothing, so they start counting, and their count is always less generous than yours.

Come back before the estimate expires, even with nothing. A ten-second "still looking, bear with me" resets the clock. Silence does not.

If it's going to be longer than a couple of minutes, offer the callback instead — and then actually make it. An offered callback that doesn't come is worse than a long hold, because it converts a mild annoyance into a broken promise.

A blind transfer — pressing transfer and hanging up — is how callers end up in the voicemail of someone who is on vacation, or explaining their problem for the third time.

A warm transfer means staying on the line long enough to tell the person receiving the call who it is and what they want. It costs twenty seconds and it is the difference between a caller who feels handed over and one who feels passed around. The mechanics are in how to transfer a call and warm transfer.

Before transferring, say where you're sending them and why: "I'm putting you through to Dan in service, he handles scheduling — if we get cut off his direct line is 555-0142." Giving the number before the transfer is the detail nobody does, and it's the one that saves the call when the transfer fails.

Most messages fail on the same two fields. Write down, in this order:

1. Name, spelled back to them if there's any doubt.
2. Number, read back digit by digit. Always. This is the field that gets transposed, and a message with a wrong number is worse than no message because somebody spends ten minutes on it.
3. What they want, in their words rather than your summary. "Wants to know if you take Delta Dental" is actionable. "Insurance question" is not.
4. When they're reachable, because the callback that lands during their shift is a second missed call.
5. Who took it and when, so there's somebody to ask.

Read the whole thing back before you hang up. It takes fifteen seconds and catches nearly every error. There's a ready-made format in our phone message template.

The instinct is to explain. Explaining early reads as defending, and defending escalates.

The sequence that works is: listen without interrupting, say back what you heard, apologize for the experience without conceding fault you don't know about, then move to what you'll do. "So the technician didn't turn up on Tuesday and nobody called — I'm sorry, that's genuinely frustrating. Let me find out what happened and call you back within the hour."

That is not a script to recite; it's an order of operations. People calm down measurably once they're satisfied you've actually understood the complaint, and almost never before.

Two rules to hold: don't put an angry caller on hold if you can avoid it, and don't promise a timeline you can't hit. The second callback that doesn't arrive is the one that turns an annoyed customer into a review.

Close the loop out loud. Say what happens next, who does it, and by when: "So I've booked you for Thursday at 2, you'll get a text confirmation, and if anything changes call us on this number."

Then let the caller hang up first. It costs a second and it stops the half-finished "oh, one more thing" from being cut off.

If nothing was resolved, say that honestly along with the next step. "I don't know, I'll find out and call you tomorrow morning" is a better ending than a confident guess that turns out wrong.

Some etiquette failures aren't manners at all — they're structural, and no amount of training fixes them.

Answering within three rings requires someone free to answer. If one person covers the desk and the phone, the ring count is a staffing fact, not a courtesy one. See how many rings before voicemail.

Not sounding rushed requires not being rushed. A caller can hear a queue at the counter.

Returning calls the same day requires the messages to be legible and in one place.

Being reachable at all requires someone on the line outside 9-to-5, which most small businesses can't staff.

Worth separating the two kinds of problem before you train anyone. If your phone etiquette complaints are really a coverage problem, politeness training will not touch them.

Briefly, since people search for this too: if you're the one calling a business, say who you are and why you're calling in the first sentence, ask whether it's a good moment before launching in, and leave a voicemail with your number at the start and the end — the person replaying it shouldn't have to listen twice to catch it.

If you're calling about a job, a quote, or anything where they'll need to call you back, spell your name. It is the single most common reason callbacks don't happen.