> ## 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.

# Quickstart

> Get a working voice agent answering calls in under 30 minutes.

This walks you through the tenant onboarding flow. Most of it happens with our operator team during your kickoff call. This page is so you know what to expect and what we'll need from you.

<Note>
  Vorel is invite-only. To start, [book a demo](https://vorel.ai/book-demo). Once your tenant is
  provisioned, your operator runs through these steps with you on a kickoff call (typically 1–2
  hours end-to-end).
</Note>

## What we need from you before the call

<Steps>
  <Step title="Business basics">
    Business name (English + Arabic if you want bilingual), preferred URL slug (e.g. `acme-clinic`),
    country code, timezone, and default language (`ar` or `en`).
  </Step>

  <Step title="Your vertical">
    One of: real estate, salon, clinic, restaurant, auto service, generic SMB. This drives the
    agent's default tone, suggested attribute keys for your offerings, and built-in safety phrases.
  </Step>

  <Step title="Primary contact">
    Email of the person on your team who'll have the operator role inside Vorel. They'll receive a
    sign-in invite.
  </Step>

  <Step title="CRM (if you use one)">
    Which CRM, and either (a) the credentials we'll connect via OAuth on the call (HubSpot,
    Salesforce, Zoho), or (b) the API credentials your team will provide for form-based connections
    (Mindbody, Tekmetric, Athenahealth, Odoo, custom webhook).
  </Step>

  <Step title="Voice number preference">
    Either we provision a UAE number from our pool (fastest), or we work with you on porting
    your existing number (longer; \~2-4 weeks).
  </Step>

  <Step title="Special requirements">
    Anything you've already decided about how the agent should behave: phrases it must never use,
    your business hours and holidays, how you want escalations handled (Slack channel? email? phone
    number?).
  </Step>
</Steps>

## What happens on the kickoff call

Your Vorel operator walks through these 10 steps live with you. Total time: typically 1–2 hours, depending on how many CRM connections + how many catalog rows we set up.

<AccordionGroup>
  <Accordion icon="building" title="Step 1: Create your tenant" defaultOpen>
    Your operator creates your Vorel tenant via our admin console. The vertical pack you picked
    seeds your persona, suggested attributes, and handoff rules.
  </Accordion>

  <Accordion icon="phone" title="Step 2: Claim your voice number">
    A UAE number from the pool is bound to your tenant. Calls to it route to Vorel's voice
    infrastructure.
  </Accordion>

  <Accordion icon="user-pen" title="Step 3: Configure persona, hours, handoff rules">
    Your operator walks you through the agent's name, tone, signature phrases, forbidden phrases,
    working hours (with timezone), and what triggers a human handoff.
  </Accordion>

  <Accordion icon="sliders" title="Step 4: Tenant-specific tuning (optional)">
    If you have specific brand-voice rules, want to disable specific tools (e.g. CRM-write if your
    CRM is read-only), or want a stricter set of forbidden phrases, your operator configures them
    here.
  </Accordion>

  <Accordion icon="address-book" title="Step 5: Connect your CRM">
    OAuth flow or form-based credential entry depending on your CRM. We test the connection live; if
    it doesn't work, we troubleshoot together.
  </Accordion>

  <Accordion icon="dollar-sign" title="Step 6: Per-tenant cost setup">
    For voice tenants, your operator captures your phone-number rental cost from the most recent
    invoice so your monthly cost rollup is accurate.
  </Accordion>

  <Accordion icon="user-plus" title="Step 7: Invite your team">
    Your primary contact gets a sign-in invite to your tenant org. They sign in, accept, and land on
    `/inbox` with the role you picked (`admin` / `agent` / `viewer`).
  </Accordion>

  <Accordion icon="key" title="Step 8: Issue an API key (if you'll use the API)">
    If you plan to integrate Vorel programmatically (n8n workflows, custom dashboards, mobile app),
    your team member issues their own API key from `/(dashboard)/settings/integrations/api-keys` and
    pastes it into their integration tool.
  </Accordion>

  <Accordion icon="vial" title="Step 9: Smoke test end-to-end">
    Your operator calls your number. The agent should answer, qualify, and either book or escalate
    per your rules. We verify the call lands in `/inbox` + the lead lands in your CRM. Repeat for
    chat if you've connected WhatsApp.
  </Accordion>

  <Accordion icon="circle-check" title="Step 10: Flip live">
    Your operator stamps the "live" gate. From this moment, your team's `/inbox` shows real customer
    traffic.
  </Accordion>
</AccordionGroup>

## After the kickoff call

<CardGroup cols={2}>
  <Card title="Day 2: first day of conversations">
    Check `/(dashboard)/analytics`. QA scores in expected range? Hallucination flags clean? Handoff
    rate looks normal? Anything weird, ping your operator.
  </Card>

  <Card title="Day 7: first week of traffic">
    Your operator schedules a check-in. Adjust prompts, tighten rules, refine handoffs based on what
    real customers asked.
  </Card>

  <Card title="Day 30: first month">
    Cost rollup is fully populated. Your operator reconciles vendor invoices and sends you the first
    month's invoice (until our automated billing model lands).
  </Card>

  <Card title="Ongoing">
    Operator-driven changes any time. The platform evolves with new vertical packs, new CRM drivers,
    and new product features. See the [changelog](https://vorel.ai/changelog).
  </Card>
</CardGroup>

## What you do day-to-day

After Day 1 you mostly just live in `app.vorel.ai/inbox`:

* **Pick up escalations** when the agent hands off a conversation (your handoff rules dictate when).
* **Reply manually** when you want to take over a conversation entirely (your team-member role determines whether you can).
* **Watch the analytics weekly** to see how the agent is performing.
* **Tell your operator** when you want adjustments, new features, or have new requirements.

For the developer-facing surface, see [API Reference](/api-reference/introduction).

{/* verified-against: apps/web/src/lib/api-key.ts + /api/keys route (per-user API-key issuance) */}

{/* verified-against: config/verticals/ (8 packs seed persona + handoff defaults at tenant create) */}