Cllr connects to the systems you already run, decides when a workflow should start, carries out the work across channels and writes the outcome back.
- workflow actions every month
1.5M+
Running for teams at
Voice · WhatsApp · SMS · Email
- languages supported
60+
Every customer, in their own language.
- from a new event to the first action
<1s
New event
1s
How a workflow runs
Four parts, the same for every workflow you add.
Start from events your systems already record
Cllr reads your billing, CRM, support desk, product usage and operations data. A failed payment, a new lead, a stalled ticket or a missing document becomes a trigger. Each one is deduplicated and routed to the workflow that owns it, so it never waits in a dashboard.
Failed · $499
Down 62%
Due in 7 days
Written to your CRM
Payment recovered
0.84s
signal to CRM
One workflow, start to finish
A failed payment, worked from day 0 to day 7. Each step is chosen from what the customer did on the one before.
Day 0 · 9:04
Payment failed · $499
From StripeDay 0 · 9:04
Recovery workflow started
0.84s after the eventDay 0
Personalised voice call
No answerDay 2
WhatsApp follow-up
Read · a soft yesDay 3
Payment link sent
OpenedDay 5
SMS reminder
DeliveredDay 7
Payment recovered
$499 · written to your CRMPayment failed · $499
From StripeDay 0 · 9:04
Recovery workflow started
0.84s after the eventDay 0 · 9:04
Personalised voice call
No answerDay 0
WhatsApp follow-up
Read · a soft yesDay 2
Payment link sent
OpenedDay 3
SMS reminder
DeliveredDay 5
Payment recovered
$499 · written to your CRMDay 7
Day 0 - the event fires, the workflow starts
A payment fails at 9:04am. In under 1 second, Cllr starts the recovery workflow and reaches the customer with a personalised offer while the purchase is still fresh.
The work your teams repeat, run on one platform
Each workflow shares the same connections, rules and audit trail.
Tickets, calls and chats are answered with the customer's full history. When a rule says a person should take over, the case moves to your team with its context attached.
Where is my refund?
Customer · WhatsAppOne platform instead of a stack of point tools
Single-purpose AI agents handle one kind of conversation well. Cllr runs the workflows around them, on your data and your rules.
Single-purpose AI agents
- Handles one kind of conversation on one channel
- Waits for the customer to make contact
- Reads your help centre and knowledge base
- One session, then the thread ends
- Measured in conversations handled
- Results stay inside the agent's own tool
- Each new use case means another vendor
Cllr
- Runs many workflows across voice, WhatsApp, SMS and email
- Also starts work when an event fires in your systems
- Reads your CRM, billing, support and usage data
- Multi-day workflows that remember every earlier step
- Measured against the KPIs you set for each workflow
- Every outcome written back to the system of record
- New workflows reuse the same connections and rules
Your systems remain the source of truth
Cllr works within the systems you already run, and understands the full context of a case before it acts.
Questions about how Cllr works
How workflows start, what your team controls and where the results go.
Still have a question?
Talk to the team and we will answer it directly.
Start with the workflow that costs you most
Bring one process with a clear owner and a measurable baseline. We map it, test it against representative cases, and hold it to the KPI you set.