Skip to main content
Vorel answers your inbound calls and messages, qualifies the customer, answers questions from your own knowledge, books appointments, and writes the result into your CRM. Your team works the same conversations from a shared inbox, or from Telegram and WhatsApp without opening the dashboard. It is bilingual (Arabic and English), MENA-focused, and configured per industry through vertical packs.
The agent is stateful. It is not a chatbot that starts from zero every time. It carries one persistent memory per customer across every conversation, every channel and every system you have connected, and that state reaches every turn. A customer who called in March and messages on WhatsApp in August does not start again. See Memory and state.

Quickstart

Take your first live conversation.

What is Vorel

The product, what you get, and what it is not.

How it works

The path a conversation takes, end to end.

API Reference

REST API, TypeScript SDK, webhooks, and MCP.

​
Where conversations come from

Every channel reaches the same agent and lands in the same inbox. A customer who calls today and messages tomorrow continues one conversation.

Voice

Inbound and outbound calls on your own numbers.

WhatsApp

Your WhatsApp Business number, connected directly to Meta.

Web chat

An embeddable widget for your site.

Instagram and Messenger

Social DMs on one connection.

Email

An address the agent reads, triages and answers.

Team assistants

Telegram, WhatsApp and MCP for your staff.

​
What the platform does around the agent

Shared inbox

Assignment, internal notes, mentions, labels, priority, SLA policies and CSAT surveys.

Memory and state

One persistent memory per customer, across every conversation, channel and connected system.

Knowledge

Upload documents, import from URLs, and see which questions you have no answer for.

Automation

Rules that fire on CRM events, product analytics, or your own webhooks.

CRM

27 drivers with per-tenant field mapping, reads and writes.

​
What makes Vorel different

  • It is stateful, and most of the category is not. One persistent memory per customer, built from every past conversation, your CRM, their bookings, their open cases and their consent history. Facts carry provenance and supersede rather than overwrite, so the agent knows what it knows, what it used to believe, and how sure it is. See Memory and state.
  • One agent behind every channel. Voice, WhatsApp, web chat, email and social DMs share the same router, the same tools, the same knowledge and the same memory. Identity is keyed on the person, not the channel, so state carries across all of them.
  • Real CRM writes, not just reads. 27 driver implementations, with per-tenant field mapping so the agent writes to your field names rather than generic ones.
  • Configurable safety per workspace. You set the phrases the agent can never use, the tools it can reach, and how strictly its answers are graded, without waiting on a release.
  • Your team does not have to live in the dashboard. Escalations, replies and approvals work from Telegram and WhatsApp, and any MCP client can query the workspace directly.
  • Bilingual by default. Arabic and English in the same conversation, answered in whichever language the customer used.

​
Get started

1

Book a demo

vorel.ai/book-demo. See Vorel running on a live workspace.
2

Onboard

Your Vorel operator sets up the workspace: numbers, persona, vertical pack, channels, CRM connection and team invites.
3

Smoke test

Run a real conversation on each channel you plan to use and confirm the lead lands in your CRM.
4

Go live

Turn the agent on. Vorel takes inbound traffic immediately.
Vorel onboards each workspace with our operator team rather than through self-service signup. To get started, book a demo.