Skip to main content
Onboarding happens with our operator team on a kickoff call. This page tells you what to prepare and what to expect.
To start, book a demo. Once your workspace is provisioned, your operator runs through these steps with you, typically in 1–2 hours end to end.

What to prepare before the call

1

Business basics

Business name (English and Arabic if you want both), preferred URL slug, country code, timezone, and default language.
2

Your vertical

Real estate (sales or rental), salon, clinic, restaurant, auto service, legal intake, or generic. This seeds the agent’s tone, your offering attributes, and the built-in safety phrases.
3

Primary contact

The person on your team who will hold the owner role. They receive the sign-in invite.
4

CRM credentials

Which CRM, and either OAuth (we connect it live on the call) or API credentials your team provides. See the driver list for what each one needs.
5

Channels you want live on day one

Phone number (from our pool, or a port of your existing number), WhatsApp Business, the web widget, Instagram or Messenger, an email address. You do not have to start with all of them.
6

Rules you have already decided

Phrases the agent must never use, your business hours and holidays, and where escalations should go (a Slack channel, a Telegram group, staff WhatsApp numbers, or email).

On the kickoff call

Create the workspace

Your operator creates the workspace. The vertical pack seeds persona, suggested offering attributes and handoff rules.
One or more numbers are bound to the workspace, each with a role (inbound, outbound, or both) and a concurrency limit. See Voice.
WhatsApp connects directly through Meta. Instagram and Messenger connect on one Meta app. The web widget is a script tag. Email is a forwarding address plus triage rules.
Agent name, tone, signature phrases, forbidden phrases, working hours with timezone, and what triggers a human handoff. All of this stays editable in the console afterwards.
OAuth or form-based credentials, then a live connection test. Field mapping is set here too, so the agent writes to your field names.
Upload documents, import from your website, or paste answers directly. The agent answers from this, not from general world knowledge. See Knowledge.
Team members sign in and land on the inbox with the role you picked (owner, admin, agent or viewer). See Access control.
A real call, a real WhatsApp message, a real widget session. Confirm each lands in the inbox and the lead reaches your CRM.
The agent starts taking real traffic.

Your first week

Day 1

Watch the inbox. Confirm escalations reach the right people on the right channel, and that bookings appear in your calendar and CRM.

Day 2

Check Quality. QA scores in range, no hallucination flags, handoff rate where you expect it.

Day 7

Review the knowledge gaps the platform found. Every gap is a question customers asked that you have no answer for. Fill the high-impact ones.

Day 30

Set SLA policies and turn on CSAT now that you know your real volume and response patterns.

What you do day to day

  • Work the inbox. Pick up escalations, assign threads, leave internal notes for colleagues.
  • Correct the agent. Fixing a wrong category or a wrong answer teaches it. See Categories.
  • Fill knowledge gaps. The platform tells you what it could not answer.
  • Adjust rules yourself. Persona, hours, tools, routing, SLA, triggers and categories are all self-serve in Settings.
If you never want to open the dashboard, connect a team assistant and work from Telegram or WhatsApp instead.