Skip to main content
By default, Flabs sends report and bill WhatsApp messages from the Flabs number (or your AiSensy account), and the CRM / Bookings page opens WhatsApp with its booking and quotation messages. If your lab uses another WhatsApp provider (Wati, Interakt, Gupshup, Meta Cloud API, …), they can go out from your own number instead.

​
How it works

  1. Register your webhook URL (once per branch).
  2. Add the templates to your provider.
  3. When your staff click Send, Flabs posts the event to your webhook, which sends the WhatsApp. Flabs itself sends nothing for that message.

​
Events

​
Key rules

  • An event is sent only where Flabs would send a WhatsApp anyway.
  • These are ordinary Flabs webhook events: registered, authenticated, delivered and retried exactly like bill.completed (see Webhooks).
  • Once your webhook is subscribed to an event, only your provider sends that message. If your webhook fails, Flabs retries it; it does not fall back to the Flabs number or AiSensy.
  • Register each WhatsApp event on one webhook per branch. Every webhook that includes an event receives it, so the same event on two webhooks sends the message twice (see Register).
  • Messages you have not subscribed to keep going out the normal way (AiSensy if configured, otherwise the Flabs number).
  • Bill and report messages carry the bill’s billID; CRM messages carry the lead’s leadID. Both stay the same on every resend.
To get started, see Connect Your WhatsApp Provider.