Public booking form overview
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
Publish a secure, responsive appointment form that offers only eligible services, providers, dates and times and creates external Pixie CRM appointment records.
What you’ll accomplish
Publish a secure, responsive appointment form that offers only eligible services, providers, dates and times and creates external Pixie CRM appointment records. It uses Pixie CRM's permission-aware appointment, availability, status and integration flow rather than an unconnected diary entry.
How it works
The public controller loads active services allowed by the form configuration and eligible providers for the selected service.
Date and time choices are generated from schedule, blocked-date, duration, buffer and busy-time checks.
Submission validates contact details, selected records, availability, optional terms and reCAPTCHA before storing an external appointment.
Follow these steps
- Configure services, providers and availability.
- Go to Booking Form and review the public URL.
- Configure heading, description, service scope, guest access, terms and verification.
- Complete a test booking in a private browser.
- Approve and inspect the created external appointment.
Settings to check
Check it worked
After this workflow completes, Pixie CRM keeps the appointment and its supported relationships connected. Reopen the appointment and verify the saved status, date, timezone, customer or lead, service, provider, attendees, reminder state, calendar or meeting reference, invoice reference and history that apply to this feature. External email, SMS, Google, Microsoft or payment outcomes must be checked separately from the Pixie CRM database save.
- Open the saved appointment and confirm the final status and source.
- Check the participant, provider, timing and timezone from the full detail page.
- Review the relevant table filter, calendar, history, report or linked invoice instead of relying only on a success message.
Common mistakes to avoid
- Do not publish before completing an end-to-end test.
- A public page must not expose internal notes or unauthorised staff data.
- Availability is rechecked at submission to prevent stale-slot booking.
- Use the least destructive correction and retain the appointment history when the booking existed operationally.
- Never bypass a permission, availability, approval, client-access or verification control by changing an unrelated route or setting.