Your brand on the front. The runtime underneath.
White-label the platform under your own brand. For CRMs, MSPs, resellers and marketing agencies adding voice to what they already sell.
What carries your brand, and what runs underneath
| Layer | Runs it | What it is |
|---|---|---|
| Your brand | Yours | The platform sold and presented under your own brand. |
| Agent platform | Alebex runs it | One AI system across voice, SMS and email, with one memory across channels. |
| Alebex Voice Engine | Alebex runs it | Streaming speech-to-text, turn control, hallucination gate, barge-in classification, multimodal intent, streaming synthesis. |
| Canadian data residency | Alebex runs it | Customer data stored in Canada. Built in Vancouver, Canadian-owned. Designed to support PIPEDA, CASL and applicable CRTC requirements, with configurable consent, disclosure, opt-out and retention controls. No certification implied. |
The platform is sold and presented as yours. The runtime, the guardrails and the data residency are ours to run.
What white-labelling gets you
What you bring to market without assembling the layers underneath.
What becomes yours. What stays ours.
White label changes the front of the product without asking you to become the voice infrastructure provider.
| Your side | Alebex side | |
|---|---|---|
| Brand | Your name and presentation are on the product. | Alebex stays behind the runtime rather than in front of your client. |
| Client relationship | You own the relationship with the client. | Alebex supports you as the platform partner. |
| Billing | The partner agreement sets whether you bill the client directly. | The same agreement records when Alebex bills the client instead. |
| Support boundary | The partner plan assigns who answers client questions first. | Alebex supports the runtime and infrastructure underneath the offer. |
| Runtime | You shape the client offer, workflows and handoff. | Alebex operates the voice engine and agent platform. |
| Infrastructure | You do not assemble the voice providers underneath the product. | Alebex runs the Canadian data residency as one system. |
| Compliance posture | You present the approved Canadian data and compliance posture to your clients. | Data is held in Canada. The platform is designed to support PIPEDA, CASL and applicable CRTC requirements, with configurable consent, disclosure, opt-out and retention controls. No certification implied. |
What you no longer have to build
Your team can stay focused on the client offer while the runtime remains underneath it.
Outbound calling, qualification and booking run on one thread across calls, texts and emails. An agentic core (Intent · Memory · Tools · Guardrails) turns conversation into action: qualify, book, resolve, update records, trigger tools, hand off.
Streaming STT, turn control, the hallucination gate and barge-in classification run in one runtime.
Barge-in detection that knows “uh-huh” isn’t an interruption (classifying raw audio, not energy heuristics), and word-level playback tracking — when interrupted, the agent resumes from what the caller actually heard, not what the model generated or the script assumed.
Canadian data residency, Canadian compliance
What your clients ask about, answered by the layer you are reselling rather than by you.
“We felt good that Alebex is built in Canada and the data is stored here. As an educational institution, compliance is important for us, so this was helpful when we decided to use Alebex.”
Recordings, transcripts and customer information are held in Canada.
A Vancouver-based Canadian AI company, incubated at the Alexander Innovation Centre.
Designed to support PIPEDA, CASL and applicable CRTC requirements, with configurable consent, disclosure, opt-out and retention controls. No certification implied.
Configurable opt-out controls across channels, with the contact flagged.
Configurable call-recording consent disclosure, with recordings stored for audit.