Skip to main content

Agent Settings

Agent Settings controls how much live work each agent can hold and what happens to agents and tickets that go idle. Use it to stop any one agent from being flooded, to give busier teams or channels more headroom, and to mark disconnected agents offline.

All sections appear in one continuous page with clear headings. Use the sticky On this page links to jump to a section. Each link adds a section fragment to the URL, so you can copy or bookmark the link and open that section directly. Save changes applies edits across the whole page; Discard restores the saved values. Changes are not saved automatically.

Open Settings → Agent Settings to find Ticket capacity, Assignment rules, and Availability & actions. The page heading is Agent Capacity & Availability.

Use the link icon beside a setting name to share that specific setting: click it and copy the browser address, or right-click and choose Copy link address. See sharing settings links for details.

Ticket capacity​

Agent ticket limits​

Set the base ticket limit for each channel. Every value must be at least 1. Apply edits with Save changes at the bottom of the page.

For details about which tickets count toward a limit, how Flowcall selects an override, and what happens when an agent reaches capacity, see Maximum ticket assignment logic.

Unlimited backend agent tickets​

Turn on Unlimited Backend Agent Tickets to remove channel limits, team overrides, and combined channel capacity limits for agents who belong only to backend teams. This includes manual tickets. The setting is off by default; use Save changes to apply it.

Tickets go to the eligible backend agent with the fewest total Assigned tickets across all channels. Ties rotate by last assignment time. Availability, team matching, and preferred-agent routing still apply. Agents with a front-line team continue to use the configured limits. Organization agents use their home account's setting; when one person has multiple enabled account records, all must enable it.

Channel capacity borrowing​

  • Channel capacity borrowing — when on, an agent may exceed a single channel's limit by using unused capacity from the other channels they handle. The agent's total assigned tickets are capped by the combined sum of their channel limits instead of each channel's own limit.

For example, with a WhatsApp limit of 3 and an Email limit of 5, an agent who handles both channels has a pooled capacity of 8. If no email tickets are waiting, that agent can hold up to 8 WhatsApp tickets; as email tickets arrive, they draw from the same pool.

Notes:

  • The toggle is off by default and applies account-wide. Save the page to apply a change.
  • Ticket limit overrides scoped to specific teams still cap their own tickets — borrowing never pushes a team bucket past its override. Channel-wide overrides contribute their overridden value to the pooled sum.
  • Manual tickets do not participate in borrowing; they keep their own separate cap.
  • Backend agents are channel-agnostic, so their pool spans all five channels.
  • Borrowed capacity is first-come-first-served: if one channel fills the pool, tickets on the agent's other channels wait until assigned tickets resolve and free slots.

See Channel capacity borrowing under the assignment logic for how the pooled limit is evaluated.

Configure ticket limit overrides​

Each override row has:

  • Teams — one or more teams the override applies to. Leave empty to apply to all teams.
  • Channel — the channel the override applies to. Leave empty (All channels) to apply across every channel.
  • Tickets — the ticket limit for this scope (minimum 1).
  • Order — use the up/down arrows to reorder the rows.
  • Delete — remove the override (with a confirm prompt).

Flowcall does not allow duplicate team-and-channel scopes. An empty Teams field counts as all teams, and an empty Channel field counts as all channels when checking for a duplicate.

Use Add override to create a row. Override changes remain local until you press Save changes in the page-wide bar, so you can add, reorder, and delete several rows together.

Assignment rules​

Assign reopened tickets to the previous agent​

When a ticket reopens automatically, return it to its previous agent if they are available and eligible for its team and channel. This covers:

  • A customer reply to a ticket awaiting response, whether an agent, the system, or an automatic resolution put it there. Child tickets that went awaiting with their parent return to their own previous agent.
  • A customer saying the issue is not resolved after a resolution confirmation.
  • A snoozed ticket waking up.

An agent manually moving a ticket out of awaiting response uses ordinary capacity rules. These assignments can exceed configured ticket limits, including team overrides and combined channel capacity.

Keep a ticket family with the same agent per team​

When a child ticket is queued, give it to the agent from its team who most recently worked the parent ticket or another ticket in the same family (another child or an interaction ticket). The agent must currently belong to the child ticket's team, be available, and handle its channel. If not, the ticket is assigned as usual. Like reopened tickets, these assignments can exceed configured ticket limits, including team overrides and combined channel capacity. A preferred agent the ticket already has, such as its previous assignee, is tried first. Off by default.

Once the setting is on, use Teams to choose where it applies. Only child tickets in the selected teams stay with the same agent; child tickets in other teams are assigned as usual. Leave Teams empty to apply it to every team. A deleted team drops out of the list; if every selected team is deleted, the field shows All teams and the setting applies to every team.

Turn on Keep the family agent even when they are unavailable to let a child ticket wait with its family agent while they are offline, busy, or on a break. An available family agent from the team still comes first. The ticket goes to an unavailable one only when no available family agent can take it, and it never goes to a disabled agent. Use Statuses to choose which unavailable statuses count; all three are selected by default, and leaving it empty also counts all three. Agents who are not available only receive tickets from families they already worked, never other queued tickets.

The ticket stays assigned until the agent is back or someone reassigns it, and its SLA keeps running in the meantime. Automatic assignment also pauses when no agent in the account has been online for 30 minutes, so a child ticket created then stays in the queue until someone comes online.

Agent reassignment​

Configure manual assignment, reassignment, unassignment, and team changes under Teams → Roles → Action access. These are separate permissions for each role and account. Taking an unassigned ticket yourself is also separate from taking over another agent's assigned ticket.

See Roles & Action Access for the full permission list and how existing account settings contribute to initial defaults. Agent Settings continues to control limits and availability, rather than who may perform these actions.

Unavailable agent assignment​

  • Unavailable agent assignment — when on, tickets can be assigned to agents who are currently marked unavailable (for example, away or on a break). Leave it off to route work only to available agents; turn it on for small teams where coverage matters more than respecting availability status.

Disposition before ticket assignment​

Require agents to save disposition before assigning or reassigning an individual parent or child ticket to an agent or team.

Availability & actions​

Busy types​

Add labels such as Lunch, Short Break, or Meeting to replace the generic Busy choice in the agent status menu. A selected label still behaves as Busy for ticket routing, but Flowcall records the label and shows it in agent status views, activity logs, and CSV exports.

Removing a label stops agents from selecting it again. Existing agent logs keep the label that was captured at the time.

Auto-actions​

  • Auto Mark Offline After — mark an agent offline when all their dashboard tabs are in the background or disconnected for this many minutes. Any visible dashboard tab keeps the agent active. Leave blank or set 0 to disable. Checks run every five minutes, so the status change may be delayed. Agents must select Available when they return. Organization agents use their home account's setting.
  • Auto Unassign Ticket After — currently disabled and not active. Existing tickets stay assigned when an agent is marked offline.

Add an agent​

Agents themselves are created on the Team Management page, not on this one. The limits below only take effect once an agent exists and has channels and teams assigned.

Invite a new person​

  1. Open Team Management and use Add Member.
  2. Enter the person's Email Address and pick a Role.
  3. Press Send Invitation.

Flowcall emails the invitation and also shows the invitation link in the drawer, so you can share it directly — useful when the email doesn't reach them.

Promote an existing member to agent​

Someone who has already joined your account is a member, which is not the same as an agent: only agents receive ticket assignments. On the Members tab, open the row menu for that person and choose Add as Agent.

Configure the agent​

Open the agent from the Agents tab to reach Agent Settings. Every field saves as you change it:

  • Status — Active, Busy, On Break, or Offline. When custom busy types are configured, choosing Busy also lets you select the reason. The agent must be enabled before status can be changed.
  • Role — the permission role applied to their account.
  • Channels — WhatsApp, Live Chat, Email, Instagram, and Incoming Call. A front-line agent is only eligible for tickets on the channels selected here.
  • Assignment Order — Old First or New First, controlling which queued ticket reaches them first.
  • Teams — the teams the agent works in. Type a name to create a new team, or pick GLOBAL (All Tasks) to make the agent eligible regardless of a ticket's tags.
  • Assign tickets from the same team tags only — on by default. The agent gets only tickets of their own teams; an agent with no team gets only tickets without a team. Turn it off to let the agent get any team's tickets.

Channels and teams are what tie an agent to the settings on this page: the Channels you pick decide which per-channel base limit applies, and the Teams decide which ticket limit override applies. For how teams and eligibility work in full, see Agent Assignement & Team.

Manage teams and agents with Copilot​

Open Ask Copilot on the Agent Settings page to look up or change teams and agents in plain words. Copilot reads your live teams and agents, so you can ask "Who is in the Billing team?", "Which agents take email?", or "Which tasks route to Returns?".

Copilot can draft these changes for you to review:

  • Create a team, with its description, backend flag, default manual source, and members. For example: "Create a Returns team with Priya and Ankit".
  • Change a team — rename it, edit its description, mark it as a backend team, keep parent tickets open while it works, set its default manual ticket source, make it the default team, or add and remove members. Making a team the default takes the default away from the current one, and the card shows both changes.
  • Change an agent — enable or disable them, set their channels, assignment order, whether they only get their own teams' tickets, and which teams they belong to.

Every change appears on a review card with the current and new values, and nothing is saved until you click Apply. The card warns you about side effects first: disabling an agent sets them offline and returns their assigned tickets to the queue, and changing backend team membership can switch an agent between the agent and backend agent roles. Undo puts the previous values back; undoing a disable enables the agent again but does not give the tickets back, and undoing a new team removes it as long as no task, SLA rule, or open ticket uses it yet.

Copilot does not delete teams, invite people, remove agents, or change an agent's role, features, name, or phone; it links you to this page for those. You cannot disable your own agent from Copilot. Team ticket limits are set with ticket limit overrides, which apply per team and channel, not per agent.