WhatsApp Booking FAQs

Customers book through WhatsApp. They need access to WhatsApp and your business number; your team manages appointments through the WebWMS2U dashboard.

Yes, in Independent services mode each service has its own capacity of one overlapping appointment. Select One shared calendar if one person or resource handles all services. This version does not assign appointments to individual staff.

You choose immediate confirmation or merchant approval. Pending approval requests reserve the appointment until confirmed or cancelled.

The system checks the entire appointment duration and rechecks availability inside a transaction before saving. Displaying a time does not reserve it; confirmation does.

Yes. Booking intake is separate from appointment availability and can be available 24/7. Customers can reserve an available future appointment outside your normal business hours.

Yes. You can pause intake until a chosen time or the next configured intake period, and add date exceptions for appointment availability or intake. Saved appointments are preserved.

Reminders are optional and require activation and the notification worker. The default reminder setting is 24 hours when enabled. A booking made inside that window is reminded on the next worker pass. Meta reminders outside the service window need the approved customer template.

Personal WhatsApp does not require Meta-approved templates. For Meta, merchant alerts always use an approved merchant template. Customer updates and reminders outside the service window use the approved customer template. Creation links prefill the drafts; you review, save, submit and await Meta approval.

One handled inbound WhatsApp message uses one platform credit. One outgoing WhatsApp message uses one credit when reserved for sending. There is no fixed per-booking credit charge. Email, account preview and dashboard actions are free; resulting WhatsApp notifications are charged separately.

A definite send failure refunds its reserved credit once. An uncertain submission retains the credit and is not automatically resent or refunded because the message may already have been sent.

Customers can check or cancel a new chat-created booking from the original conversation using its reference. Rescheduling is managed by the merchant in the dashboard. Merchant contact corrections do not change the original WhatsApp routing destination.

The current module does not collect deposits or online payments. Use your normal payment method and verification process. If your services require deposits, cancellation fees or payment-gateway integration, discuss that scope with us before launch.

Yes. Completed or cancelled appointments can be archived and restored. Archived records remain in statistics. Reports cover 7 days, calendar month or year by appointment date in the account timezone, with CSV and browser Print / Save as PDF.

Export upcoming active appointments as ICS. Validated ICS import accepts individual timed events, checks service duration and availability, and skips previously imported events. Recurring and all-day events must be converted first. This is file import/export rather than continuous two-way calendar synchronisation.

No. Archiving hides old records and retains their history. Your quotation should specify retained-data capacity and retention arrangements. Additional storage or a reviewed deletion policy may be needed as history grows.

Indicative Booking add-on pricing covers one account-wide booking setup. A compatible base platform subscription, platform credits and applicable Meta fees are separate. The quotation confirms pricing, activation, storage, taxes and any assisted setup.

Yes, with separate entry keywords such as BOOK and ORDER. An active conversation keeps its own replies; each module retains separate records and notifications.

The current version is account-wide and supports shared or independent service calendars. Named staff allocation, multiple locations and more than one simultaneous appointment per service require further scope confirmation.

A manually created or imported booking has no verified original WhatsApp conversation destination, so the current module does not automatically send WhatsApp updates or reminders for it. Per-service merchant email alerts are available. New chat-created bookings retain the routing information needed for WhatsApp notifications.