How to scope which campaigns a group can QC

Quality control in VICIdial means listening back to recorded calls and re-scoring how each one was handled — did the agent follow the script, take the right Disposition, stay compliant. If you run more than one program on the same dialer, you rarely want every QC reviewer to see every program's calls. The two settings that draw that boundary live on the User group modify screen: QC Allowed Campaigns and QC Allowed Inbound Groups.

Both settings sit alongside the other QC controls on the group, and they behave like every other scoping list in VICIdial: an empty selection means the group sees nothing, a specific selection means the group sees only what you picked, and an ALL option opens the whole system. That consistency is worth internalizing, because the same mental model applies to allowed campaigns, allowed call times, and the report scoping settings on the same screen.

What each setting scopes

QC Allowed Campaigns is a selectable list of outbound Campaign records that members of the group are allowed to QC. QC Allowed Inbound Groups does the same for each inbound Ingroup — the queue that routes received calls to agents. Each list has an ALL option: ALL-CAMPAIGNS lets the group QC any campaign on the system, and ALL-GROUPS lets them QC any inbound group. Anything you do not select stays invisible to that group's reviewers.

These settings only govern what a reviewer can pull up for QC. They do not change which agents run a campaign, and they do not change which Disposition codes an agent can pick at the end of a call. Think of them purely as the lens a QC team looks through.

How a QC reviewer's access is decided

flowchart TD
  A[QC reviewer opens a call] --> B[Read reviewer user group]
  B --> C{Call is outbound or inbound}
  C -->|Outbound| D{Campaign in QC Allowed Campaigns}
  C -->|Inbound| E{Group in QC Allowed Inbound Groups}
  D -->|Yes| F[Reviewer can QC the call]
  D -->|No| G[Call is hidden from reviewer]
  E -->|Yes| F
  E -->|No| G

A practical setup

Say you host two clients on one box. Create a QC group for each client and set QC Allowed Campaigns to only that client's outbound campaigns, plus QC Allowed Inbound Groups to only that client's inbound queues. A reviewer in Client A's group now cannot open a single Client B recording, even though both run side by side. Reserve the ALL options for an internal team that genuinely needs to audit the whole system.

There is a second, quieter benefit to scoping QC tightly: it speeds reviewers up. A QC team that only ever sees its own client's calls is not wading through a list cluttered with other programs' recordings, so they spend their time scoring rather than filtering. On a busy box where a Closer desk and several outbound campaigns all record into the same store, that filtering cost adds up fast. Set the lists once when you stand up the group and the reviewers never have to think about it again.

Warning: these settings only gate the QC review screen. They do not stop a manager with broad permissions from finding recordings through other admin tools, and they do not encrypt or remove anything. Treat QC scoping as a workflow boundary that keeps teams in their own lane, not as a security wall around the recordings themselves.

Note: QC scoping is separate from the campaign-allow list that controls which campaigns a group can log into. Restricting QC does not restrict login, and vice versa. If you also need to fence off which campaigns agents can join, see the user-group allowed campaigns setting. The bigger picture of grouping agents and reviewers lives in our users and groups guide.

Multi-client QC is far simpler when the dialer comes pre-secured and single-tenant. See VICIfast plans to spin up a dedicated, branded VICIdial server in under 40 seconds.