What the TTS ID and TTS Name fields are

Every TTS (text to speech) entry in VICIdial has two naming fields you must fill in before the record will save: the TTS ID and the TTS Name. They look similar but do different jobs, and the rules on each are strict enough that they trip up newcomers. This post explains what each field is for and the limits on both.

TTS ID

The TTS ID is the short name of the entry and has to be a unique identifier. It is the value the system uses to reference the entry, so it has tight character rules.

• Two to fifty characters.
• Numbers, letters, and underscores only.
• No spaces and no punctuation.

TTS Name

The TTS Name is the more descriptive label. It is a short summary of what the entry says or does and exists for humans scanning the list, not for the system to reference.

• Two to one hundred characters.
• Free text, so you can write a real sentence like Holiday closure announcement.

Where you see both

The Text To Speech list shows the TTS ID, the name, the active status, and the start of the prompt text, with a modify link per row. Both fields are required: if either is blank the form will not save. Think of the ID as how the dialer finds the entry and the name as how you recognise it.

The split exists for a reason. The ID is locked down to numbers, letters, and underscores precisely because other parts of the system reference it, and a stray space or symbol there can break that reference. The name has no such job, so it is free text and can be as descriptive as you like within its hundred-character limit. Keeping the ID terse and the name verbose gives you the best of both: a stable key the dialer trusts and a label a human can scan.

A small naming convention pays off as the list grows. Group related entries with a shared ID prefix, such as vm_ for voicemail messages or ivr_ for menu prompts, and write the name as a plain sentence describing exactly what the entry says. Future you, and anyone who inherits the system, will find the right entry far faster.

flowchart TD
  A["New TTS entry"] --> B["TTS ID"]
  A --> C["TTS Name"]
  B --> D["Unique key, strict chars"]
  C --> E["Human-readable label"]
  D --> F["Call flow references entry"]
  E --> G["You spot it in the list"]

This mirrors how Music on hold entries also split a strict ID from a descriptive name, so the pattern carries across the admin. A clean ID matters because it is what an IVR (interactive voice response) step or Call menu points at when it plays the entry.

If you have not created an entry yet, follow adding a TTS entry, and for how all of this fits with prompts and the audio store see the audio and TTS guide. Want a dialer that is wired and ready in under 40 seconds? See the plans.