Skip to content
Help Center

How can we help?

Short guides for every part of the platform — from your first sign-in to branch controls and provider troubleshooting.

Getting Started

Deploying the platform

Right Agent Group deploys on your own server against your own PostgreSQL database. The deployment guide covers environment variables, provider keys and first-run checks — your data never leaves infrastructure you control.

Signing in to the console

Team members sign in with Google sign-in. Access is limited to allowlisted email addresses, and admins can additionally require two-factor. If you can't sign in, ask your Admin to check the allowlist.

Understanding roles

Five built-in roles — Admin, Branch Manager, Agent, Viewer and Developer — control what each person sees and can do, and custom roles can be created for specific needs. Permissions are enforced on every API call, not just in the interface.

AI Employees

Creating an AI employee

AI Employees are managed from their own console screen. You define the employee's name, script, languages and channels, and scope them to branches. Each employee works the channels you assign — phone, WhatsApp or both.

Pausing the AI instantly

The kill switch stops AI calls and automated messages with one click. Pausing can be scoped globally or per branch, and paused leads return to your team's manual queue — nothing is lost, everything waits.

Scripts and the knowledge base

Scripts define what the AI says and asks, per channel. The knowledge base grounds every answer: upload your FAQs as documents or CSV, and the AI quotes your approved information instead of improvising.

Voice Calling

How the call queue works

Leads land in a call queue with the campaign's talking points attached. The AI works the queue within your calling-hour rules and DND lists, and every attempt is logged against the lead.

Call outcomes and recordings

Every call ends with an outcome, a recording and a transcript. Authorized roles can play recordings from the Calls area of the console — access is role-gated and audited.

WhatsApp

Connecting WhatsApp

WhatsApp connects through the official Meta WhatsApp Business Cloud API — no QR codes or unofficial libraries. Number verification and webhook setup happen once, during onboarding with your team.

Auto-replies and follow-ups

The AI answers inbound WhatsApp messages and voice calls, and sends follow-ups including secure application links. Business-initiated messages follow compliance rules — DND and consent are checked before anything is sent.

Leads

Importing leads

Upload CSV lead lists, or let leads flow in from web forms, WhatsApp and Instagram automatically. Every lead lands in one pipeline with its source recorded, so you always know where it came from.

Statuses and callbacks

Move leads through statuses as they qualify, schedule callbacks, and let the AI handle automatic retries within calling windows. Lead Brain keeps a running memory of every conversation so nobody re-asks what the customer already answered.

Applications

Sending application forms

Send a secure application link to any lead over WhatsApp. The customer fills the form on their phone, and submission status is tracked on the lead — no paper, no copy-paste.

Branches

Adding a branch

Create branches from the Branches screen. Each branch can have its own phone numbers, scripts, AI employees and call quotas. Branch staff see only their branch; Admins see everything.

Team Access

Modules and permissions

Console modules can be allotted per role, and custom roles combine the permissions your team needs. Every API request re-checks permissions server-side, so restricting the menu always restricts the capability.

Analytics

Reading the qualification funnel

Analytics cover call volume, the qualification funnel, sentiment trends and branch performance. Data can be exported for your own reporting — the console shows the same conversations the AI and your team actually had.

Security

Kill switch, audit logs and IP allowlist

Pause all AI activity with the kill switch, trace sensitive actions in the audit log, and restrict console access to approved network ranges with the IP allowlist. These controls live in the Security area, Admin-only.

Troubleshooting

Call audio and provider keys

Most call-audio and connection problems trace to provider configuration — check provider keys, webhook status and recent errors in the developer logs view. Recordings for each call are attached to the call entry for playback.