Customer service · Alebex
Solutions / Use cases

Resolve what is answerable. Escalate the rest, with context.

The agent handles service conversations inside the approved knowledge, and hands the rest to a person with the whole conversation attached rather than a ticket number.

9:41 Illustrative walkthrough
Service thread · illustrative
Customer The answer I need is not in the information I was sent.
A Agent I can answer what is inside the approved knowledge. I will carry this thread to a person for the rest.
Guardrail

The unanswered part is preserved as the reason for escalation, not replaced with a guess.

Illustrative service correspondence · rendered example
Status Illustrative walkthrough The sequence below describes how an agent would run this workflow.
Coming soon This walkthrough starts with a call coming in.

This walkthrough begins with a conversation coming in. Inbound communication is not available yet. Outbound calling, qualification, booking and the record-keeping described below run on the platform today.

Runs on the platform today
Outbound calling on the same runtime. Qualification against the criteria you approve. Booking, confirming and rescheduling. SMS and email on the same thread, with the same memory. The record, and the workflows behind it.
Not available yet
Answering a call that comes in. Answering a message that comes in.

Everything below is written as the workflow would run once inbound ships. The sequence, the scope and the handoff are the parts that do not change.

On this page How it runs Where it stops Related walkthroughs Live demo
How the workflow runs

Where the approved knowledge ends

Question in, resolution or escalation out — on one thread, with one memory.

Question in, resolution or escalation out
01 Voice
The question arrives

On voice, SMS or email — whichever the customer chose.

02 Agentic core
Checked against approved knowledge

Every sentence the model produces is checked before the caller can hear it, in parallel with speaking.

03 Agentic core
Resolved, or escalated

Resolved inside the approved answers, or handed to a person with the thread already open.

04 Email
The customer is kept informed

On the same thread, on whichever channel they used.

One thread, whichever lane a step sits in.

Where the agent stops

In scope, out of scope

In scope
The agent handles
Questions answerable from the approved knowledge.
The same conversation across voice, SMS and email.
Updating the record and triggering the workflows behind it.
Escalation, with the thread attached.
Honouring an opt-out immediately, on every channel.
Out of scope
The agent hands off
Anything outside the approved answers and workflows.
Any commitment your brand has not approved.
Anyone who asks to speak to a person.

The guardrail layer decides what is answerable. The agent does not decide for itself.

Resolution

A grounded handoff is a valid service outcome.

The agent resolves what the approved knowledge can support and makes the boundary legible when a person should take over.

Live demo

Try the live demo

Drop in your website. Alebex reads it, learns what you do, and calls you in under 30 seconds — fully trained, zero setup.

Free demo No credit card Available in Canada and the US
Alebex reads it and learns what you do.
So the agent knows who it is speaking to.
Canadian and US numbers. Alebex calls this number.

No business name needed — Alebex takes that from the site.

Call me

By submitting, you agree to receive a call and a follow-up SMS from Alebex. Reply STOP on any channel to opt out at any time. How we handle your details: Privacy.