Business phone numbers and phone menus for the United States and Canada. FRES(510) 288-6288[email protected]Sign in

Home › Call-flow templates › Role mailbox greeting

Call-flow template

Role mailbox greeting: a call-flow template

For a shared role such as billing, bookings or service, where callers can leave a message for whoever owns that work.

Last checked 14 October 2026 · 3 cited sources

Ready-made call-flow templates

When this flow fits

For a shared role such as billing, bookings or service, where callers can leave a message for whoever owns that work.

Keep each route tied to a caller need. With Auto Attendant each option does one thing: it rings up to three phones one after another (never together), takes a voicemail, or plays a message and hangs up; a line can also skip the menu entirely. A forwarded call shows your business number as caller ID, and the team returns calls from its own mobiles.

Why this flow is built this way

A role mailbox is voicemail for a job, not a person: billing, bookings, service. It lets a caller leave a message for “whoever owns this” without needing to know who that is this week, and it lets the business change who owns the work without recording a new greeting each time. The greeting should name the role and ask for the one reference the team needs to act, such as an invoice number, an appointment date or a job address.

Because several people may read the inbox, a role mailbox needs a rule for who replies. The simplest is first come: whoever opens the message claims it with a one-line reply to the group. Without a rule, either nobody calls back or two people do.

Flow and keypresses

The diagram shows what the caller hears and where each choice leads. The count is the number of keypad selections from the first menu to that destination; a submenu adds another press.

Name the role, request the details needed to act, state the callback expectation.

Next: Voicemail emailed to everyone who covers the role, with the MP3 attached

Caller destinationKey sequenceKeypressesRoute in this example
Default routeNo keypress0Voicemail emailed to everyone who covers the role, with the MP3 attached

Original script wording

Replace the shaded fields with details your callers need. Do not read them aloud as written. Word count and duration are calculated from each script; spoken time is estimated at 150 words per minute, so pauses and keypad instructions may make the spoken greeting longer. Auto Attendant reads your wording in a text-to-speech voice; you type the words rather than recording them.

Role mailbox · 42 words · about 17 sec at 150 words per minute

You have reached the team or role mailbox at Business name. Please leave your name, callback number and the relevant invoice, appointment or job reference after the tone. The team will review your message and get back to you realistic response window.

Shaded text is a fill-in field: replace it with your own.

A worked example

Illustration: a landscaping firm uses a billing role mailbox. The greeting says: “You have reached the billing team at [Business name]. Please leave your name, number and invoice number.” The transcript goes to the office manager and the owner. The office manager replies in the inbox with “mine” when she takes it, and the owner ignores it unless a message sits for more than a day.

The weak design sends the role mailbox to a single person’s email. When that person is on leave, billing questions pile up. Pointing the mailbox at a shared address or a group that survives staff changes avoids that.

Timing, options and common mistakes

Use the same unanswered-call timeout as the route leading to this mailbox unless the role has a different coverage pattern.

Create separate role wording only where the caller needs to provide different information.

  • A role mailbox should be monitored by more than one person where possible.
  • Do not ask callers to leave sensitive payment details in a voicemail.

Say the option before its key, put the most frequent caller need first, and repeat the key choices at the end. A practical starting point is no more than about four top-level options: callers must listen, remember the choices and select one. Use a submenu for a less common branch rather than making every caller hear every detail.

For a full routing walkthrough, see call routing and menu design. An Auto Attendant menu has up to seven options; each rings up to three phones in turn, takes a voicemail or plays a message. The menu can be in English, French or Spanish. Voicemails are emailed in the business’s chosen language with the MP3 attached, followed by a transcript in the language of the message.

Standards and rules behind it

Access to a shared mailbox is a security decision. The HIPAA Privacy Rule’s minimum-necessary standard requires covered entities to identify the persons or classes of persons in their workforce who need access to protected health information 1, which is a useful model even outside healthcare: give mailbox access to the people who need it. The Gramm-Leach-Bliley Act sets a continuing obligation for financial institutions to protect the security and confidentiality of customers’ nonpublic personal information 2.

NIST’s Small Business Cybersecurity Corner gathers cybersecurity guidance and resources for small businesses 3. Review who belongs to the mailbox group each quarter, and remove people who have left.

This is general information, not legal advice. Rules differ by state and change; confirm anything that affects your business with the source or an adviser.

Test it before you publish it

  • Name the role in the greeting and ask for one reference number.
  • Point the mailbox at a shared address, not one person.
  • Agree a first-come claiming rule.
  • Review mailbox membership every quarter.
  • Test by leaving a message and timing the reply.
Put a clear menu on your business number
Use these words as a starting point, then point each option at the phones, voicemail or message that fit your team.
Get started

Further reading

Longer research pieces on this topic, each with its own source list and a downloadable PDF.

Sources

Every regulatory and pricing claim on this page links to the primary source it came from. Figures were checked on the date shown at the top of the page; rules and prices change, so verify before relying on one.

  1. 45 CFR § 164.514(d), Minimum necessary requirements. Retrieved 14 Oct 2026
    https://www.law.cornell.edu/cfr/text/45/164.514
  2. 15 U.S.C. § 6801, Protection of nonpublic personal information (Gramm-Leach-Bliley Act). Retrieved 14 Oct 2026
    https://www.law.cornell.edu/uscode/text/15/6801
  3. NIST, Small Business Cybersecurity Corner. Retrieved 14 Oct 2026
    https://www.nist.gov/itl/smallbusinesscyber