Query Params

Query Params (short for query parameters) are optional key–value pairs appended to a URL that convey additional data or instructions to a connected system or endpoint. In the context of Connectors, query params help determine specific content, actions, or behavior based on the data being delivered as part of the connector request.

When a connector is triggered, such as opening an external application or sending data to a linked system, query params can be included at the end of the URL to pass extra information. These parameters follow a question mark (?) and are structured as key–value pairs connected with &.

For example:

?city=los angeles&state=california

In this example, the URL includes two query params:

  • city with the value “Los Angeles”
  • state with the value “California”

The receiving application can read these parameters and use them to filter content, prefill forms, trigger specific logic, or customize the experience based on the user’s context.

Query params are commonly used in web integrations to pass session data, identifiers, user preferences, or other contextual variables without needing backend changes.

Why It Matters

  • Provides flexibility when passing contextual data between systems
  • Allows connected applications to customize behavior dynamically
  • Supports integrations without requiring backend modifications
  • Improves workflow automation and system interoperability

Key Takeaways

  • Appended to URLs as key–value pairs
  • Guide specific content or behavior in connected systems
  • Used in connectors to pass data dynamically

Queue

Queue is an inbound call routing destination that organizes and distributes calls to a group of agents. It ensures that incoming calls are efficiently managed and sent to the right available agents based on predefined rules and logic.

When a call enters the system, whether through an incoming phone number (DID), an IVR menu selection, or an internal transfer, the call can be directed into a Queue. The queue holds the call until an agent becomes available to handle it. While in the queue, callers often hear hold music or announcements.

Queues support multiple configurations such as agent membership, routing strategies (e.g., longest idle, ring all, or prioritized agents), and fallback behavior. Depending on how it’s set up, a queue may:

  • Distribute calls to agents as they become available
  • Serve as a selectable option in an IVR menu
  • Act as a failover destination if another routing path isn’t available
  • Be assigned directly to a phone number (DID) for inbound handling

Agents assigned to a queue become eligible to receive calls from that queue based on availability and routing logic.

Why It Matters

  • Ensures structured and fair call distribution
  • Reduces caller wait times
  • Maximizes agent utilization
  • Supports efficient inbound call management

Key Takeaways

  • Organizes inbound call routing to agents
  • Works with IVR, transfers, and DID destinations
  • Supports multiple routing strategies
  • Helps manage call load and improve service levels

Queue Action

Queue Action is a column within the Agent Statuses table that reflects the specific action tied to an agent status when they are part of a queue. It identifies what the agent will do or how they will be treated in relation to queue-based call routing.

In the Agent Statuses settings, administrators can define various statuses for agents, such as Available, After Call Work, Paused, or Wrap-Up. Each status can be associated with a Queue Action that determines how the system should handle the agent with respect to queue operations.

For example:

  • Ready: The agent is eligible to receive calls from the queue.
  • Not Ready / Paused: The agent will not receive calls from the queue even if they are logged in.
  • After-Call or special states: The agent may temporarily be excluded from queue routing until the status changes.

By configuring Queue Actions, organizations control how agents interact with inbound queues throughout different parts of their workflow.

Key Takeaways

  • Found in the Agent Statuses table
  • Ties an agent status to queue behavior
  • Determines whether an agent accepts calls from a queue
  • Supports tailored queue routing and agent management

Queue Agents

Queue Agents refers to the interface within the CallTools platform that displays and manages the users currently joined to a queue. It provides real-time visibility into agent participation and key attributes that influence call routing and agent availability.

What You See on the Page

The Queue Agents page lists all agents who are members of a selected queue along with important status information, including:

  • Pause Status: Indicates whether an agent is currently paused and therefore not eligible to receive calls from the queue.
  • Static Member: Shows whether the agent is permanently assigned to the queue (as opposed to dynamically added via rules).
  • Follow Me Enabled: Shows if the agent has the Follow Me feature active, allowing calls to ring their alternate numbers before routing to voicemail or the next destination.
  • Penalty Score: Displays the agent’s penalty score, which influences how frequently they receive calls compared to other agents.

Actions You Can Take

  • Add Queue Agents: Clicking this button allows administrators to assign a user to the queue. The user must already exist and be eligible for membership.
  • Delete: Use the delete action to remove an agent from the queue, preventing them from receiving further calls from that queue until re-added.

Why It Matters

  • Centralizes management of queue membership
  • Provides visibility into agent availability and participation
  • Helps supervisors manage staffing and routing behavior
  • Supports optimized call distribution and team performance

Key Takeaways

  • Shows agents currently assigned to a queue
  • Displays pause status, static membership, follow-me status, and penalty score
  • Allows administrators to add or remove agents from the queue

Queue ID

Queue ID refers to the unique numeric identifier assigned to a specific queue within the CallTools platform. It distinguishes one queue from another and is used internally by the system to track, configure, and reference queues in URLs and API operations.

Every time a queue is created, the system generates a Queue ID that remains fixed for that queue’s lifetime. You can easily view a queue’s ID by navigating to its settings page in the dashboard.

Once you click Settings for a particular queue, the URL in your browser reveals the identifier. For example, in a URL such as:

calltools.io/manager/queues/edit/10

The final segment (10) represents the Queue ID for that queue. This numeric ID is essential when referencing the queue for configuration, scripting, integrations, or platform workflows that rely on unique identifiers.

Although the Queue ID appears in the interface URL, it is not typically edited directly by users. Instead, it functions behind the scenes as a stable reference point for system processes and integration mapping.

Why It Matters

  • Provides a consistent identifier for each queue
  • Supports integrations, scripting, and automation
  • Helps administrators verify and troubleshoot configurations
  • Ensures queues can be uniquely referenced across the platform

Key Takeaways

  • Unique numeric identifier for a queue
  • Found in the queue settings URL
  • Used for internal reference, scripting, and integrations
  • Helps uniquely identify queues across the system

Queue Priority

Queue Priority is a setting used when agents are members of more than one queue. It determines the order in which calls from different queues are delivered to the agent. Calls waiting in a higher-priority queue will be offered to the agent before calls from a lower-priority queue.

When an agent belongs to multiple queues, the system uses each queue’s Queue Priority value to decide which call should be delivered first. A queue with a higher priority value takes precedence, meaning the agent will receive calls from that queue before receiving calls from queues with lower priority values.

For example, if an agent is part of both a Sales queue and a Support queue, and Sales is assigned a higher priority, incoming calls from Sales will be handled first, even if the Support queue has been waiting longer.

Administrators can configure the Queue Priority field within the queue setup screens. Adjusting these values enables supervisors to align call delivery with business goals such as urgency, revenue impact, or service level agreements.

This setting only affects the order in which queued calls are offered to an agent—it doesn’t remove the agent from any queue or alter membership status.

Why It Matters

  • Ensures critical or time-sensitive calls are handled first
  • Helps align call handling with business priorities
  • Supports balanced workloads across multiple queues
  • Improves overall service quality and responsiveness

Key Takeaways

  • Used when agents belong to multiple queues
  • Higher values mean calls from that queue are delivered first
  • Helps prioritize important call types
  • Configurable by queue managers

Queue Timeout

Queue Timeout is a queue setting that defines how long incoming calls remain in a queue attempting to reach available agents before the system sends the call to a designated failover destination. This timeout value is expressed in seconds and ensures that calls don’t remain in a queue indefinitely when no agents answer.

When a call enters a queue, the system begins ringing the phones of all eligible queue members based on the selected routing strategy. If no agent answers within the Queue Timeout period, the system stops trying to distribute the call within that queue and forwards it to the configured failover destination.

The failover destination can be any defined endpoint, such as voicemail, another queue, an IVR menu, a different phone number, or a recorded message.

Why It Matters

  • Prevents callers from waiting indefinitely in a queue
  • Ensures calls are redirected if agents do not answer in time
  • Helps balance caller wait time with agent availability
  • Improves overall call routing and customer experience

Key Takeaways

  • Defines how long a call stays in a queue before failing over
  • Measured in seconds
  • Controls when the system redirects calls to a fallback destination
  • Helps maintain caller experience and queue efficiency

Quiet Mode

Quiet Mode is a conference setting that disables the standard audio notifications played when participants enter or leave a conference call. When enabled, the system suppresses the default join and exit prompts, allowing participants to enter or exit the conference silently.

This feature is commonly used in conference environments where frequent participant movement could disrupt the conversation. Normally, conference systems play an audible tone or announcement whenever someone joins or leaves the call. Quiet Mode removes these notifications so the conversation can continue without interruption.

By eliminating entry and exit tones, Quiet Mode helps maintain a smoother and more professional conference environment, especially when many participants are involved.

Why It Matters

  • Helps maintain focus during conference calls
  • Removes distracting join and leave notifications
  • Supports smoother conversations in active meetings
  • Improves the overall participant experience

Key Takeaways

  • Silences default audio prompts when participants join or leave a conference
  • Applied within conference call settings
  • Reduces interruptions during meetings
  • Improves clarity and professionalism in large or active conferences