Frequently Asked Questions

The customer sends your configured keyword, such as BOOK. The conversation collects the service, date, available time and full name. A reliable sender phone can be captured automatically, with an option to change it.

Yes. The currently published Booking service supports a connected Personal WhatsApp device and your own Meta number. Meta API conversations and notifications remain subject to window, template and billing requirements.

Yes. Create services with displayed prices and durations. Availability is checked against the full appointment length rather than just the starting time.

A shared calendar prevents services from overlapping when they use the same resource. Independent service calendars allow different services to run at the same time. Choose the arrangement that reflects your real capacity.

The current module has one account-wide booking setup. Named-staff assignment, multi-staff capacity and allocation across multiple locations are outside its present scope. Discuss those requirements before selecting a package.

Yes. Configure immediate confirmation or merchant approval. Pending approval requests hold the selected slot until they are confirmed or cancelled, so staff should review pending requests promptly.

Yes. Configure appointment periods and date exceptions. Booking intake hours can be controlled separately, and new requests can be paused until a chosen time.

Optional reminders are available and start disabled until configured. Set the reminder arrangements before use. WhatsApp reminders consume platform credits, and Meta reminders outside the customer service window require an approved template.

Yes. Staff can correct customer details, reschedule, cancel and complete appointments through supported management actions. Changes retain an audit history. Check the resulting customer and merchant notification settings.

Yes. Completed or cancelled appointments can be archived and restored. Archived appointments remain in reports; archiving hides records rather than deleting them or reclaiming storage.

No. The current Booking module does not collect appointment payments or deposits, verify payments or process refunds. Continue your normal payment arrangements and discuss any payment integration as a separate requirement.

The published indicative add-on is RM348 per year, billed annually, for one account-wide setup. A compatible base subscription, message usage, applicable Meta fees and separately quoted services are additional. Your quotation confirms activation and terms. See Booking pricing.

There is no fixed credit fee per appointment. An illustrative flow with the customer conversation, merchant WhatsApp alert, one reminder and completion updates uses 17 credits. Approval, browsing, corrections and rescheduling can change the total. Budget actual inbound and outbound messages.

Yes. Review 7-day, calendar-month and calendar-year activity and statuses. Use available CSV export and browser Print or Save as PDF for reports. Archived appointments remain part of reporting history.

See the Booking overview, customer journey, pricing and Booking FAQs, or contact us for activation.

No. Web and chat bookings share the existing scheduling engine and appointment records. They use the same availability, duration and capacity rules.

Yes. The web option is an additional route. Customers can continue the guided WhatsApp conversation if they prefer.

Yes. The invitation retains its original channel and recipient so configured updates and reminders follow that route.

Availability is rechecked under the same merchant lock used by chat/admin booking. Only one can reserve an overlapping slot where the configured capacity forbids a clash.

Yes. Simulated checkout shows a TEST reference but creates no live appointment, consumes no capacity, sends no notifications and deducts no credits.

No. This release displays the service price but does not collect booking payments or deposits. Continue using your usual payment arrangements.

Web actions do not use WhatsApp inbound processing credits. Real WhatsApp replies, notifications and reminders still follow platform credit rules and applicable Meta charges.

No. Opening or submitting the web page is not a new inbound WhatsApp message. The existing delivery rules still determine whether an approved template is required.

The current Booking setup is account-wide, using shared or independent service calendars. Named staff allocation, multi-location routing and multi-capacity services need separate scope confirmation.

No. Customers use a private invitation from the business conversation. Merchant previews use separate TEST invitations.