What Queue Groups do in reports

A reporting bucket, not a routing rule

A Queue Group is a reporting convenience. It bundles several campaigns and-or inbound groups under one ID so that certain reports can show their stats together as a single line. It does not route calls and it does not change how an Ingroup behaves at call time. Its only job is to let you ask one question across many queues: how is this whole team, product line, or business unit doing right now?

That distinction matters. If you have three sales Campaign definitions and two support inbound groups that all roll up to one department, a Queue Group lets a manager read the department's numbers without mentally adding five rows together.

Creating one

The ID must be 2 to 20 characters with no punctuation except an underscore, and the name must be 5 to 40 characters. The Active flag decides whether the group appears as a selectable option in reports, so you can stage one without exposing it. Then you simply pick the campaigns and inbound groups you want included. There is no limit on mixing inbound and outbound in the same group, which is exactly what makes it useful for blended teams.

flowchart LR
  C1["Sales campaign A"] --> QG["Queue Group"]
  C2["Sales campaign B"] --> QG
  I1["Support in group 1"] --> QG
  I2["Support in group 2"] --> QG
  QG --> R["Combined report line"]
  R --> M["Manager reads one number"]

When you actually reach for one

Queue Groups earn their keep on any Real-time report where you want a rolled-up view. A floor lead watching three campaigns at once can track a single combined queue instead of flipping between tabs. They are also handy for a Service level conversation: if your target is answered-within-X across an entire support department, a Queue Group gives you one number to defend rather than five. The same goes for any team KPI you report up the chain, where leadership wants the department total and does not care which queue did what.

A practical example: say you run a billing team that takes inbound support calls in two separate inbound groups and also makes outbound win-back calls from a third campaign. Each of those queues has its own ID, its own agents, and its own row in most reports. By dropping all three into one Queue Group, your billing manager opens a single report line and sees the team's total calls, total handle time, and overall answer behavior in one place. When a new campaign joins that team next quarter, you add it to the group once and every report that respects the group picks it up automatically. That is the real payoff: you describe the team's shape once instead of re-selecting the same five queues every time you build a report.

Warning: only some reports respect Queue Groups. They are not a universal filter, so if a particular report ignores the group you selected, that is expected behavior, not a misconfiguration. Build the group, then confirm it appears in the specific report you plan to live in before you rely on it for a daily stand-up or an executive summary.

Grouping queues for reporting is part of the same organizing instinct as grouping users for permissions. If you are setting up several teams from scratch, the VICIdial users and groups multi-team guide ties the two together.

Of course, a Queue Group is only useful if the right people can open the report in the first place. See how the view reports permission works before you hand a manager a dashboard they cannot reach.

Want a dialer where the reports are already wired and waiting? Start a VICIfast trial and your branded box is online in under 40 seconds.