Platform

Everything a contact center needs,
on every plan.

Plans differ by how many people you have and how much usage is included. They never differ by which features you are allowed to touch — feature gating exists to create upgrade pressure, not because a feature costs anything to switch on.

Routing & queues

The part that decides who gets which conversation. Everything else on this page depends on it being right.

Skills-based routing

Tag agents with skills and proficiency levels, and require a skill on a queue. A caller only reaches someone who can actually help them.

Seven distribution strategies

Longest idle, round robin, fewest calls, random, skill-first, and more — chosen per queue rather than imposed platform-wide.

Priority & VIP

Boost a queue or a specific caller so they move ahead of the line without needing a separate queue to manage.

Overflow

After a wait you set, a caller moves to a second queue instead of holding indefinitely for a team that is clearly busy.

Service-level targets

Set the target per queue; every call is marked met or missed, and the figure surfaces on the wallboard and in reports.

Callbacks

Offer to ring back rather than hold. The caller keeps their place, and the system dials them when an agent is genuinely free — including at a time they choose.

Wait experience

Position announcements, estimated wait, music or a message on hold, all per queue.

Transfers

Blind and attended transfers, transfer to a queue or a named person, and multi-party conference — from the softphone or the browser.

Wrap-up

A configurable window after each call for notes and a disposition code, after which the agent returns to available automatically.

The flow builder

What happens on a call, built by dragging pieces together rather than by writing dial plans or filing a ticket with us.

The flow builder: a widget palette on the left, and a flow on the canvas running from an AI agent to an IVR menu and on to Sales, Billing, Customer Support and voicemail queues.
This flow starts on an AI agent, falls through to a menu, and lands in a queue. A widget visited more than ten times ends the call — a loop guard, so a misconfigured flow cannot trap a caller.

Fourteen widgets, one canvas

Play a greeting or a prompt. Collect a keypress and branch on it. Branch on business hours against a schedule you keep in one place, or on conditions — where the call came from, what the caller entered, what time it is. Look a value up in your own systems and branch on the answer. Set a variable and carry it through the call. Put the caller in a queue, take a voicemail, take a callback request, ask for a satisfaction rating, or hand the conversation to an AI agent — with a dedicated widget for choosing between AI and a person.

One flow, every channel

The same flow serves voice and digital, so a web chat and a phone call enter identical logic and land in the identical queue — you maintain one thing, not one per channel.

Flows are versioned with a note on each save and a history you can read, and there is a Test button — so changing what happens on your main line is not an act of faith.

Channels

Six of them, sharing one routing engine, one set of queues and one team.

Voice

Real SIP telephony with your own carrier or ours. Desktop softphones for macOS and Windows, and a browser workspace that needs no install.

Web chat

An embeddable widget with typing indicators, a pre-chat form, file attachments and an end-of-chat rating that feeds your CSAT reporting.

SMS

Two-way messaging on your numbers, routed through the same queues as everything else.

Email

Handled as tickets with a sticky owner, so a reply comes back to the person who answered it, with signatures, attachments and CC.

WhatsApp

Business messaging as a first-class channel rather than a forwarded inbox.

Social

Messenger and Instagram conversations land in the same queue as everything else.

Agents have separate capacity per channel — typically one voice call and several chats at once — so a phone conversation is never interrupted by a message. How omnichannel works

Supervision & quality

Watching what is happening now, and grading what already happened.

Live wallboard

Queues, waiting counts, longest wait, agent states and service level, updating as it happens.

Listen, whisper, barge

Join a live call silently, coach the agent without the customer hearing, or join the conversation outright. The same three modes work on text: read a live chat, send the agent a private note, or post as yourself.

Recording

Configured per flow, with a spoken disclosure for two-party-consent jurisdictions and a pause control so card numbers are never captured.

Quality management

Build QA forms and score against them, with review sampling that automatically assigns a share of completed interactions to evaluators round-robin under a monthly quota — so reviewing is a worklist, not a good intention.

Calibration

Have two or more evaluators score the same conversation and watch the spread. A low spread means your reviewers agree on what "good" means; a high one means they are scoring inconsistently and should recalibrate against the form. Machine scores are excluded so they cannot flatter the number.

Automatic scoring

An LLM grades every transcribed call and every ended chat against your own form — with a per-question score and its reasoning — instead of the 2% sample a human team can manage.

Agent assist

A suggested reply grounded in your knowledge base, next-best actions, and live sentiment that can alert a supervisor.

Workforce management

How many people you need, when — and whether the people you scheduled actually cover it.

Staffing forecast

Erlang-C over your own history, at 15, 30 or 60-minute intervals, against the service level you are targeting.

Shift scheduling

Build shifts per weekday and assign them, in the same place as everything else.

Coverage gaps

Scheduled headcount against forecast requirement, per interval, so an understaffed Monday morning is visible before it happens.

Reporting

Both kinds: the standard set every contact center needs, and the question you did not anticipate.

The standard set

Grouped by queue, agent or number, over any date range: total handled, answered, abandoned and abandon rate, average speed of answer, average handle time and service level. Exportable as CSV, and schedulable so it arrives by email without anyone remembering to run it.

Asked in plain English

Ask a question the report builder cannot express — a pivot, a top-N, a time-of-day window — and keep the answer as a saved report. It re-runs through the same engine that produced it, so the numbers match by construction rather than because a second implementation agrees.

The analytics page: per-queue statistics, a custom report builder with group-by, direction and channel selectors and fifteen selectable columns, and an agent leaderboard ranked by calls handled.
Group by any dimension, choose the columns, run it, export CSV, or save it to re-run on a schedule. Figures are from a demonstration account.

Administration & platform

The parts a buyer asks about once the product itself has been agreed.

Roles & permissions

Sixteen granular permissions, custom roles, and supervisors scoped to specific queues or a branch of the team.

Single sign-on

Google, Microsoft, generic OIDC and SAML 2.0, with SCIM provisioning and an account policy that can require SSO outright.

Audit trail

Every configuration change recorded with who made it, from where, and when — readable in the console and exportable.

API & webhooks

Scoped API keys and event webhooks, so the platform can drive the systems you already run.

Carrier connections

Bring your own SIP trunks, or use numbers from us. Trunk credentials are encrypted at rest and never returned by the API.

Privacy tooling

Export or erase everything held against a phone number, and automatic redaction of card numbers and SSNs from transcripts.

Start free with Google

Google or Microsoft · 30-day free trial · $15 credit · no card required