Default Transfer Group: pre-selecting an in-group in the transfer frame

If your agents transfer to the same closer queue almost every time, making them pick it from a dropdown on every call is wasted motion. Default Transfer Group fixes that by pre-selecting an in-group the moment the transfer frame opens.

What the setting does

Default Transfer Group is the in-group that gets automatically selected when an Agent goes to the transfer-conference frame in their interface. An Ingroup is the inbound queue a transferred call lands in, where a closer or specialist picks it up. Instead of opening to a blank or arbitrary selection, the frame opens with your chosen queue already highlighted and ready.

The agent can still change it. This is a default, not a lock. If a particular call needs a different destination, the agent opens the pull-down and picks another in-group as usual. The setting just removes a step from the common case.

How the pre-selection happens

flowchart TD
  A[Agent clicks transfer button] --> B[Transfer-conference frame opens]
  B --> C{Default Transfer Group set}
  C -->|Yes| D[Pre-select that in-group]
  C -->|No| E[Open with no preset queue]
  D --> F{Agent keeps default}
  F -->|Yes| G[Transfer to default in-group]
  F -->|No| H[Agent picks another in-group]
  H --> I[Transfer to chosen queue]

The frame checks the Default Transfer Group value as it loads. If one is set, that in-group is highlighted right away. From there the agent either accepts it and completes the Warm transfer, or overrides it for that one call. Either path is fast.

Choosing the right default

Pick the in-group your agents send calls to most often. A few sensible choices:

• The primary closer queue for a single-product sales campaign.
• A verification queue that every qualified lead has to pass through.
• The busiest Closer team, so the default matches the path most calls take anyway.

Make sure the in-group you choose as the default is one the campaign is actually allowed to transfer to. The pool of valid destinations comes from Allowed Transfer Groups, so set that list first, then pick your default from inside it. A default that points at an in-group the campaign cannot reach only causes confusion.

Small setting, real time saved

On a floor doing hundreds of transfers a day, one fewer click per handoff adds up. It also cuts mistakes: when the right queue is already selected, an agent is far less likely to fire a transfer into the wrong place during a busy stretch. Pair it with a sensible sort order so the rest of the dropdown is easy to scan when an override is needed.

Default versus forcing a choice

It is worth being clear about what a default is not. It does not stop an agent from sending a call somewhere else, and it does not narrow the list of available in-groups. That narrowing is a separate job handled by the allowed-groups list. The default only changes what is highlighted first. So if you have a campaign where every call truly must go to one queue, the default alone will not enforce that; you also restrict the allowed groups so no other destination is even on the menu.

Used the other way, a default is a gentle nudge rather than a hard rule. It steers the common case while leaving agents free to handle the odd call that needs a different Ingroup. For most teams that balance is exactly right: fast on the routine handoff, flexible on the exceptions.

Reviewing it over time

Traffic patterns shift. The queue that took most of your transfers six months ago might not be the busiest one now. Make the Default Transfer Group part of a periodic campaign review: glance at where transfers actually go, and if the bulk of them no longer match the default, update it. It is a thirty-second change that keeps the most common path the fastest one.

For how the default, the allowed list, and the sort order combine into one transfer experience, see the VICIdial transfers and closers guide. If you want these campaign defaults configured to match how your team really transfers, our pricing page covers managed setup.