Appointomatic – Appointment Booking & Scheduling

Appointomatic provides the booking engine, responsive booking wizard, catalogue management, staff and branches, availability, customer accounts, notifications, visual Form Builder, payments, WooCommerce integration, calendar synchronization, automation, CRM, memberships/packages, WhatsApp/SMS, reporting, Elementor widgets, advanced commerce, staff scheduling, customer portal tools, coupons, service areas/travel, SMTP delivery, public API/webhooks and audit-log administration from one plugin.

Former add-on feature keys are preserved internally for compatibility, but separate Appointomatic add-on plugins are no longer required. Manage built-in capabilities from Appointomatic → Modules.

Privacy and tracking

Appointomatic does not send plugin telemetry, usage analytics, or site-administration data to a Appointomatic-operated service.

org build. Optional abandoned-booking recovery is disabled unless a site administrator enables it. When enabled, Appointomatic stores the minimum local event data needed for recovery in the site’s own WordPress database.

Site administrators are responsible for obtaining any consent required by their jurisdiction and for describing their own use of these features in their privacy notice.

Marketing synchronization is opt-in aware by default. When the “Sync only customers who enabled marketing email” setting is enabled, marketing providers receive contact data only for customers whose stored notification preference permits marketing email.

External services

Appointomatic can connect to external services only when the corresponding feature is enabled/configured. The plugin does not proxy these services through a Appointomatic-operated server.

Payment providers

• Stripe: Used for hosted checkout, payment-status reconciliation, webhooks and refunds. Booking/payment references, customer email, amount/currency and checkout metadata are sent when Stripe is enabled and a checkout/refund is requested. Terms: https://stripe.com/legal/ssa Privacy: https://stripe.com/privacy

• PayPal: Used for hosted checkout, payment capture, webhook verification and refunds. Booking/payment references, amount/currency and checkout metadata are sent when PayPal is enabled and a checkout/refund is requested. Terms: https://www.paypal.com/us/legalhub/useragreement-full Privacy: https://www.paypal.com/us/legalhub/privacy-full

• Square: Used for hosted payment links, webhook verification, payment reconciliation and refunds. Booking/payment references, amount/currency and payment metadata are sent when Square is enabled. Terms: https://squareup.com/us/en/legal/general/ua Privacy: https://squareup.com/us/en/legal/general/privacy

• Razorpay: Used for payment links, signed webhooks and refunds. Booking/payment references, amount/currency and payment metadata are sent when Razorpay is enabled. Terms: https://razorpay.com/terms/ Privacy: https://razorpay.com/privacy-policy/

• Mollie: Used for hosted payments, webhook reconciliation and refunds. Booking/payment references, amount/currency and payment metadata are sent when Mollie is enabled. Terms: https://www.mollie.com/legal/user-agreement Privacy: https://www.mollie.com/privacy

Messaging, calendar, meetings and identity

• Twilio: Used to send SMS and WhatsApp messages when enabled. Recipient number, sender configuration and message content are sent for each delivery. Terms: https://www.twilio.com/legal/tos Privacy: https://www.twilio.com/en-us/legal/privacy

• Google Calendar / Google OAuth: Used for optional calendar synchronization. OAuth codes/tokens and calendar event details are exchanged only when an administrator connects calendar synchronization. Terms: https://policies.google.com/terms Privacy: https://policies.google.com/privacy

• Microsoft Graph / Microsoft identity platform: Used for optional Microsoft calendar synchronization. OAuth codes/tokens and calendar event data are exchanged when the integration is connected and calendar sync runs. Terms: https://www.microsoft.com/servicesagreement Privacy: https://privacy.microsoft.com/privacystatement

• Zoom: Used for optional meeting creation. Meeting title/time, attendee/booking context needed by the configured integration and OAuth/access credentials are sent when a meeting is created. Terms: https://www.zoom.com/en/trust/terms/ Privacy: https://www.zoom.com/en/trust/privacy/privacy-statement/

Marketing and CRM

• Mailchimp: Used for optional marketing contact synchronization. Customer email/name/phone and configured audience membership are sent only when marketing sync is enabled and allowed by the site’s marketing preference rules. Terms: https://mailchimp.com/legal/terms/ Privacy: https://www.intuit.com/privacy/statement/

• Brevo: Used for optional marketing contact synchronization. Customer email/name/phone and configured list membership are sent when enabled. Terms: https://www.brevo.com/legal/termsofuse/ Privacy: https://www.brevo.com/legal/privacypolicy/

• ActiveCampaign: Used for optional marketing contact/list synchronization to the administrator-configured ActiveCampaign account URL. Customer email/name/phone and list identifiers are sent when enabled. Terms: https://www.activecampaign.com/legal/terms-of-service Privacy: https://www.activecampaign.com/legal/privacy-policy

• HubSpot: Used for optional CRM contact synchronization. Mapped booking/customer fields are sent when enabled. Terms: https://legal.hubspot.com/terms-of-service Privacy: https://legal.hubspot.com/privacy-policy

• Salesforce: Used for optional CRM contact synchronization to the administrator-configured Salesforce instance. Mapped booking/customer fields are sent when enabled. Terms: https://www.salesforce.com/company/legal/customer-agreements/ Privacy: https://www.salesforce.com/company/legal/privacy/

• Zoho CRM: Used for optional CRM contact synchronization. Mapped booking/customer fields are sent to the administrator-configured Zoho API domain when enabled. Terms: https://www.zoho.com/terms.html Privacy: https://www.zoho.com/privacy.html

• Pipedrive: Used for optional CRM contact synchronization. Mapped booking/customer fields are sent to the administrator-configured Pipedrive account when enabled. Terms: https://www.pipedrive.com/en/terms-of-service Privacy: https://www.pipedrive.com/en/privacy

Maps, webhooks and administrator-selected services

• OpenStreetMap: The booking form can display an OpenStreetMap embed. The visitor’s browser requests map imagery/embedding from OpenStreetMap when that map is displayed, which can expose the visitor IP address and requested map coordinates to OpenStreetMap. Tile usage policy: https://operations.osmfoundation.org/policies/tiles/ Privacy: https://osmfoundation.org/wiki/Privacy_Policy

• Google Maps: Some administrator-facing map/location previews can use a Google Maps embed. The browser sends the map query/location and normal HTTP request data when an embedded Google map is loaded. Terms: https://maps.google.com/help/terms_maps/ Privacy: https://policies.google.com/privacy

• Administrator-configured SMTP: If custom SMTP is enabled, email recipients, subject/body and transport credentials are sent to the SMTP server chosen by the administrator. That provider’s own terms/privacy policy apply.

• Administrator-configured outgoing webhooks / CRM webhook: If enabled, Appointomatic sends the administrator-selected booking/payment event payload and configured headers to the endpoint entered by the administrator. The endpoint operator’s own terms/privacy policy apply.

Source code and build

The PHP, CSS and JavaScript shipped in Appointomatic are human-readable source files. There is no required npm, webpack or other compilation step for this release, and third-party JavaScript/CSS is not loaded from a CDN.