Archus Lab Request access

Customer messaging · WhatsApp Business Platform

The CRM for
businesses that
actually reply.

One shared WhatsApp inbox, a contact record that remembers every conversation, and approved templates that go only to people who opted in. Every thread can reach a human.

Request access How the integration works
Channel
WhatsApp Business Platform, Cloud API
Onboarding
Meta Embedded Signup — you keep ownership of your WABA
Message policy
Opt-in only. Every thread carries opt-out and human handover
Operated from
{{COUNTRY}} · {{LEGAL_ENTITY}}

§01 — What Archus Lab is

A customer record and a conversation, in the same window.

Most teams answer customers from a personal phone — and lose the thread when that person is off. Archus Lab moves those conversations onto the business's own number, where they belong to the company.

01

Shared inbox

Every inbound message lands in one queue. Assign, note, resolve — no thread stuck in someone's pocket, no customer answered twice.

02

Contacts & history

Each contact holds full history, consent status, tags, and the fields your team defines — so the next person knows where things stood.

03

Templates

Draft a template, submit it to Meta from inside Archus Lab, track its approval. Only approved templates reopen a conversation outside the 24-hour window.

04

Handover

Automation routes; it never traps. Any customer can type agent to reach a person; any teammate can take over with one click.

§02 — The WhatsApp integration

Exactly what we ask Meta for, and exactly what we do with it.

Two permissions make the integration work. We request no others, and each maps to a feature you can see in the product.

Permission whatsapp_business_management

What we do with it. Manage the WhatsApp Business Account a customer connects: register their number, show display name and quality rating, and create, submit, and delete the templates they author in our editor.

What we never do with it. Touch any WABA not connected to us through Embedded Signup by that business's own admin.

Permission whatsapp_business_messaging

What we do with it. Send and receive on the connected number: deliver agent replies, send approved templates to opted-in contacts, receive inbound messages by webhook, mark them read.

What we never do with it. Send to purchased or scraped lists, blast bulk promotions, or message anyone who opted out.

You keep your WhatsApp Business Account. Connection happens through Meta's Embedded Signup inside your own Meta login; the WABA, number, and billing stay in your Business Manager. Disconnect any time and our access ends immediately — see Data deletion.

§03 — Onboarding

From signed-up to answering, in five steps.

Five steps, the same for every customer — and the sequence shown in our demo recording.

  1. Create an Archus Lab workspace

    An admin signs up, names the workspace, and invites the colleagues who answer messages.

  2. Connect WhatsApp through Embedded Signup

    The admin clicks Connect WhatsApp and signs in with their own Meta account — keeping an existing WhatsApp Business app number, chat history included, or registering a new one. We never see a Meta password.

  3. Bring contacts in, with their consent recorded

    Import your list with each contact's opt-in source and date, or collect consent going forward. No recorded opt-in, no templates — enforced at send time.

  4. Write and submit templates

    Write the notifications you actually need and submit them to Meta from the editor. Approval status shows against each one.

  5. Answer from the shared inbox

    Inbound messages arrive in the queue. Agents reply, assign, resolve; opt-outs are honoured automatically.

§05 — Who it is for

Small teams with a real queue of customers.

Built for teams where the same conversation is picked up by different people on different days — and getting it wrong costs an appointment.

A

Education

Tuition centres coordinating class changes, make-up lessons, and term reminders with parents who all message one front desk.

B

Clinics & practices

Appointment confirmations and reschedules — a missed reply is an empty chair.

C

Services & trades

Quotes, scheduling, arrival windows — the conversations that currently live on one manager's phone.

D

Retail & e-commerce

Order and delivery updates to customers who opted in at checkout, in the same thread they reply to.

§06 — Data & security

Message data is your customers'. We are its custodian, not its owner.

Archus Lab processes personal data on behalf of the business using it. What we collect, why, how long, and how to delete it — in plain language.

01

Encrypted in transit and at rest

All traffic over TLS 1.2+. Message content and contact records are encrypted at rest on {{HOSTING_PROVIDER}} infrastructure in {{DATA_REGION}}.

02

Separated by workspace

Every record is scoped to its workspace; access is role-based; admin actions are audit-logged.

03

Kept only as long as it is needed

Retention is set per workspace. On termination, data is deleted within {{RETENTION_DAYS}} days — see Data deletion.

04

Never sold, never resold

We don't sell personal data, and never use one customer's messages to market to another. Sub-processors are listed in the Privacy Policy.

Get started

Tell us what your team is answering today.

Archus Lab is onboarding businesses now. Tell us how many people answer and roughly how many conversations a week — we'll show you the platform on your own workflow.

Request access hello@archuslab.com