Service Pages & Bookly Integration — 2026-04-05
Working session covering two parallel tracks: (1) resolving Bookly/Square/Google Calendar booking integration issues and (2) designing a new Glossier-inspired service page layout with variants. Attendees from Asymmetric: Melissa Cusumano, Chris Østergaard. From La Marie Beauty: Katie Schueller, Lisa Frommelt, Roxana Lopez.
See also: [1]
Key Decisions
- Classic microneedling selected as the prototype service page — simpler variant structure than Tox, good representative case.
- New service page layout will be Glossier-inspired: variant selector tabs at top, shared info in upper block, expandable accordion sections (key ingredients, before/after images, clinical info) below — with content changing per variant.
- Variants will be implemented as separate linked pages rather than true in-page tab switching, due to platform constraints around booking links.
- Service content spreadsheet will use a color-coding system to distinguish core service info (same across variants) from variant-specific fields. Empty-but-required fields will get a distinct "not started" color.
- Filters project budget may be redirected toward the service page variant work, given the overlap in underlying data structure.
- Prototype target: ready for review by next Tuesday.
Bookly / Square / Google Calendar Integration
What's Working
- Google Calendar ↔ Square sync is functional. Chris connected the Square profile to his Asymmetric email and confirmed appointments block calendar time correctly.
- Katie can proceed with connecting individual team G Suite accounts — but this must happen in the staging site, not production.
Open Issues
1. Appointment inventory not populating in Square customer profiles
When a booking is created via Bookly, the appointment does not appear in the customer's Square profile under the Appointments tab. Calendar time is blocked, but there is no persistent record tied to the customer. Chris is actively working on this.
2. Card-on-file not supported natively through Bookly
Bookly can store card details only when integrated with Authorize.Net or Stripe — not Square directly. The team discussed a deposit workaround but Katie declined, citing client communication overhead and the fact that existing Square customers already have cards on file. Chris will trial the Bookly Square Payments add-on (free trial available) to see if it enables card capture through the widget.
3. Team member ID mapping causing booking failures
Chris could not access the Staff → Team Members section in Square due to permission scope. Katie will email all team member IDs directly. Chris believes this missing mapping is a root cause of appointment creation failures in Bookly.
Next Steps — Integration
- [ ] Katie: Email Square team member IDs to Chris.
- [ ] Katie: Connect all team G Suite accounts via the staging site (follow instructions doc Chris sent previously).
- [ ] Chris: Trial Bookly Square Payments add-on; report back on card-on-file capability.
- [ ] Chris: Resolve appointment inventory display in Square customer profiles.
- [ ] Melissa: Restore staging site access for Roxana and Katie (Roxana regained access during this call; Katie's password reset was sent).
Service Page Redesign
Concept
Inspired by Glossier's product detail pages. The layout separates a shared upper block (service name, subtext, elevator sentence, CTA, variant selector) from a variant-specific lower block (expandable accordions for key ingredients, before/after images, downtime, treatment frequency, benefits, complementary treatments).
Variants are short (one or two words: "Face," "Neck," "Crow's Feet," etc.) to fit cleanly in the selector UI. The "Book Now" button on each variant page links to that specific variant's booking flow.
Content Spreadsheet
Roxana has built a detailed spreadsheet covering all services. Color-coding logic:
- Yellow — service has variants
- Gray / "Same as [core]" — field content is identical across all variants; no need to duplicate
- Distinct "not started" color — field is required but not yet populated
Fields currently tracked: service name, subtext, elevator sentence, CTA, key ingredients, downtime, treatment frequency, benefits, pairs well with (complementary treatments). Fields under consideration (pending Lisa's input): how to prep, post-treatment care, potential complications, timeline for results.
Roxana noted the spreadsheet has long-term value beyond the website — as a reference for front desk staff and as a structured data source for future AI/chatbot integrations.
Prototype Plan
- Service: Classic Microneedling (chosen for manageable variant count)
- Owner: Ishak (developer) will build the prototype page
- Input: Melissa will walk Ishak through the Canva mockup Roxana shared; Roxana will annotate the spreadsheet to clearly mark which fields are shared vs. variant-specific for microneedling
- Review: Prototype due next Tuesday
Navigation Menu
Current nav feels redundant — subcategories like "Biostimulators" appear at the same level as top-level categories like "Injectables," which confuses the hierarchy. Some services (e.g., Luxe Enhancement) have no page yet and are not listed anywhere in the nav.
Desired structure: four or five top-level categories (Lifestyle, Skincare, Injectables, Wellness, Shop) with hover-activated submenus. Roxana previously shared a site tree / sitemap in Canva — Melissa to re-locate this.
Nav refinement is lower priority than the service page prototype but should be addressed once the page layout is settled.
Product Pages
- Daily Dynamic Hydrator needs to be added to the product section.
- Products are managed through WooCommerce, which syncs to Square.
- Roxana can likely duplicate an existing product page and update fields herself; the tricky part is ensuring the WooCommerce ↔ Square link is set up correctly.
- A training session on adding/editing pages will be scheduled for the La Marie team once the new page template is finalized.
Action Items Summary
| Owner | Task | Due |
|---|---|---|
| Ishak | Build classic microneedling prototype page | Next Tuesday |
| Roxana | Annotate spreadsheet: core vs. variant fields for microneedling; continue populating other services | Ongoing |
| Melissa | Brief Ishak on Canva mockup and Glossier reference | This week |
| Chris | Trial Bookly Square Payments add-on | This week |
| Chris | Resolve appointment inventory in Square customer profiles | This week |
| Chris | Use team member IDs (from Katie) to fix booking mapping | This week |
| Katie | Email Square team member IDs to Chris | Immediate |
| Katie | Connect G Suite accounts via staging site | This week |
| Melissa | Locate sitemap/site tree Canva file | This week |
| Melissa / Roxana | Schedule CMS training session for La Marie team | TBD |
Transcript Excerpts
On the card-on-file problem:
Katie: "How does a platform like Bookly not have a capability of storing a card, though?"
Melissa: "It says they can store credit card information when integrated with a payment gateway like Authorize.Net or Stripe."
On the value of the service content spreadsheet:
Roxana: "Even when considering inputting into AI integrations, and we have a chatbot — if all of this info just exists in a centralized place, the work that's going into this is really important. So it makes me excited to think about — we're just organizing it on a web page, but there's a grander scheme."
On the variant page architecture:
Roxana: "They'll be like separate pages, basically, right? And they're just kind of like links to each other at the top."
Melissa: "Yeah. We just have to make sure that it looks really slick, that it looks good."