Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.vorel.ai/llms.txt

Use this file to discover all available pages before exploring further.

​
The product in one paragraph

Vorel is a multi-tenant AI receptionist platform. Your customers call your business phone number or message your WhatsApp; Vorel’s agent answers — in Arabic or English depending on what they speak — qualifies them with the questions you’d want a human receptionist to ask, answers their questions about your services from a vector-indexed knowledge base, books their appointments against your hours and rules, and writes the resulting lead + booking into your CRM. Every conversation is transcribed, scored for quality, and surfaced in a unified inbox. When the agent decides it’s out of its depth, it routes to a human on your team.

​
What you get when you become a customer

A dedicated phone number

A Telnyx UAE number (or your own ported number) routed through Vorel’s voice infrastructure. Inbound calls reach the agent; you see every call in your inbox.

A WhatsApp channel

Your business’s WhatsApp Cloud number connected to Vorel. Inbound messages reach the agent; outbound replies land back in WhatsApp.(Outbound currently in Phase 4b — fully operational once Meta Business Manager verification clears for your tenant.)

An operator dashboard

app.vorel.ai/inbox. Every conversation across voice + chat, in one place. Reply manually when needed; the agent handles the rest.

CRM integration

Vorel writes leads + bookings + updates back into HubSpot / Salesforce / Zoho / Mindbody / Tekmetric / Athenahealth / Odoo / your own webhook. Per-tenant field mapping lives in our admin console.

Per-tenant configuration

Your dedicated operator tunes the agent’s persona, working hours, signature phrases, forbidden phrases, handoff rules, vertical pack, and tool whitelist — all without a code deploy.

Per-tenant analytics

/(dashboard)/analytics — conversation counts, QA score distribution, voice-minute consumption, leads-to-bookings funnel.

Public API + SDK

REST API at /api/v1/* (full OpenAPI 3.1 spec) and a TypeScript SDK at @vorel/sdk for tenants who want to build custom integrations.

Around-the-brain workflows

n8n template workflows for post-booking confirmations, lead-nurture cadences, and weekly QA digests. Operator-deployed; tenant-isolated.

​
What Vorel is NOT

  • Not a chatbot platform. You’re not building flows in a no-code UI. The agent’s intent classification and tool calling happen via our LLM — your operator configures behaviour at the layer above.
  • Not a CRM. Your CRM stays your source of truth. Vorel reads from + writes to it, but doesn’t try to replace it.
  • Not self-service signup. We onboard tenants manually with our operator team — partly because we want to get the configuration right with you, partly because regulated verticals (clinics) need a real conversation about compliance scope before launch.
  • Not a contact-centre BPO. Human handoff is for edge cases (complaints, negotiations, compliance questions). The agent handles the steady-state inbound; humans handle exceptions.

​
What “vertical pack” means

Each vertical pack is a JSON file (config/verticals/<vertical>.json in our codebase) that ships:
  • Default agent name + tone for that vertical (in English + Arabic)
  • Suggested attribute keys for offerings (e.g. real-estate ships bedrooms / bathrooms / size_sqft; salon ships duration_minutes / category)
  • Pack-specific signature phrases + forbidden phrases (e.g. clinic packs ship forbidden_phrases='diagnose' to prevent obvious medical-advice issues)
  • Sensible defaults for handoff triggers (e.g. clinics escalate on any compliance-adjacent question; restaurants escalate on negotiation)
Your tenant inherits the pack at create time, then your operator can override individual fields per your needs at /admin/tenants/[id]/pack-overrides. The 6 packs we ship today: real_estate, salon, clinic, restaurant, auto_service, generic. New verticals = a new JSON file; we add them per signed customer demand.

​
How tenants think about Vorel

You’re not “building” anything. You’re getting a working AI receptionist that’s been tuned for your vertical, connected to your CRM, and deployed against a number that customers can already reach. Your job is to:
  1. Confirm the persona + hours match your business.
  2. Pick up your inbox when the agent escalates.
  3. Watch the analytics weekly to see how it’s performing.
  4. Let your operator know when you want adjustments (tighter rules, broader scope, new prompts for a campaign).
If you want to do more — build custom integrations, automate post-booking flows, write your own analytics dashboards — the API Reference and n8n integration are open.

​
Where to go next

Quickstart

Get a working voice agent in under 30 minutes.

How it works

Architecture overview for the technically curious.

Voice features

What the voice agent can do.

Security

How we protect your customer data.