Text to Speech

The Text to Speech (Render TTS) element converts written text into spoken audio, playing it to the caller at a defined point in the IVR flow. Unlike a Play element which requires a pre-recorded audio file, TTS lets you type the message you want the caller to hear directly into the element — including dynamic content pulled from call or lead data.


Connections

ConnectionDescription
I – InputThe entry point for this element. Connect from the preceding element in your IVR flow.
O – OutputThe path taken once the text has been spoken to the caller.
E – ErrorThe path taken if the element encounters an error.

Settings

FieldDescription
NameGive the element a clear name so it is easy to identify within your IVR flow.
DescriptionOptional. Add a note to explain the element's purpose — useful in more complex flows.
Agent Can See ThisWhen enabled, agents can transfer a live caller directly to this element via the IVR Transfer option.
Supervisor Can See ThisWhen enabled, the element is visible in the IVR Transfer list for users with a Supervisor role. It remains hidden from all other users.
Result CodeAssign a result code to this element to track calls that pass through it.
TextEnter the text you want spoken to the caller. This can be static text, dynamic content using double curly brackets {{ }}, or a combination of both. See Dynamic content below for details.
VoiceSelect the voice to use from the dropdown. By default, two Windows voices are available. Additional voices and languages can be added — contact your account manager for further details.

Dynamic content

The Text field supports dynamic content, allowing you to include caller or lead-specific information in the spoken message. To use a dynamic field, wrap the field name in double curly braces — for example, {{call.name}}. This is replaced at runtime with the actual value for that call.

Dynamic fields can be used on their own or within a sentence. For example:

This message is for {{call.name}}. If you are {{call.name}}, press 1.

The following fields are commonly used for dynamic content:

FieldDescription
call.ReferenceIDThe reference or account ID for the lead.
call.NameThe first name or full name of the lead.
call.Name2The last name, company, or other value stored in the Name2 field.
call.AddressThe street address for the lead.
call.CityThe city for the lead.
call.PostalCodeThe postal code for the lead.

Primary mapped fields to a lead


Formatting content

You can control how certain values — such as dates, times, numbers, and addresses — are spoken by applying a format tag within the double curly braces, separated by a colon. For example: {{call.PostalCode:SpellOut}}.

Format tagApplies toExample outputDescription
SpellOutAny fieldM-1-2-A-PSpells out a word or number as individual characters. Useful for postal codes or account numbers.
OrdinalIntegers1st, 2ndExpresses a number as a position (1st, 2nd, 3rd, etc.).
LongDateDateMonday, June 11, 2018Expresses a date including day of week, month, day, and year.
MediumDateDateJune 11, 2018Expresses a date including month, day, and year.
ShortDateDateJune 11Expresses a date as month and day only.
DayOfWeekDateMondayExpresses just the day of the week.
DayDate11Expresses just the day of the month.
DayOrdinalDate11thExpresses the day of the month as an ordinal value.
MonthDateJuneExpresses just the month.
YearDate2018Expresses just the year.
TimeTime2:33 PMExpresses a time value in 12-hour format with AM or PM.
Time24Time14:33Expresses a time value in 24-hour format.
TelephonePhone number0330 159 6570Expresses a string of digits as a phone number in the way a person would naturally say it.
AddressAddress12-49 Saint Lucie StreetExpresses a street address in the way a person would naturally say it.
CurrencyMoney£39.45Applies a currency symbol to a value.

Related articles