Last updated: September 12, 2026
What a call center greeting script has to do
A call center greeting script carries four jobs in about four seconds. It names the business, names the agent, signals that the caller reached the right place, and starts any disclosure the law or the client requires, such as a recording notice or the TPMO disclaimer on a Medicare call. Greeting is usually the first scored line on a scorecard.
Four seconds is roughly what you get before the caller starts talking over the greeting. Inside that window they have to learn which business picked up, get a name for the rest of the call, and pick up some signal that this line handles what they are calling about.
On a recorded seat there is a fourth job, and it almost never comes from training. It arrives from a compliance review, or from a client's legal team reading an account script, and gets bolted onto a greeting already at capacity. What comes out is the greeting every caller has heard, delivered fast enough that the first half is unintelligible.
Scripts by call type
Eleven versions cover most seats. Bracketed placeholders are the parts that change per company or per account. Change the wording freely; the element column beside each script is the part to keep.
| Call type | Script | Required elements | Scoring note |
|---|---|---|---|
| Inbound, general support | "Thanks for calling [company], this is [agent]. How can I help you?" | Company name, agent name, an offer to help | Score the parts separately, since a greeting marked failed tells a supervisor nothing |
| Inbound, recorded line | "Thanks for calling [company], this is [agent]. This call is recorded for quality assurance. How can I help you?" | Everything above plus the recording notice where consent law requires it | Only the notice belongs on the auto fail list |
| Inbound sales | "[company], this is [agent]. Are you calling about [product line], or something else?" | Company name, agent name | Score whether the routing question came before the pitch |
| Answering service, client account | "Thank you for calling [client business name], this is [operator]. How may I direct your call?" | The client's exact business name from the account script, operator name | The wrong business name zeroes the call whatever follows |
| Answering service, after hours on-call | "[client business name] after hours line, this is [operator]. Is this an emergency, or can it wait for the office in the morning?" | Account name, operator name, the account's own triage question | Score the triage question on wording and on position, ahead of capture |
| Closed line, voicemail | "You have reached [company] after business hours. Leave a name, a number, and what you need, and somebody returns the call by [time]." | A callback window the floor can actually hit | Nothing in the recording to score. Score the callback against the window it promised |
| Transfer | "I am putting you through to [department] now, and that line is recorded for quality assurance." | Where the caller is going, plus a notice when the receiving line records | Score whether the caller heard both before the hold started |
| Callback on a message | "Hi, this is [agent] at [company], returning your call about [reason]. Is now still a good time?" | Agent name, company name, the reason from the original message | Compare the stated reason against the message, which is where accuracy breaks show |
| Outbound sales, recorded | "Hi [caller], this is [agent] with [company]. This call is recorded for quality assurance. You asked about [reason] on [date]. Do you have two minutes?" | Agent name, company name, recording notice ahead of the first question, the basis for the call | Score the second the notice landed against the second the first question did |
| Medical account | "Thank you for calling [practice name], this is [agent]. Can I get your first and last name?" | The practice name from the account script, plus the identity step that account's instructions require | Score identity as its own line, separate from the greeting |
| Medicare marketing | "Hi, this is [agent] with [agency]. This call is recorded. [TPMO disclaimer in current CMS language.]" | Recording notice, and the disclaimer before any plan benefit is named | The scored fact is the disclaimer's position against the first benefit, rather than the clock |
All eleven rows download as a CSV with the element column attached.
The greeting strings load into a vocabulary set the same way a phrase library does, which is what makes the criterion checkable later.
Three of those elements are convention. No law makes an agent say their own name, and none requires the offer to help at the end. They stay because a caller holding a name will use it, and because a greeting without a handoff line leaves both people waiting.
The recording notice is the one part of an ordinary greeting that can carry a legal obligation, and what it has to say depends on which states the call touches. A Medicare marketing call adds a second. Per account requirements, like the business name an answering service picks up in or the identity check a medical practice wants, come from a contract rather than a statute, which makes them just as binding on the floor and a lot easier to change.
Answering a call under a client's name
An operator on an answering service floor picks up in somebody else's business name, then does it again forty seconds later under a different account. Greeting is the criterion most exposed to that, because every element inside it changes per account while the shape holds still.
Two variants cover most boards. The daytime version routes, and the after hours version triages before capturing anything, because the account bought that line so somebody could decide whether to wake a technician.
Whether the operator identifies as the answering service belongs to the account. Some clients want it said out loud, a medical practice usually wants the opposite, and that puts the do-not-say list on equal footing with the greeting string. The answering service scorecard has the criterion with points on it, and QA for telephone answering services covers the rest.
Medical and HIPAA sensitive greetings
A greeting on a medical account collects a name and a callback number without inviting clinical detail the operator has no reason to hold. Practices differ on where that line sits, and the account script is the authority.
What holds across most of them is that the identity step happens before a condition or an appointment reason gets written down. Keep it as its own scorecard line, so a call that skipped the check does not score as a clean open. HIPAA and recorded calls covers the recording side.
Medicare marketing calls
A Medicare marketing, sales, or enrollment call carries the TPMO disclaimer, and 42 CFR 422.2267(e)(41)(ii) requires it verbally during sales calls prior to the discussion of any benefits. The older standard tied delivery to the first minute and no longer sets the trigger. An agent who opens with the disclaimer is fine. The harder case is the one trained to fit it inside sixty seconds, now working against a trigger that moves with the conversation.
CMS owns the wording and this page does not reproduce it. What CMS requires on recorded calls carries both versions of the language and the retention rules attached to them.
The recording disclosure line
Where the notice sits inside the greeting is a placement question with a legal consequence on the end of it. Deliver it after the caller has explained why they called and the notice arrived too late to be a choice.
Consent rules vary by state, and a call crossing a state line answers to more than one of them. State recording disclosure rules carries the enumeration, and five disclosure scripts with their placement rules carries the wording. Neither page is legal advice, and your final line goes past your own counsel before it reaches the floor.
The timestamp matters six months later, when a caller says nobody told them. A transcript showing the notice at 00:03 of a call that ran four minutes settles that conversation. A monthly average showing 96 percent disclosure compliance settles nothing, because the dispute is about one call.
Scoring the greeting
On a 100 point scorecard with the greeting criterion, the branded greeting line is worth 5 points and the recording notice is a separate 5, inside a 15 point opening section. That is deliberately small for the thing every trainer spends the first morning on, and we argued about it. Ten is defensible on an account with a long required open.
Weight the greeting at 40 and you have told the floor that the open matters more than the callback number read back digit by digit. An agent can deliver a flawless greeting on a call that captured the wrong phone number, and the total should say that call failed.
A missed disclosure is the exception, and it belongs on the auto fail list rather than in the points. Zeroing a call says one thing very clearly, so every extra row on that list weakens the ones that earned their place.
Greeting is the easiest criterion in QA to check automatically, because every element is a rule. Either the business name appeared or it did not. Aircall and StackAI both describe automated scoring as reliable on rule based criteria and shakier on tone, which puts a greeting at the easy end. CallSniper scores it against the greeting string stored for that account, with a timestamp and a confidence value on each line, so a disputed deduction gets settled by opening the call at that second.
Exact matching has a failure mode worth knowing about. An operator who says the account name correctly and reorders the rest gets flagged on a call that was fine. Loosening the criterion wording fixes that, and no confidence threshold does.
What to fix before you rewrite the words
A perfect greeting delivered after four rings by somebody out of breath fails anyway, and no rewrite of the script reaches that. The things sitting in front of the words get checked first.
Start with how long the caller waited. Count the rings and the queue prompt together, since the caller does not separate them, and the greeting lands on whatever mood that wait produced. Wrap time is the other one. An agent picking up two seconds after the last call reads the greeting at the speed of somebody still typing, and the caller hears the speed instead of the words.
Pace is the one nobody measures. Read your greeting out loud at the tempo the recordings show, and time it. Four seconds of required elements delivered in under two is a compliance line nobody can parse, which is worse than a shorter script said clearly. Cutting an element is usually the honest fix, and on a regulated account the one you get to cut is whichever the law left alone. That decision belongs to whoever wrote the account script.
Then rewrite. Pull ten recent calls on one account, count how many opened with every required element, and rewrite only the element that failed most often. A whole script rewrite buys you a floor of agents relearning lines that were already working.
A first pass on your own audio does the counting on your own recordings, scored against your own greeting wording, and starts without a phone system integration because the audio uploads straight out of whatever your platform exports. The pilot costs a fixed pilot price.
Frequently asked questions
What should a call center agent say when answering the phone?
"Thanks for calling [company], this is [agent]. How can I help you?" On a recorded line the notice goes between the agent's name and the offer to help, so the caller hears it before explaining anything.
How do you greet a caller as an answering service?
In the client's business name, word for word from that account's script, followed by the operator's own name and a routing question. Everything in the line changes per account, including whether the operator names the answering service at all, so score it against the account rather than a house standard.
Do you have to tell someone the call is being recorded?
It depends on the consent rule in every state the call touches, and a call crossing a state line answers to more than one. The practical posture is a single line that satisfies the strictest state you dial into, placed before the caller says anything substantive. State recording disclosure rules has the detail, and your own counsel signs off on the wording.
What is the TPMO disclaimer and when is it read?
It is the CMS required statement that a third party marketing organization does not offer every plan available in the caller's area. 42 CFR 422.2267(e)(41)(ii) requires it during sales calls prior to the discussion of any benefits, so the older first minute timing no longer sets the trigger.
How many points should a greeting be worth on a scorecard?
Five out of a hundred on most forms, or up to ten when the account has a long required open. Push it past fifteen and the score starts rewarding a clean open on a call that took down the wrong callback number.
Sources
- Trinsic feature sheet and call notes, 2026-08-27 through 2026-09-10. Per account scorecards, stored greeting strings, timestamps, confidence values, and manual upload verified internally.
- 42 CFR 422.2267(e)(41)(ii), TPMO disclaimer content and timing. Read from primary text on 2026-09-09.
- The earlier first minute disclaimer timing. From agent facing summaries rather than superseded primary text, unverified.
- Aircall and StackAI on rule based criteria scoring more reliably than tone. Third party, unverified.
- Consent rules varying by state. Summarized here, enumerated on the state law page, unverified against current statutes.
- The 5 point greeting weighting and the eleven scripts themselves. Editorial judgment, with no outcome data behind it.