Shared inbox
Every inbound message lands in one queue. Assign it, note it, close it. Nothing sits unread in someone's pocket, and nobody gets answered twice.
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.
- 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
- Singapore · Archus Lab
What Archus Lab is
A customer record and a conversation, in the same window.
Most teams answer customers from a personal phone, then 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.
Contacts & history
Each contact holds full history, consent status, tags, and the fields your team defines, so whoever picks it up next knows where things stood.
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.
Handover
Automation never gets the last word. Any customer can type agent to reach a person; any teammate can take over with one click.
The WhatsApp integration
The two permissions we ask Meta for, and what each one does.
The integration needs two permissions. We ask for nothing else, and each one maps to a feature you can see in the product.
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.
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.
Onboarding
From signed-up to answering, in five steps.
The same five steps for every customer, and the same sequence you will see in our demo recording.
-
Create an Archus Lab workspace
An admin signs up, names the workspace, and invites the colleagues who answer messages.
-
Connect WhatsApp through Embedded Signup
The admin clicks Connect WhatsApp and signs in with their own Meta account. They can keep an existing WhatsApp Business app number, chat history included, or register a new one. We never see a Meta password.
-
Bring contacts in, opt-outs included
Synced contacts are reachable straight away. When you import a list, map its unsubscribe column to Opted Out. Getting opt-in is your responsibility under WhatsApp's policy. Once someone opts out, a template to them will not send. That check runs at send time.
-
Write and submit templates
Write the notifications you actually need and submit them to Meta from the editor. Approval status shows against each one.
-
Answer from the shared inbox
Inbound messages arrive in the queue. Agents reply, assign, resolve; opt-outs are honoured automatically.
Already running on the WhatsApp Business app? Step two is Meta Coexistence: same number, the app keeps working, and up to 180 days of history syncs in. It has its own step-by-step guide: read the Coexistence setup.
Consent & control
Opt-outs are honoured automatically, and every thread can reach a person.
Getting opt-in stays with you, as WhatsApp's Business Policy says. Honouring opt-outs is built into the product instead of left for you to remember. Once someone opts out, by replying STOP, by stopping marketing in WhatsApp, or because your team marked them, the block happens at send time, so nothing is queued in the first place.
What Archus Lab is for
- Answering customers who messaged the business
- Service notifications people asked to receive
- Appointment, order, and renewal updates
- Support threads a named agent owns and closes
What it is not for
- Bulk or promotional broadcasting
- Purchased, scraped, or rented contact lists
- Messaging anyone who has opted out
- Bots with no route to a human being
Northside Dental
Reminder · 3 Sep
Hi Priya, your cleaning is Thu 3 Sep, 4:15pm. Reply C to confirm, R to reschedule, or STOP to opt out of reminders.
C. Can I move it 30 minutes later?
agent
Customer asked for a human · automation paused, thread unassigned
Getting a person for you.
Priya, this is Dan at Northside. 4:45pm on the 3rd is free. Shall I move you?
Yes please. And STOP, no more reminders after this.
Opt-out honoured · templates blocked at send time
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.
Education
Tuition centres coordinating class changes, make-up lessons, and term reminders with parents who all message one front desk.
Clinics & practices
Appointment confirmations and reschedules, where a missed reply is an empty chair.
Services & trades
Quotes, scheduling, and arrival windows: the conversations that currently live on one manager's phone.
Retail & e-commerce
Order and delivery updates to customers who opted in at checkout, in the same thread they reply to.
And when we are not the right fit. If the plan is one-way bulk broadcast to the biggest list you can assemble, a mass sender will make you happier than we will, since our opt-out checks will only get in your way. If you need Meta's webhooks routed to your own backend with no inbox at all, a lightweight integration layer is the better buy. Archus Lab is for teams who want the conversations held, properly: scoped to your workspace, retained on your schedule, deleted on your say-so.
Data & security
The messages belong to your customers. We only hold them for you.
Archus Lab processes personal data on behalf of the business using it. What we collect, why we collect it, how long we keep it, and how to have it deleted.
Encrypted in transit and at rest
All traffic over TLS 1.2+. Message content and contact records are encrypted at rest on Supabase (on AWS) infrastructure in Singapore (ap-southeast-1).
Separated by workspace
Every record is scoped to its workspace; access is role-based; admin actions are audit-logged.
Kept only as long as it is needed
Retention is set per workspace. On termination, data is deleted within 30 days. See Data deletion.
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, and we will show you the platform running on your own workflow.