Frequently asked questions

No. The platform is built on the linked-device (multi-device) protocol. You link your own numbers by scanning a QR code — no Meta approval process, no per-message API fees. Built-in pacing, verification and number-health tools help protect your numbers.

In the browser Agent Console — answer, mute, record and chat from any modern browser — or on any SIP softphone/PBX registered against the built-in SIP gateway. Calls route by extension, department or first-available, with queues and voicemail as fallback.

Yes. Link as many numbers as your plan allows and design unlimited flow variations in the visual builder: assign a flow per number, a tenant-wide default, and a separate after-hours flow.

Every workspace has a prepaid wallet. Request a top-up, the operator approves it, and plans are purchased from the balance. Included quotas reset monthly; extra usage is pay-as-you-go per country.

Yes. Connect any OpenAI-compatible LLM for an AI voice agent that answers from your knowledge base, and voice prompts with ElevenLabs text-to-speech or your own uploaded audio.

A WhatsApp call center answers voice calls made to a WhatsApp Business or personal number instead of a traditional phone line. Callers use the free in-app call button; software answers, plays an IVR menu and routes the call to human agents — exactly like a PBX, but over WhatsApp.

Two ways: the browser Agent Console (answer, mute, record, transfer from any modern browser) or any SIP softphone/PBX registered against the built-in SIP gateway. Routing supports extensions, departments and first-available with queueing and voicemail fallback.

Yes — concurrency is plan-based. Extra callers wait in a hold queue with music, position announcements and callback offers, and are dispatched serially as agents free up.

Yes. On plans with call recording, every call can be auto-recorded end-to-end — IVR prompts, caller audio and the agent leg mixed onto one timeline — with an in-app player, download and retention controls.

Yes. The built-in SIP gateway registers softphones like Zoiper or MicroSIP (or a PBX trunk) and bridges WhatsApp audio to SIP with parallel targeted ringing, caller-ID and blind transfer via REFER.

A voice broadcast automatically calls a list of WhatsApp numbers and plays a pre-recorded or AI-generated voice message to each person who answers — like a robocall campaign, but over free WhatsApp calling.

Yes. Add a name greeting like “Hello {{name}}” and it is spoken first on every answered call using text-to-speech. Recipients without a name skip the greeting automatically, so nobody hears a broken “Hello ,”.

Both. Upload a recorded WAV/MP3 clip, or type your message and let ElevenLabs text-to-speech speak it — including with your own ElevenLabs account and cloned voice if you connect one.

You control rate-per-minute plus a random delay range between calls. Campaigns balance across every connected number you have and skip quarantined or over-limit numbers automatically.

Each plan includes free monthly broadcast minutes. After they are used, calls continue pay-as-you-go per second at the destination country’s rate, debited from your prepaid wallet. Prepaid call-plan bundles can add discounted minutes.

Any unofficial bulk activity carries risk. The platform ships number-health tracking, manual quarantine, per-number outbound caps and randomized pacing to keep sending behavior conservative — but always warm up numbers and message people who expect to hear from you.

An IVR (Interactive Voice Response) answers calls with recorded or AI-spoken menus — “press 1 for sales, 2 for support” — and routes the caller. A WhatsApp IVR does this for calls made to your WhatsApp number instead of a phone line.

No. Flows are built on a visual canvas with drag-and-drop blocks and connected branches. Developers can still use Webhook blocks to call external APIs and branch on the response.

Three ways: keypad tones (detected in-band), digits typed into the WhatsApp chat during the call, or spoken words when speech recognition is configured — including instant realtime voice catch with language detection.

ElevenLabs natural AI voices (with per-tenant accounts supported), Cartesia or PlayHT via admin config, uploaded WAV/MP3 recordings, or the built-in system voice as a fallback. Prompts are cached, so repeated text costs nothing.

Yes. Each WhatsApp number can have its own assigned flow, with a tenant-wide default and a separate after-hours flow driven by your business-hours schedule.

Yes — the Live agent block rings browser agents and SIP softphones with queues, hold music, queue-position announcements, callback offers and post-call rating surveys.

Link your own WhatsApp numbers by QR code; the platform sends through the linked-device protocol — no Meta approval, no per-message conversation fees. Pacing and verification tools are built in to keep sending behavior safe.

Yes — {{name}} and {{number}} placeholders fill per recipient from your contact book or uploaded name,phone lines, in the text, caption and even button labels.

Buttons ride on text broadcasts as native interactive messages (quick reply, URL, call, copy code). WhatsApp does not officially support buttons from normal senders, so some recipient apps render them and others show only the text — the message itself always arrives, with automatic plain-text fallback.

Yes — enable the WhatsApp check pass and the campaign verifies every recipient before sending, or use the standalone Number Checker to clean lists and save results into contact groups.

Each plan sets a monthly bulk-message quota (0 = unlimited) plus read/seen tracking quotas. Past the free quota, sends continue pay-as-you-go at per-country rates from your wallet.

Aggressive sending can. Use the built-in random delays, batch pauses, number verification, per-number daily caps and warm-up discipline, and always message people who expect to hear from you.

Yes. Owners and agents share the same inbox in the browser; every conversation, receipt and reaction syncs in real time over WebSocket for everyone.

Yes — opening a thread marks it read and sends the customer blue ticks, and your outbound messages show sent/delivered/seen ticks live.

Yes. Record in the browser and it is delivered as a native WhatsApp PTT voice bubble with waveform — no apps or converters needed.

Yes — group threads appear in the inbox with per-sender attribution, and you can send text and media to groups.

Yes — every thread has a call button that opens the softphone, auto-dials the contact and returns you to the same thread when the call ends.

Recent history syncs when you pair the number, and each thread has a “Sync older” action that asks the phone for 50 older messages at a time.

It is part of the same platform and dashboard — customers, pipeline, tasks, reports and automations ship with the product, gated by your plan.

Yes — bulk CSV import with upsert, plus export at any time. Duplicate detection and merge keep the book clean.

Yes — the CRM lives beside the call center, live chat and campaigns, so contact names personalize broadcasts and agents see who is calling.

Yes — owners define custom fields (text, numbers, dates and more) that appear on every customer profile.

The platform exposes a scoped public API with API keys and signed webhooks, so external systems can read calls and push order-confirmation jobs.

Your store calls a REST API with the order details. The platform places a WhatsApp call to the customer, speaks the order in a natural AI voice (or your recorded clips), and captures the decision: press 1 to confirm / 2 to cancel, say a keyword, or reply in chat. The outcome fires a webhook to your system.

You choose: retry via your own logic on the order.no_answer webhook, or use message-first mode — an ask message, an automatic reminder, then an escalation call after a configurable delay.

Yes — configure an IVR digit (e.g. press 3) and the call plays a transfer prompt and hands the customer to your main IVR flow with menus and live agents.

Anything that can send an HTTP request: WooCommerce, Shopify apps, custom carts, Google Sheets scripts or n8n/Zapier-style tools. The API is a single JSON POST plus webhooks.

Order calls meter per second against your plan’s included call minutes, then pay-as-you-go from the wallet at admin-set AI/manual rates.

Upload the list; the platform queries WhatsApp through your linked number and marks each entry as on or off WhatsApp within seconds to minutes depending on size.

Lists of thousands are fine; your plan sets the monthly check quota. Progress streams live and you can re-check a saved filter later.

Yes — both result sets export as .txt or .csv, and either can be saved into your contact book as a group for use in bulk message or voice broadcast campaigns.

Verification uses standard contact-existence queries. As with all bulk activity, quotas and pacing keep behavior conservative.

Yes — because the platform terminates the call server-side, it can tee all audio into a recording session: IVR prompts, the caller and the agent leg are mixed onto one aligned timeline WAV.

No — campaign/broadcast calls are never auto-recorded by design. Recording covers real conversations: inbound calls and dialer calls.

Owners see all tenant recordings; agents see only their own calls. Deleting is owner-only and removes the stored audio.

A configurable retention window (default 7 days) auto-deletes old audio; set it longer or to keep-forever as policy requires.

That is your legal responsibility and varies by country — add a “this call may be recorded” line to your IVR greeting where required.

Share your public booking link (it works for logged-out visitors); the customer picks a service and a slot and submits — no account needed.

In the Appointments page of your dashboard, visible to your team, alongside the customer’s calls and chats.

Yes — owners create, edit and disable services and adjust booking settings from the dashboard.

It is a lightweight booking layer built for WhatsApp-first businesses; export or sync needs can ride on the platform’s API and webhooks.