Skip to content
ProductOpen console

Changing the voice

Changing a voice looks like picking a different name from a list. It is closer to re-recording every fixed line your agent owns.

Every phrase you have authored is recorded in a specific voice. Change the voice and none of those recordings are usable. They are not wrong, they are someone else, and playing them in a call that is otherwise in the new voice would be worse than not having them at all.

ONE VOICE CHANGE, EVERY PHRASENew voiceone settingGreetingAcknowledgementAcknowledgementAcknowledgementIdle nudgeIdle nudgeFarewellFixed answerevery one of these has to be recorded again before a caller needs it
The count is per language. An agent speaking two languages with seven phrases each has fourteen recordings to remake, and only the language whose voice you changed is affected.

Picking a voice does not change anything. The console first shows you what the change would cost:

  • How many phrases are affected, in that language.
  • How much audio that is in total, as the caller experiences it.
  • How long re-recording takes, which is the number that decides whether a caller is going to wait.
  • Whether those figures are measured or estimated. Before a phrase has ever been recorded, its length is calculated from the text. The console says so rather than presenting a guess as a measurement.

You confirm against those numbers. Nothing moves until you do.

The new recordings are made before the change goes live. Until they exist, calls keep using the previous voice.

This is the part worth understanding, because the obvious order is wrong. Switching the voice first and recording afterwards produces a window where some phrases exist in the new voice and some in the old, and a caller in that window hears two different people in one conversation. Recording first means the worst case is a call that sounds exactly like yesterday.

You can change a voice three times per language, per week. An owner can override the limit when there is a real reason to.

The limit is not about cost. A voice is what your business sounds like, and a business that sounds different on Tuesday than it did on Monday reads as unreliable to the people who call it more than once. Three is enough to audition alternatives and settle. It is not enough to keep fiddling.

When the allowance is used up, the console says how many changes remain and when the window resets.

Voice changes are logged: which language, from which voice to which, by whom, and when. Two reasons this matters. Callers report that “it sounds different” long after anyone remembers making a change, and a voice that turned out to mispronounce something specific is worth being able to trace back.

  • Audition before you commit. Listen to a real phrase of yours in the candidate voice, not a vendor sample of somebody else’s sentence. Your business name is usually where a voice fails.
  • Change one language at a time. Two changes at once means two sets of recordings and no way to tell which one people are reacting to.
  • Do it when the line is quiet. Not because anything breaks, but because the one caller who might wait should be nobody.
  • Re-read your phrases afterwards. A line written for a brisk voice can sound curt in a warm one. The words are half of the impression.

Omazy CX documentation. One voice. Every channel. Always on.

Founded by Mosthofa Imran · imran@omazy.ai