Weekly project call with the La Marie Beauty team to review progress on the Bookly + Square integration. Roxana was unable to attend. The call surfaced a key technical blocker — Zapier cannot establish a return connection from Square back to Bookly — and landed on Google Calendar as the centralized sync hub to resolve it. The team also aligned on a revised UX flow for service variation selection.
Attendees:
- Katie Schueller (La Marie Beauty) — client lead
- Lisa Frommelt (La Marie Beauty) — not present; note referenced
- Roxana Lopez (La Marie Beauty) — absent
- Chris Ostergaard (Asymmetric) — lead developer
- Melissa Cusumano (Asymmetric) — project manager
- Mark Hope (Asymmetric)
Zapier cannot establish a two-way connection directly between Bookly and Square. The approved solution is to route all calendar events through a shared Google Calendar: both Bookly and Square sync to it independently, achieving effective two-way awareness without a direct Bookly↔Square pipe. Because La Marie Beauty already uses G Suite (managed by Katie), no new Gmail account is needed — existing Google Workspace accounts are compatible.
The team confirmed the direction to consolidate service variations onto single product pages rather than displaying each variation as its own tile. The revised flow:
Chris has all variations already entered in Bookly with pricing. The remaining work is connecting the product-page selection to the correct Bookly event (to be done with Eshaq).
The current "Book Now" CTA on service tiles goes directly to booking. Under the new flow, clicking it first lands users on the variation-selection page — creating a confusing double "Book Now" experience. The button text needs to change (suggestion: "View Now" or similar). Final wording to be confirmed; Lisa's preference should be considered.
Chris has implemented a lookup step: before creating a new customer record in Square, Zapier checks for an existing customer by email and phone number. Duplicates will not be created.
| Owner | Action | Target |
|---|---|---|
| Katie | Schedule a meeting with Chris (and optionally Melissa) + Roxana to configure Google Calendar access and sync | Before next Tuesday; email Chris with times, prioritizing Thursday morning |
| Chris | Continue resolving timestamp mismatch between Bookly and Square in Zapier | Ongoing |
| Chris | Work with Eshaq to connect product-page variation selections to corresponding Bookly events | Before next Tuesday |
| Chris / Melissa | Revisit "Book Now" button text and update CTA copy across service pages | TBD |
| Chris | Provide full integration update at next Tuesday's standing meeting | Next Tuesday |
| Melissa | Hold on responding to Lisa's email re: variations until Katie reviews internally | Immediate |
Katie noted that the complexity of this integration feels greater than what was originally communicated — earlier conversations (primarily with Lisa) made it seem more straightforward. Chris clarified that Zapier was always the intended bridge for Bookly's external communication, and that the unexpected complexity is specifically the lack of a return path from Square. He expressed confidence that once configured, the end-user experience will be seamless, and noted that Bookly's booking UX is superior to Square's native scheduling. Moving away from Square entirely was not considered viable given La Marie Beauty's existing infrastructure investment there.