WhatsApp inbox & AI copilot
Who reads your dive center's WhatsApp while the team is underwater?
AbyssOS puts every WhatsApp enquiry in one team inbox on your own number, translated, with the booking facts already extracted and a reply drafted in the diver's language. Your staff send it in one tap, send the waiver and payment link from the same thread, and the booking lights up green in the Cockpit.
By the AbyssOS team · Updated 5 Nov 2026
2 divers · Saturday · fun dive · certified
Illustration with example data from our demo center.
Why the reply speed on WhatsApp decides the booking
Most dive enquiries now arrive on WhatsApp, often in the evening, often in a language your front desk does not read, and the diver is messaging three centers at once. The first clear answer with a price and a booking link usually wins. The problem is not that your team cannot answer; it is that the thread lives on one phone, the facts are buried in forty messages, and the waiver and deposit still have to be chased by hand afterwards.
One team inbox, on your own number
Your WhatsApp Business number connects to AbyssOS through Meta's official WhatsApp Business Platform. Every conversation lands in a shared inbox the whole front desk can see, with a conversation owner, customer search and a waiting indicator, so nothing depends on whose phone the message arrived on.
- • Official Meta Cloud API, embedded signup, your existing number
- • Shared inbox with owners, search and realtime updates
- • Conversation linked to the customer record and their bookings
- • Approved message templates synced from Meta, per language
An AI copilot that reads, translates and drafts
The AI does the reading. Your team does the sending.
Every incoming conversation is analysed: intent, language, urgency, a short summary, the translation of the last message, and the booking facts the diver has already given. The copilot then shows what is still missing to book, checks live availability from your real schedule, and drafts a reply in the diver's language from your prices and policies.
- • Date, party size, activity, certification level, hotel, email extracted
- • “Missing to book” chips with a combined question ready to send
- • Live spots left on the boat the diver is asking about
- • Editable draft: insert → review → send, never auto-sent
Booking, waiver and payment links from the chat
When the facts are in, your team sends the next step without leaving the conversation: a booking invitation, a waiver, a medical form, an invoice or payment link, or the diver portal. Each is a secure one-time deep link. When the diver completes it, the booking's readiness updates in the Cockpit, so the front desk sees “waiver signed, deposit paid” next to the chat.
- • Booking invitation, waiver, medical, invoice, portal
- • Secure deep links, no password for the diver
- • Default meeting point and pickup messages
Automations that run while you sleep
The messages that should go out unattended do: booking confirmations, pre-trip reminders a set number of days before the dive, and the two chases every dive center hates doing by hand, the unsigned waiver and the unpaid deposit. Each automation is opt-in per center, logged once per booking, and sent through the same path that enforces opt-outs and template rules.
- • Booking confirmation
- • Pre-trip reminder (you choose how many days before)
- • Waiver chase and deposit chase, with configurable lead time
- • Idempotent: one message per booking, per kind, per day
Five languages, one front desk
Saved replies live in a library with a slash shortcut and one variant per language, so “what to bring tomorrow” exists in English, French, Spanish, German and Italian and the right one is picked for the conversation. The copilot translates what comes in and drafts what goes out, and a tu/vous register setting keeps the tone right for your market.
- • Multilingual saved replies with
/shortcut - • Incoming messages translated for the team
- • Copilot knowledge base: upload your own price list and policies as PDF
Compliant by construction
There is exactly one path a message can take out of AbyssOS, and it enforces the rules every time: diver consent, STOP opt-outs, Meta's 24-hour customer-service window, approved templates outside that window, and a kill switch per center. The copilot cannot send anything itself and only ever proposes structured actions, so there is no way for it to invent a price or a promise in a message.
- • Official Meta WhatsApp Business Platform
- • Consent, STOP and the 24-hour window handled for you
- • Your conversations are never used to train shared models
- • Monthly copilot request cap you control
From “hola” to ready to dive, in one thread
A chatbot that answers alone is only useful until it quotes the wrong price or promises a wreck dive to an Open Water diver. AbyssOS keeps a person on every reply and removes everything around it: reading forty messages, translating, checking the boat, typing the answer, chasing the form, chasing the deposit. The diver gets an answer in their language within minutes; your team gets a booking that is already paid, signed and on the roster.
WhatsApp is a module of the same platform as your schedule, waivers, payments and finance, so the enquiry, the booking and the money are one record from the first message.
Questions dive center owners ask about WhatsApp
Does AbyssOS answer WhatsApp for us automatically?
Two things run on their own: automations (booking confirmation, pre-trip reminder, waiver chase and deposit chase) and the copilot analysis of every incoming conversation. Replies to a diver are drafted by the copilot and sent by your team in one tap, so nobody is quoted a wrong price or promised a dive site at 2 a.m.
What does the AI copilot actually do?
It reads each conversation, detects the intent, language and urgency, translates the last message, extracts the booking facts (date, party size, activity, certification level, hotel, email), lists what is still missing to book, checks live availability from your schedule, and proposes a saved reply or an editable draft in the customer’s language.
Is it the official WhatsApp Business API?
Yes. AbyssOS connects your own WhatsApp Business number through Meta’s WhatsApp Business Platform (Cloud API) with embedded signup. Consent, STOP opt-outs, the 24-hour customer-service window and approved templates are enforced by the platform on every message.
Which languages are supported?
Any language your divers write in. The copilot translates incoming messages for your team and drafts replies in the customer’s language. Saved replies and approved templates can be stored in several languages (English, French, Spanish, German, Italian and more) and the right one is picked per conversation.
Can we send a waiver or a payment link from the chat?
Yes. From any conversation your team can send a booking invitation, a waiver, a medical form, an invoice or payment link, or a portal link as a secure one-time deep link. When the diver completes it, the booking’s readiness updates in the Cockpit.
What happens to the message data?
Message content is used only to run the channel and the copilot for your center. We never train shared models on your conversations. See the WhatsApp section of our privacy policy for the full detail, including Meta’s role as a processor.
Related: booking engine · online payments · how WhatsApp data is handled · AbyssOS vs DiveOps
Answered. Booked. Signed.
WhatsApp • Copilot • Cockpit
See it on your own WhatsApp number.
We connect your number, load your prices and schedule into the copilot, and walk your team through a real enquiry on the demo call.