Offer configured availability
The booking node generates slots from the workflow’s timezone, weekly hours, slot length, lead time, booking horizon, and capacity.
For bookings and payments
Turn WhatsApp intent into a confirmed, paid booking.
Collect the right details, offer configured availability, request a deposit or full payment, and retain the appointment record inside the workflow.
The problem
Intent is not a booking until the operational details are settled
A WhatsApp request needs the right service, customer details, a valid slot, and sometimes payment before the team can count it as confirmed. The workflow makes each of those decisions explicit.
Outcomes
Booking outcomes to review
- Configured slots that respect the workflow’s availability rules.
- A captured appointment reference and status.
- A payment branch that continues only through its configured result.
- A visible unavailable and error path instead of an ambiguous customer dead end.
Capabilities
The tools behind the work
Collect the details you need
Ask workflow questions before the booking node and retain the customer and appointment record in Fluenta.
Request a deposit or full payment
The payment node supports Stripe and Paystack hosted checkout, with required success and error branches.
Review booking outcomes
Inspect appointment records and workflow activity after the conversation.
How a flow looks
A booking journey with explicit outcomes
Build the customer request, service selection, availability, payment, confirmation, and exception paths as steps your team can inspect.
Request
Capture the service need
Ask for the service and customer details before showing a slot.
Availability
Offer bookable slots
The booking node offers currently valid configured slots, up to ten choices in WhatsApp.
Payment
Route the payment result
The payment node sends hosted checkout and requires both a success and an error path in the flow.
Confirmation
Retain the appointment
A successful booking receives a reference and is kept with confirmed or cancelled status.
Example workflow
Service booking with a deposit
- 01Customer request — capture the requested service.
- 02Service selection — collect the details needed for the appointment.
- 03Availability — offer currently bookable configured slots.
- 04Payment — send a Stripe or Paystack hosted checkout link for the deposit or full amount.
- 05Confirmation — continue the payment-success path and retain the appointment record.
- 06Reminder — no booking reminder is sent automatically; it must not be assumed from this flow.
- 07Reschedule or cancel — design an explicit customer path; automated rescheduling is not provided.
Demonstration workflow using a first-party Fluenta template.
Product truth
Product truth
- Availability configuration
- Each workflow has a booking configuration: IANA timezone, weekly local-hour windows, slot minutes, lead minutes, booking horizon, and capacity.
- External calendar sync
- There is no external calendar sync. Fluenta provides a token-protected, read-only ICS feed for appointments; it does not import or reconcile an external calendar.
- Capacity
- Capacity is configured per slot. A slot is no longer offered when its configured capacity is reached.
- Payment providers
- Payment nodes support Paystack and Stripe, using the provider configuration for that workflow.
- Payment result routing
- Payment-node configuration or checkout-link errors follow the error branch. A provider-confirmed payment resumes the success branch; failed or abandoned provider states are recorded but do not resume a customer-facing error branch.
- Cancellation and refunds
- Appointments can have confirmed or cancelled status. There is no automated cancellation-to-refund workflow or provider refund handling in the booking flow.
- Reminders
- Bookings do not send reminders automatically.
Metrics
Numbers visible to the operator
- Booking requests
- Slots offered
- Unavailable outcomes
- Confirmed appointments
- Cancelled appointments
- Payment success path
- Payment error path
Questions
Before you build
Does Fluenta sync with Google Calendar or another external calendar?
No. It has a read-only ICS feed for Fluenta appointments, not external calendar synchronization.
Can we take a deposit?
Yes. Configure a Stripe or Paystack payment node for the amount and route both its success and error outcomes.
Does a cancellation automatically refund the customer?
No. Refund handling is not automated by the booking flow and should be handled with the payment provider outside it.
Start from the booking template
Build the confirmation path, test the unavailable and payment-error branches, then publish the customer journey you have reviewed.