Skip to content
Ringfully

Blog

The six messages a phone line needs

Most business lines have two recordings and need six. What each one has to say, which two go missing every time, and how to write the set in one sitting.

Owner and CEO · 6 min read ·

Most business phone lines have two recordings and need six: open, the menu, waiting, closed, holidays and voicemail. The two that go missing are the holiday message and the one a caller hears while waiting. Both leave a caller listening to something wrong, and neither costs more than an afternoon to fix.

The six, and what each one has to do

During opening hours. Five seconds. Who they have reached, and that they are in the right place. Nothing else belongs here, because the menu is about to ask them for a decision and they cannot hold a sentence about your history at the same time.

The menu. What the caller wants, in their words, and the key for it. Not your departments: nobody rings a plumber to reach Estimating, they ring to get a price. Read straight after the greeting with no pause, because a gap sounds like the recording has finished.

While they wait. The one message that is nothing but reassurance. It exists because silence on a held line reads as a dropped call, and a caller who thinks they have been cut off rings somebody else rather than ringing you back.

Outside opening hours. When you are open, when you are back, and what to do now. This is the message you will change most often, so keep the words written down somewhere a colleague can find them.

On a holiday. The same shape, with the holiday named and a different return date. It replaces the closed message on the days you choose.

Voicemail. The mailbox itself, reached either from the menu or after nobody picked up. Ask for three things, never four.

The two that go missing

Nobody sets out to skip the holiday message. What happens is that the closed message gets recorded on the day the line is set up, it says back at nine tomorrow morning, and it is correct three hundred and thirty days a year.

On the other thirty it is a lie, and it is a lie told to somebody who took the trouble to ring you on a day off. They are told to ring back tomorrow at nine. They do. They get the same recording. The second time, they stop.

The waiting message goes missing for a different reason: it does not feel like a message. It feels like hold music, and hold music is a setting somebody ticked once. But a caller thirty seconds into silence has no way to tell being queued from being disconnected, and the difference between the two is one sentence saying which it is. What a caller hears while nobody is free is a decision whether or not you make it deliberately.

Say the same thing six times

Here is the part that only shows up when you write all six together: they have to agree.

The business name is said the same way in five of them. The hours in the opening greeting are the same hours in the closed message. The callback promise in the voicemail is the same promise as the one after the tone at the end of the closed message, because a caller who hears both should not be doing arithmetic about which one you meant.

That consistency is almost impossible to get when the messages are written one at a time, months apart, by whoever was free. It is nearly automatic when they are written in one sitting from one set of answers, which is what the phone message pack generator does: you answer once, and the same name, hours, return date and callback promise land in every message that needs them.

The name, and how it gets said

The person recording your greeting is often not the person who named the business.

A surname, a street, a word from another language: all of them get read the way they are spelled by somebody in a hurry, and then every caller for two years hears a version of your name that nobody in the building uses. It is a small thing that sounds exactly like a company that does not care very much.

Write the pronunciation down beside the script, not in it. Not as phonetic notation nobody can read, just as it sounds: NORTH-line, like the road. Whoever holds the microphone reads the direction, records the name, and the problem never comes up again.

The keys your menu prompt names

The one message that can be checked rather than merely proofread is the menu.

It names a set of keys. Your menu answers a set of keys. Those two sets drift apart with total reliability: somebody adds a department and updates the routing but not the recording, or re-records the greeting from a document that turns out to be an old draft. Six months later the message says press 4 for deliveries and 4 does nothing, or 7 reaches the workshop and nobody has ever been told.

Both halves read perfectly on their own, which is why nothing catches this. The recording is fine. The routing is fine. Only together are they wrong, and the only person who finds out is a caller who does not tell you. The phone menu builder runs that comparison in both directions on a menu you type in, and how a published menu actually decides where a call goes is the other half of the same question.

Writing them, and then recording them

Write all six before you record any of them. Read each one out loud at the desk first, because a sentence that reads well on a screen can be unsayable, and you will find out either now or in a take you have to do four times.

Then record: one file per message, in a quiet room, at the pace you would use with somebody standing at the counter. Slower than feels natural. Whoever has the clearest speaking voice, not whoever has the title.

Phone systems want a specific file rather than whatever your phone produced: usually 8 kHz, one channel, in the encoding your vendor asks for. The phone audio converter does that in the browser without uploading anything.

One thing worth knowing before you go looking for a shortcut: a generated voice is not free. Amazon's own published price for neural speech is sixteen US dollars per million characters outside its free allowance, which is real money once six messages are regenerated every time your hours change, and the speech built into a web browser cannot reliably hand you a file at all. A colleague with a decent phone and a closed door is genuinely the better answer for a business your size.

The last thing is not a recording. A holiday message that nobody switches on is a holiday message nobody hears, so the six files are only half of it: the other half is the hours behind them, deciding which one a caller meets, and one switch for the day the snow closes you. If changing that means raising a ticket and waiting a week, the drift is guaranteed, which is worth thinking about when you look at what a phone system costs. Not the monthly figure. Who is allowed to edit it.

Questions people ask

What messages does a business phone line need?
Six. A greeting for when you are open, the menu that follows it, something for a caller who is waiting, a message for outside your hours, one for a holiday, and the voicemail itself. Most lines have two of them, usually the opening greeting and the voicemail, both recorded years apart by different people.
What should a business voicemail greeting say?
Who they have reached, what to leave, and what happens next. Name, number and what the call is about is three things and about as many as a caller will remember. Then a promise you can keep: we ring you back the same working day. A greeting that asks for a message and promises nothing is why people hang up and try a competitor.
Do I need a separate message for holidays?
Yes, and it is the one almost nobody records. Your closed message says when you are open again, and on a statutory holiday that sentence is wrong. A caller told to ring back at nine tomorrow morning, on a day you are shut, rings back at nine and gets the same recording. One extra file fixes it for every holiday in the year.
How long should a phone greeting be?
The greeting itself, about five seconds. The menu after it, under twenty. A prompt runs at roughly two and a half words a second when it is read properly, so forty words is sixteen seconds and a caller who has waited that long starts pressing 0 to escape. If the list will not fit, the answer is fewer options rather than faster reading.