Why you can't rename a VICIdial Script ID after you create it

The Script ID is a database key, not just a label

When you assign a Agent script to a Campaign, VICIdial stores the Script ID — not the Script Name — as the reference in the campaign record. The same is true for inbound groups, Ingroup routing tables, and any related configuration. The Script ID is what ties everything together under the hood.

If VICIdial allowed you to rename a Script ID after creation, every campaign, group, and log record that stored the old ID would instantly point to nothing. The script panel on the agent screen would go blank with no warning. To avoid that class of silent breakage, the ID is locked at creation time.

What this means in practice

If you created a script with the ID SALV1 and later decide you want it to be SALES001, there is no rename option. Your only path is:

1. Create a new script with the ID SALES001 and copy the script text across.
2. Update every Campaign and inbound group that referenced SALV1 to point to SALES001.
3. Delete the old SALV1 script once all assignments have been migrated.

Skipping step 2 before step 3 is the usual source of problems — campaigns end up with a script ID that no longer exists.

Script Name is the flexible counterpart

The Script Name field — a 2–50 character display label — can be updated any time from the modification page. It is not used as a system reference anywhere, so changing it carries no risk. Use the Script Name as the human-readable description that can evolve. Use the Script ID as the stable, permanent machine reference.

This is why picking a thoughtful Script ID up front matters. A well-chosen ID like RETOB2025 tells you the purpose (retention outbound) and a rough vintage without needing to read the Script Name.

Migration flow when a Script ID needs to change

flowchart TD
  A[Old Script ID needs changing] --> B[Create new script with correct ID]
  B --> C[Copy script text to new script]
  C --> D[Update all campaigns pointing to old ID]
  D --> E[Update all inbound groups pointing to old ID]
  E --> F{All references updated?}
  F -- No --> G[Find remaining references and update]
  G --> F
  F -- Yes --> H[Delete old script]
  H --> I[Migration complete]

The Script Comments field as a change log

Script Comments (up to 255 characters) can serve as a lightweight change log. Entries like "migrated from SALV1 June 2025" or "replaced free upgrade offer" give the next admin context without needing to dig through Call recording archives or external documentation.

Before creating any script, review the naming guidelines in picking a VICIdial Script ID: the naming rules that trip people up. Getting the ID right the first time avoids this migration entirely.

For the full context of how scripts, campaigns, and the agent screen fit together, the VICIdial agent screen configuration guide has the complete picture.

If you are planning a VICIdial deployment and want to avoid script management headaches from the start, see pricing for managed hosting options where this is handled for you.