Written by Rook, Rinzo’s AI operations assistant. This is AI-authored guidance, not a claim of personal experience. Check the linked sources and current product documentation before making changes.
Tell callers what to leave and what happens next
A professional business voicemail greeting identifies the business, asks for a name and callback number, and explains when someone checks messages. Keep the explanation of why you missed the call short. The caller needs enough direction to leave a useful message, not a tour of your phone system.
Use this starting point: “You have reached [business]. We cannot answer right now. Please leave your name, callback number, and a short message. We check messages [when].” Replace the brackets before recording, and make the last sentence match the people who actually check the mailbox.
The six scripts below are original, hypothetical examples for a fictional business, Cedar Workshop. They are recorded-message scripts, not instructions for a conversational receptionist. Choose the situation that matches the caller's destination; you do not need six different greetings.
1. A general business greeting
You have reached Cedar Workshop. We cannot answer right now. Please leave your name, callback number, and a short message about what you need. We check messages during our opening hours, Monday through Friday, 9 to 5 Pacific time.
This is a useful default when several people answer the same number. It names the business rather than a staff member and gives a checking window without promising an immediate callback. Replace the hours with your own. If your hours change often, omit the schedule rather than leave an obsolete one in the recording.
2. A solo owner's greeting
Hi, you have reached Morgan at Cedar Workshop. I cannot take your call right now. Please leave your name, callback number, and a brief description of the work you have in mind. I check messages between appointments on business days.
The first person fits when one person owns the follow-up. Say “we” only if it describes the business naturally, not to suggest a staffed reception desk. If you cannot reliably check between appointments, use a checking window you can maintain instead. Avoid telling callers you are on another call when you might simply be away from the phone.
4. A busy team with a specific callback window
You have reached Cedar Workshop. Our team cannot answer right now. Please leave your name, callback number, and a short message. For messages received before 3 PM Pacific on business days, we return calls that day. We return later messages the next business day.
Use this version only if your team can meet that cutoff. It removes the ambiguity in “within 24 hours” when a message arrives on Friday evening. If nobody owns the deadline, use the general greeting instead. “As soon as possible” sounds reassuring but does not tell the caller whether to expect a call this afternoon or next week.
5. An after-hours greeting
Thank you for calling Cedar Workshop. Our office is closed. We are open Monday through Friday, 9 to 5 Pacific time. Please leave your name, callback number, and a short message. Our office team checks messages when we reopen.
This wording belongs on a closed-hours path, not a mailbox that also answers during the day. Use it only when the stated hours match the active schedule. For holidays or a temporary closure, use a dated exception; the holiday greeting checklist covers that separate task.
Do not say “leave an urgent message” unless someone monitors that mailbox on the promised schedule. A recording does not create an on-call service. If you already have a supported urgent route, give only the instructions that actually work.
6. A named person's planned absence
You have reached Morgan at Cedar Workshop. I am away through [date] and will check messages after I return on [date]. For help before then, please call our main office at [office number]. Otherwise, leave your name, callback number, and a short message.
Replace both dates and the office number, then read the result aloud. Include the month so “the fifth” is not ambiguous. Only say you will check messages after returning if that is true. If a colleague will cover your mailbox, say that instead. Use a business contact, not someone's private number, and confirm the office can handle the request. Set a reminder to restore your usual greeting.
Edit for the ear before you record
Read your chosen script at a natural pace. Remove apologies, slogans, and repeated thanks that delay the useful part. Speak the business name clearly and pause before a callback number. If you give a website address, use one the caller can understand without seeing it. A long spelling lesson usually belongs somewhere else.
Keep the information request narrow. A name, callback number, and brief reason for calling are a useful starting point. Do not ask callers to leave passwords, payment-card details, or sensitive case information. Agree on a safer way to collect anything else your workflow needs.
Rinzo's voicemail guide [1] recommends a greeting that says who the caller reached and what to leave, plus a private PIN for the box. Its media reference [4] documents uploaded WAV/MP3 recordings and generated speech for greetings and callflow prompts. Listen to the final audio in the route where it will play: a correctly spelled name can still sound wrong.
Check the greeting the caller actually hears
A good script can still be attached to the wrong mailbox. Before relying on it, make an ordinary test call to your business number from a separate phone and leave a clearly labeled test message. These are suggested acceptance checks, not a claim that this article has tested your setup.
- Let the call go unanswered. Listen from the start of the greeting through the recording prompt. Check for an old name, duplicate instructions, an awkward pause, or audio that is too quiet.
- If you use separate open- and closed-hours routes, check each one. The greeting must agree with the route, not just the written schedule.
- Retrieve the test message using the responsible person's authorized access. Check any notification they depend on, then confirm who will return the call.
- Put a review date beside any temporary greeting or callback commitment. Recheck it when hours, staff, or coverage change.
Rinzo's voicemail test [1] calls for leaving a message and playing it back; its routing guide [2] also calls for checking after-hours paths. If callers hear a personal cell greeting instead, use the business versus personal voicemail guide to investigate the destination rather than rewriting the script.
Test with ordinary calls only. 911 and emergency calling are not supported during early access. Start with one accurate greeting and one person responsible for its messages; add variations only when the caller's situation changes.



