Yes. Clio uses the official Meta WhatsApp Cloud API, so your business must have a Meta-verified Business Portfolio and an eligible WhatsApp Business Account/number before connecting Clio. Clio does not bypass Meta’s verification or eligibility requirements.

Yes. Clio connects to your own WhatsApp Business Account through the official Meta Cloud API, so the number, the templates and the customer relationship all stay yours. We can walk you through the setup during onboarding.

If your number is already on an eligible WhatsApp Business Account with access to the Meta Cloud API, you can connect it to Clio. Numbers that only use the consumer WhatsApp app or unofficial automation tools must be migrated to the WhatsApp Business Platform through Meta first — Clio does not perform that migration for you.

Yes. That is a core part of Clio. Once a WhatsApp Business number is connected, your team works from a shared inbox around that number — with roles, permissions and a single customer history — instead of sharing a physical phone.

Clio uses the official Meta WhatsApp Cloud API and does not rely on WhatsApp Web automation or unofficial APIs. That said, Meta’s policies and quality requirements still apply to your account. Clio cannot guarantee that Meta will never restrict an account if messaging quality, opt-outs or template rules are violated.

WhatsApp only allows free-form replies within 24 hours of a customer’s last message. Outside that window, you must use an approved message template. Clio enforces the service window in the inbox so your team knows when free-form replies are allowed and when a template is required.

No. Meta bills messaging and conversation charges separately, according to Meta’s published rates for your market and category. Clio does not resell or mark up messaging — your subscription covers the Clio platform only.

Meta bills conversations separately, typically to the payment method on your WhatsApp Business Account, at their published rates. Clio does not mark them up. See Meta’s WhatsApp pricing documentation for current rates.

Yes. You can export contacts as CSV (with the same filters you use in the contacts list). Exports are available to roles with export permission and are recorded in the audit log so you know who exported what and when.

Yes — CSV import with column mapping and duplicate handling, plus a Google Sheets connection if your list already lives there. Export remains available so your data stays portable.

Credentials are encrypted at rest, webhooks are signature-verified, access is role-based, and sensitive actions are written to an immutable audit trail. Rate limiting and account lockout are on by default.

You can stop renewing when your current billing period ends. Before you leave, export your contacts (and any other data you need). After access ends, your team can no longer use the Clio workspace; disconnecting WhatsApp from Clio does not delete your Meta Business Portfolio or WhatsApp Business Account — those remain under your Meta ownership.