Loading...
The comms deck · WhatsApp
Connect WhatsApp the official way or pair a personal number by QR. An AI agent triages each message, answers from the knowledge you give it, and — in supervised mode — parks every draft until you approve it. One is parked in the thread right here.
Sana K.
Customer · online
Parked sends
0
Service window
open · free text OK
Sample conversation · not a customer claim
Official WhatsApp Business runs on Meta's Cloud API — templates, campaigns, automation, analytics. Personal WhatsApp pairs by QR code and does live chat only. The product tells you which is which before you connect, not after.
Pick a door
Official WhatsApp Business
Meta Cloud API · embedded signup, OAuth or credentials
Personal WhatsApp
QR pairing · scan from your phone
Connecting either costs nothing · switch or run both
Meta opens a 24-hour service window each time a customer messages you. Inside it, free text flows. Outside it, only a Meta-approved template delivers — the API accepts cold free text and quietly drops it. wrrk checks the window before the send and would rather refuse than fake a “sent”.
The 24-hour service window
Checked before every send
If we can’t read the window · we treat it as closed
Meta reviews templates in minutes to 24 hours
Four modes: off, copilot, supervised, autonomous. In supervised mode every draft parks until you approve it. Answers come from the knowledge you assign the agent — and each AI reply costs one credit. The meter is on the reply, never on the reading.
One agent, four modes
A campaign is an approved template, an audience — everyone, a label, or your own list — and a schedule. A chat flow answers on its own rails: message, collect a field, offer a menu, run an action, book a meeting, hand off to the agent. One flow is live per workspace at a time.
A campaign, then a flow
Sample dataTemplate
order_update
APPROVEDAudience
Label · Repeat buyers
214Schedule
Tomorrow · 09:00
queuedOnly approved templates can start a campaign
Then the flow answers the replies
One flow live per workspace · hand-off to the agent is a step, not a default
Default reply caps: 50 an hour, 500 a day, 5 in a row before the agent stands down — the streak resets when the customer writes back — and a human takes the thread after 10. Business hours run on the clock, escalations on the content, and every send passes an org-wide rate limit. The counters live in the platform, not the prompt.
Default limits · adjustable per agent
Sample datathen it waits for the next hour
then it waits for tomorrow
stands down until the customer writes back
After 10 replies · a human takes the thread
Every send · org-wide limit of 100 a minute
The streak resets when the customer writes back
Sample conversations · not a customer claim. Caps and limits shown are the platform defaults.
Connect a number, teach the agent your knowledge, keep the approvals. The wrrk answers.