Internal team sync to work through the variant implementation approach for [1] service pages, resolve the Bookly integration constraint, and get status updates on other active projects. Attendees: Ishaq (dev), Chris (dev), Melissa (PM).
| Owner | Task | Notes |
|---|---|---|
| Ishaq | Build Vampire Facial service page with variant selector as a proof-of-concept | Melissa to provide the client's variant spec document in ClickUp |
| Melissa | Update ClickUp task with variant implementation details and attach client's design reference doc | Do not route through designers — Ishaq already has the pages built |
| Melissa | Confirm homepage "Book Now" → Square page redirect with client | Will follow up same day |
| Chris | Continue troubleshooting Zapier integration | Awaiting additional info from client; will escalate to support if needed |
| Melissa | Extend La Marie weekly calendar invites through November 11th | — |
The client (Roxanna's team) envisions parent umbrella service pages where a user can select a variant (e.g., "Lip Fill," "First Time Tox") and have the page content update dynamically to reflect that variant's details, images, and pricing — with the "Book Now" CTA routing to the correct Bookly flow for that specific variant.
The constraint: Bookly has no native concept of service variations.
The workaround:
1. Each variant is created as a separate, standalone service in Bookly.
2. On the WordPress front end, a single page presents all variants via a selector/tab UI.
3. When a variant is selected, JavaScript/page logic swaps the visible content and updates the "Book Now" button's target URL to point to that variant's Bookly booking flow.
4. The user experience appears unified; the backend remains a set of discrete Bookly services.
Ishaq confirmed single-page implementation is feasible. The Vampire Facial test case will validate the full flow before the pattern is rolled out to more complex services (e.g., Tox Juvo with many variants).
Melissa: "So you still have 50 Bookly flows, but ideally this page would be kind of a merged products."
Ishaq: "For Bookly, we need to add separate services… Yeah."
Melissa: "So if you're on this Neurotox, but you have the lip fill picked, that book-your-appointment would then go to that single product Bookly flow."Melissa (on homepage button): "On the homepage, they want this 'Book Now,' instead of it going to this service page, until we get this Bookly running, they want it to go to a Square page with all the products listed."