AI-generated summary
where external SIP trunk calling names override queue-level settings, E.164 number format validation based on organization language defaults, and alerting timeout ranges between 7-59 seconds that trigger "Not Responding" agent status when exceeded. Voice channel features include service level targets, caller ID customization, auto-answer functionality that bypasses alerting timeouts while providing audio alerts, optional whisper audio prompts before agent-caller connection, and Architect in-queue flows. Voice transcription and audio monitoring require administrator-level enablement and AudioHook integration. Whisper prompts can be applied to all agents or specific Architect user prompts, with customizable audio files and duration display for each language or text-to-speech option. Voice recording during queue wait can be independently enabled or disabled, with recording suppression resumable upon agent interaction. Custom hold music can be configured at the queue level to override organization-level settings.
For digital channels including chat and messaging, service level percentages and targets are configurable using sliders and input fields. Auto-answer functionality automatically connects interactions to agents without alerting timeouts, though agents receive audio alerts upon connection. Audio duration alerts can be enabled for auto-answered, unparked, or manually-answered interactions. Outbound SMS channels require association with Message Routing flows for inbound response routing. Dynamic utilization supports weight reduction rules with configurable inactivity intervals and percentage-based reductions. For message channels, in-queue flows can be defined using Architect, and outbound messaging requires channel-specific configurations: SMS channels need assigned outbound SMS numbers, WhatsApp channels require WhatsApp integration selection, and Open Messaging channels need Open Messaging integration assignment. Inactivity handling for messaging conversations supports timeouts between one and 30 minutes with options to disconnect with sign-off messages or route to alternative Architect flows.
Email channel configuration allows administrators to specify outbound email addresses and domains, assign multiple addresses to queues, and designate default email addresses for agent use. Optional features include in-queue email flows via Architect and published scripts for email interactions. The system routes replies through the original incoming email route by default, with interaction transcripts providing visibility into which email address agents used.
Callback configuration supports two types: Agent First (default), where the system connects the agent before dialing the customer, and Customer First, where the system places the callback to the customer first and routes to an agent only after customer answer, improving agent utilization. Configurable service level percentages and targets apply to callbacks, with agent ownership limited to Agent First scenarios and requiring at least one Preferred Agent Routing rule. Agents can schedule callbacks up to 30 days in advance for non-owned callbacks, with customizable advance scheduling windows for owned callbacks. Ownership periods range from one hour to 30 days, after which unclaimed callbacks are removed from the queue. For Agent First callbacks, administrators can enable auto-answer and automatic callback initiation/termination, configure alerting timeout durations and audio settings, and allow agents to take ownership with automatic reassignment upon expiration. Communication Level After Call Work enforcement is required for automatic callback start and end functionality. For Customer First callbacks, agent reservation before dialing ensures optimal availability, with routing options including transfer to queue using existing Architect in-queue flows or transfer to custom Architect inbound flows. Answering machine handling supports prerecorded message delivery and retry functionality through designated Architect flows. Callback configuration also involves managing pacing modifiers that determine callback volume by calculating ratios with online agents (ranging from 1 callback per 50 agents at value 1 to 1 callback per agent at value 10), setting maximum retry attempts (0-20) with configurable time intervals between retries (up to 24 hours), and directing routing to specific telephony sites based on customer callback origin. All configurations require explicit saving to take effect.