Free recording tool
Paste a draft, choose a speaking pace, and see how long the greeting may take to record. The checker also flags a few common filler phrases without uploading your words.
Free in-browser check
Estimated time
21sec
Word count
47
A practical working range for many routine small-business greetings.
Phrases worth reviewing
No common filler phrase was detected. Still check that every sentence changes what the caller knows or does.
Timing is an estimate based on word count and the pace you select. Pauses, names, phone numbers, and dates can make the recording longer.
Direct answer
A routine greeting often needs only the business identity, availability boundary, response window, and one request. Temporary closures can run longer because exact dates and monitoring limits reduce confusion.
Editorial benchmark
Our 18–32 second focused band is a working editorial range, not an industry standard. If the caller needs a date or handoff to act safely, keep it. If a sentence only sounds polite, cut it.
Worked timing decision
This constructed after-hours greeting includes identity, operating hours, routing information, and a callback deadline. It assumes the team really reviews messages each weekday and can return them by noon; replace that promise if your operation cannot keep it.
Thanks for calling Northstar Cleaning. You reached us outside our regular hours of Monday through Friday, 8 AM to 5 PM. Leave your name, number, ZIP code, and the cleaning service you need. We review new messages each weekday morning and will call back by noon.
| Pace | Estimated speech time | What to check |
|---|---|---|
| 120 words/min | 23.0 seconds | Does a slower pace add helpful pauses or needless delay? |
| 135 words/min | 20.4 seconds | Can the listener retain the details without the written script? |
| 150 words/min | 18.4 seconds | Are names, ZIP code, hours, and the deadline rushed? |
The 135-word pace yields about 20.4 seconds, not the previously stated 27 seconds. This correction is arithmetic, not evidence that 20 seconds is optimal. Try the same text in the checker, record it, and compare the actual duration with the estimate.
The table keeps one decimal place; the checker rounds estimates up to the next whole second, so this draft displays 21 seconds at 135 words per minute. Paste this exact example: the checker’s separate reset sample includes an extra “Please,” so its word count differs by one.
The normal callback routine is already predictable.
Thanks for calling Harbor Mobile Detailing. We may be working on a vehicle. Leave your name, number, vehicle type, and preferred service day. We return new inquiries after 3 PM on weekdays.
The caller needs to know when messages are reviewed.
You’ve reached Greenline Landscaping after hours. Leave your name, number, neighborhood, and whether you need maintenance or project work. We review new messages the next business morning and return estimate calls between 3 and 5 PM.
A longer message prevents uncertainty about reopening.
Thanks for calling Fieldstone Photography. The studio is closed through Monday, July 6, and messages are not monitored during the closure. Leave your name, number, and event date. We will begin returning inquiries in the order received when the studio reopens on Tuesday, July 7.
For measured durations rather than this arithmetic example, see the 12-recording timing lab. Those are controlled synthetic recordings, not a study of live callers or an approval benchmark.
Guide consolidated and reviewed October 8, 2026. The former length article now opens this section.
Questions before recording
There is no universal limit. Call Safety Guide uses 18–32 seconds as a practical editing range for many routine greetings, then allows more time when dates, a closure, or a real handoff must be explained.
It divides the script word count by the speaking pace you select. The result is an estimate because pauses, names, numbers, and emphasis can change the final recording.
No. The calculation runs in your browser. The tool does not submit the script to a Call Safety Guide database.
Check the worked timing example, or decide the callback promise first with the Promise Planner.