The control plane from
audience to outcome.
One platform owns the whole arc: who to reach, what should happen, making it happen safely at volume, and what it achieved. Deepest today in outbound voice.
Platform
Not a dialer. A control plane.
Throughline CX is the control plane between your contact data and your business outcomes: design the logic, govern the run, and measure what it achieved, in one console.
See everything
The live state of every program, interaction, and guardrail is current and unambiguous. Nothing happens silently.
Prove everything
Compliance runs in the execution path, before the action, and leaves an auditable trail. Confidence, not hope.
Measure outcomes
Business results (booked, promised, completed), not just dial counts. So you tune what works instead of guessing.
Lean on it
Durable execution and reliable eventing keep your programs and downstream systems correct, even through failures.
How it works
Four objects, one throughline.
The same four primitives power every program, and they are channel-agnostic by design. Voice is the first surface on them, not the foundation.
01 · Flow
The logic
A visual graph: speak, ask, branch, transfer, call an API, record a result. Versioned and published.
02 · Audience
Who to reach
Imported, segmentable contacts with the data you bring, fed into the logic as live variables.
03 · Automation
The governed run
One flow against one audience: paced, scheduled, pausable, and durable. A restart never loses its place.
04 · Outcomes
What it achieved
Declarative business results, measured and surfaced in analytics. Achievement, not throughput.
The engine
Compliance is the first thing that happens.
For each due contact, the rules run before the action. Anything that fails is skipped or rescheduled. It is never reached.
Check the rules
DNC / suppression, the contact's local-time window, frequency caps, and a live concurrency ceiling.
Act
Place the call over your own telephony. The platform orchestrates; it doesn't resell a carrier.
Run the flow
Speak, ask, branch, transfer, call an API, with live {{ expressions }}.
Record
Disposition and outcome signals, written as immutable records for analytics and audit.
Use cases
Declare the outcome. We reach it, safely.
Say what you want to achieve. The platform reaches the audience, stays inside the rules, and measures what it actually did.
Examples: you define the outcomes that matter to your program.
Reminders & confirmations
Reach the right contact at the right local time, and capture whether they confirmed.
Collections & promises
Run sensitive outreach inside strict limits, with every decision on the record.
Surveys & feedback
Ask, capture keypad or spoken input, and turn answers into structured outcomes.
Renewals & win-back
Branch on the contact's data and route to a person when the moment calls for it.
& more
Custom programs, at any scale
These are starting points. The same four objects build whatever you run, at the volume you run it.
Trust
Compliance in the path, not in a report.
This is the part a compliance officer reads line by line. So here are the real controls, and the honest limits, stated plainly.
- In the path, not a report
- A pre-dial gate enforces DNC / suppression, local-time windows, per-contact frequency caps, and a live concurrency ceiling, before each contact is reached.
- Isolation you can show
- Database-enforced row-level isolation on a non-privileged role; per-tenant encrypted credentials; scoped API keys. Demonstrable, not asserted.
- Auditable by construction
- Immutable activity and outcome records; login and session auditing; live, unambiguous state. What happened is reconstructable after the fact.
- Your rules, our controls
- The platform gives you the tools to operate within your own rules. It does not make you legally compliant, and it claims no certification on your behalf.
No fabricated proof: no invented customers, logos, ratings, or metrics. No unearned certifications. No compliance guarantees. We describe the real controls, and we label trajectory as trajectory.
FAQ
Straight answers, including what isn't built yet.
What's available today?
Outbound voice, end to end: the visual flow builder, audience import, governed automations with the gate in the path, durable execution, reliable eventing, and outcome analytics. Available today
Can we sign up online?
Not yet. Onboarding is sales-assisted today: a guided pilot, operator-provisioned, bring-your-own-provider. Public signup, billing, and plans are direction. On the path
Does it make us compliant?
No. You operate within your own rules; the platform enforces the controls you configure and leaves an audit trail. It holds no certification on your behalf. It gives you the tools to prove control.
Which channels are supported?
Outbound voice today, over a supported PBX, 3CX only, for now. A true multi-channel platform is on the path. On the path
Do you provide telephony or AI?
No. You bring your own providers (telephony, voice, email, CRM, APIs). Credentials are encrypted and test-connected. The platform orchestrates; it doesn't resell a carrier.
Is there real-time conversational AI?
Not today, and we don't pretend otherwise. AI shows up now as natural, multi-language AI-generated speech and a live expression engine. A real-time conversational AI voice loop is deliberately deferred. On the path
Is there anything for developers?
Yes, today: scoped API keys, request logs, webhooks, and reliable eventing with signed, idempotent deliveries. See the developer reference.
How do we start?
Start with a demo against what you actually run, then a governed pilot with your own providers. Watch a demo.
Turn outreach into a governed, measurable operation you can stand behind.
Bring your own providers. Start with a demo against what you actually run, then a governed pilot.