What should the recorded-call announcement actually say, and where should it play?

Placement is the part that usually goes wrong

Wording gets all the attention and placement causes all the problems. A common configuration puts the disclosure after the department menu, which means a caller has already spoken their name and problem before hearing it. Another puts it only on the main line, leaving every direct-dial number silent.

The rule of thumb: the disclosure should be the first substantive thing a caller hears, before any prompt that invites them to speak.

Keep it short enough that people hear it

Long legal language does not increase comprehension; it increases the number of callers who mentally tune out or press zero. One sentence, spoken at a normal pace, in the same voice as the rest of the greeting, is more likely to actually register than a paragraph.

There is also an operational cost to length. Every second before a caller reaches a human is a second during which some share of callers hang up, and that share is higher on urgent service calls than on almost any other kind of inbound. A disclosure that adds fifteen seconds to a greeting is buying compliance with abandoned calls, which is a trade you should make deliberately rather than by accident.

Avoid stacking it with other notices. A disclosure buried in a run of promotional messaging is functionally invisible.

Test every published number on a schedule

Phone systems drift. Someone adds a new tracking number for a campaign, provisions a location, or rebuilds a call flow, and the announcement quietly stops playing on one path. This is not hypothetical; it is the normal state of a system with more than a few numbers.

Make it an operational check. List every number you publish — website, Local Services Ads, truck wraps, Google Business Profile, direct mail, vendor portals — and dial each one on a fixed cadence. Log the result. It takes an hour and it is the only way to know.

What the announcement does not cover

A recording disclosure addresses recording. It is a separate question whether and how you tell customers that recordings are later analyzed by software, or that they might be speaking with an automated system. Those are different disclosures with different triggers, and conflating them tends to produce a greeting that satisfies nobody.

If you are adding analysis on top of recording, treat the disclosure review as part of the project rather than an afterthought, and get the final language reviewed by your own counsel.