What Admin Hide Lead Data and Hide Phone Data do

Not every manager needs to see a customer's name, address, or phone number to do their job. A QC lead or a floor supervisor often only needs to see call outcomes, timing, and agent activity. VICIdial gives you two user settings to support that separation of duties: Admin Hide Lead Data and Admin Hide Phone Data. Both live on the user modification screen, and both replace sensitive values with rows of X characters so the underlying record is invisible.

Who these settings affect

The most important thing to understand is that these two settings only apply to level 7, 8 and 9 users. Lower-level accounts are governed by other restrictions, so toggling these on a level 6 user does nothing visible. If you are unsure where your accounts sit, the User group and per-account level fields decide everything else about what a person can reach, and the level number itself controls whether these masks even take effect.

For a refresher on how the numbering maps to capability, see VICIdial user levels explained.

Admin Hide Lead Data

When Admin Hide Lead Data is enabled, the customer's Lead details are replaced with Xs across the many reports and screens in the system. Names, addresses, and the other personal fields tied to a record stop rendering for that manager. The call itself, the Disposition, and the agent who handled it are still visible, so a supervisor can review performance without ever reading the contact's identity. The default is 0, which means disabled and full visibility.

Admin Hide Phone Data

Admin Hide Phone Data works the same way but targets the Phone Number Prefix and the full dialed numbers. With it on, customer phone numbers show as Xs throughout reports and screens. There is a companion DIGITS setting: instead of masking the entire number, you can choose to reveal only the last few digits, so a record reads as a string of Xs followed by something like 4821. That is enough for a manager to match a callback or confirm a record without exposing a number an agent could dial off the clock. The default here is also 0, disabled.

How the masking decision flows

flowchart TD
  A[Manager opens a report] --> B{User level 7 8 or 9}
  B -->|no| C[Settings ignored full data shown]
  B -->|yes| D{Hide Lead Data on}
  D -->|yes| E[Lead fields show as Xs]
  D -->|no| F[Lead fields visible]
  E --> G{Hide Phone Data on}
  F --> G
  G -->|yes| H{DIGITS set}
  G -->|no| I[Phone number visible]
  H -->|yes| J[Last few digits shown]
  H -->|no| K[Full number as Xs]

What stays visible

It is worth being clear about what these settings do not hide, because that is what makes them useful rather than crippling. The operational layer of each call remains fully readable: the Status (lead status) of the record, the timing, the agent who handled it, the Talk time, and the campaign it belonged to. A supervisor can still measure productivity, audit a Disposition pattern, or spot an agent who is mishandling calls. What disappears is only the identity of the person on the other end of the line. That is exactly the split you want for a team whose job is performance review rather than customer contact.

There is one more practical detail with the phone mask. Because the DIGITS option reveals only a trailing slice of the number, you can tune how much exposure to allow. Showing the last four digits is usually enough to let a manager confirm they are looking at the right callback record, while still keeping the full number out of reach. Setting DIGITS lower, or leaving it off entirely so the whole number renders as Xs, is the stricter choice for the most sensitive campaigns.

When to reach for these

These masks are practical for shared QC teams, outsourced supervision, and any setup where GDPR or other data-handling rules push you to limit who sees customer identity. Remember the scope: they take effect only on level 7, 8 and 9 accounts, so they are aimed squarely at the manager and admin tier rather than at agents, who are governed separately. They are a display-layer control, not encryption, so treat them as one layer alongside recording access rules and login auditing. Pair them with tight account scoping; the broader picture of who can touch what is covered in our VICIdial users and groups multi-team guide.

Standing up a clean dialer where these controls are wired in from day one beats retrofitting them. A managed VICIdial box gives you a private subdomain over HTTPS in under 40 seconds. See the plans and pricing to get started.