What the five Custom User Fields are for

Every VICIdial user record carries five free-form slots called Custom User Fields. They are not tied to any built-in behaviour; they exist purely so you can stash arbitrary information about an agent and then pull it back out where you need it. The payoff is that you can pipe that data straight into the Agent screen web forms and scripts without writing any custom code.

What the fields hold

There are exactly five, and you can put whatever you like in each one. They are blank by default. Because they are plain text fields on the user, they are perfect for per-agent values that VICIdial has no native concept of: an external employee ID, a team code, a regional flag, a partner reference, or a licence number for a regulated Agent. Whatever your downstream systems care about, the five slots give you somewhere to keep it next to the rest of the user record.

How you read them back

The useful part is the naming. The five fields are exposed as user_custom_one, user_custom_two, user_custom_three, user_custom_four, and user_custom_five. You reference those names in the web form addresses and scripts attached to a campaign, and VICIdial substitutes the logged-in agent's values when it builds the URL or renders the Agent script. So a single campaign-level URL can carry different data for each agent who logs in.

flowchart LR
  A[Manager fills user_custom_one to five] --> B[Stored on user record]
  B --> C[Agent logs in]
  C --> D[Campaign web form or script loads]
  D --> E[VICIdial substitutes the five values]
  E --> F[URL or script carries agent data]
  F --> G[External CRM or page receives it]

A practical example

Say your external CRM expects each call to arrive tagged with the agent's internal staff ID. Put that ID in Custom User Field one for every agent, then include user_custom_one in the WEB FORM URL on the campaign. Now when any agent clicks through to the customer record, the Web form opens already stamped with that agent's ID, no per-agent URLs and no manual entry. Change roles? Edit one field on the user and the next login picks it up.

The same trick feeds scripts. If your Agent script needs to greet the customer with the rep's display name or route to a region-specific knowledge base, a custom field carries that value cleanly into the script text.

Keep them disciplined

Because the fields are unstructured, the only thing keeping them useful is your own convention. Decide what each of the five slots means across the whole account and write it down, otherwise field three holds an employee ID for one team and a phone extension for another, and nothing downstream can trust it. Treat the five slots as a tiny schema you have agreed on, not a junk drawer.

They also pair naturally with User group organisation. A consistent custom field across a group makes it easy to feed group-level context into every agent's CRM hand-off.

Where this fits

Custom User Fields are one of the quieter but more flexible parts of the user record. For the broader view of how agents, groups, and per-user settings fit together, read the VICIdial users and groups guide. If you are building out new agents, our walkthrough on how to add a VICIdial user shows where these fields sit on the form.

Want a dialer where wiring custom data into your forms is straightforward from day one? See our pricing plans for a managed VICIdial server that is live in under 40 seconds.