Skip to main content

Integration channels

Booker4j is built as an API that returns assistant messages and form state. How users reach that API is up to the company or product integrating it.

Planned channel targets​

The following are planned integration targets. The core does not implement these channels itself; instead, adapters or middle layers would translate between the channel and the Booker4j API.

  • RCS (Rich Communication Services) — Messaging over carrier RCS. An adapter would receive RCS messages, call the Booker4j API, and send replies back over RCS.
  • SMS — Plain text messaging. An adapter would receive SMS, call the same API, and respond via SMS (within length and format constraints).
  • WhatsApp — Integration via the WhatsApp Business API. An adapter would receive WhatsApp messages, call Booker4j, and post the assistant reply and any structured content (e.g. buttons) back to WhatsApp.
  • Facebook Messenger — Same idea: an adapter receives Messenger events, calls the Booker4j API, and sends the assistant response (and optional quick replies or cards) back through Messenger.

How it works conceptually​

For each channel, a separate service or component would:

  1. Receive the incoming message or event from the channel.
  2. Map it to a customer ID and session ID (and optionally language).
  3. Call the Booker4j chat API with the message and those headers.
  4. Take the API response (assistant message, current question, form state) and format it for the channel (text, buttons, list, etc.).
  5. Send the formatted reply through the channel’s API.

So the same booking and conversation logic runs inside Booker4j; only the transport (RCS, SMS, WhatsApp, Messenger) and presentation (length, rich elements) differ per channel. No implementation details for these channels are specified here; they are listed as the intended integration directions.