Symphony Core Calendar Setup SOP
Overview
- What: Configure a Symphony Core calendar end-to-end so a public booking link routes to the correct user, fires confirmations and reminders, and is wired into the client's WordPress site as a working CTA.
- When: Triggered by (a) the post-go-live integration call after a WordPress migration, (b) any client report that bookings are not reaching the intended person or a
BOOK A 15-MINUTE CALL-style link 404s, (c) the calendar verification block of client-onboarding-verification.csv (CALENDARS rows). - Who: Support Process Owner runs the SOP. Client representative who owns the consult intake must be available on the call to confirm availability and notification preferences live.
- Time Required: ~30 minutes if the client is on the call; ~60 minutes if availability or routing details have to be chased after the call.
Prerequisites
- Sub-account access to Settings → Calendars in
app.symphonycore.comfor the target client. - Calendar owner identified by role. The person whose calendar receives the booking — usually a partner, intake coordinator, or first-touch attorney. Must already have a Symphony Core user account in the client sub-account.
- Calendar owner's Google or Outlook calendar connected, with two-way sync confirmed, per item CRM-04 of the Client Onboarding Checklist.
- Brand colors confirmed in the client profile's design system. The Primary color hex is required for GHL Calendar Primary Color SOP.
- Destination page(s) on the client website known — every page hosting the booking CTA must be listed before Step 6.
- WordPress admin access (Elementor or theme editor) for the destination pages.
Procedure
Step 1 — Create the calendar
- Open Settings → Calendars in the client sub-account at
app.symphonycore.com. - Click Create Calendar and choose the type that matches the client's intent:
- Single User when one person owns the consult intake (most legal/professional services clients).
- Round Robin when several teammates share intake and bookings should rotate.
- Collective / Class only when the client requested it explicitly.
- Name the calendar after the public-facing label the website uses (e.g.,
15-Minute Consultationif the button says BOOK A 15-MINUTE CALL). - Assign the calendar owner identified in Prerequisites.
Step 2 — Configure availability
Confirm each value with the client before saving:
- Timezone — the client's office timezone, not the operator's.
- Working hours and days — match the firm's business hours.
- Slot duration — match the public CTA (e.g., 15 minutes for a
BOOK A 15-MINUTE CALLbutton). - Buffer time — 15 minutes before and after by default; widen if the calendar owner requested setup or wrap-up time.
- Minimum scheduling notice — 24 hours by default; tighten only if the client wants same-day bookings.
- Maximum lookahead — 30 days by default.
Step 3 — Configure routing and notifications
- Confirm the assigned user is the calendar owner from Step 1, not the operator's account. This is the single most common cause of "bookings not reaching the right person."
- Confirmation email to attendee — on, with the client's business hours and meeting-prep instructions in the body.
- Confirmation email to assigned user — on, so the owner sees every booking in their inbox even if the calendar event is filtered.
- SMS reminders — 24 hours and 1 hour before by default; confirm with the client and disable SMS if A2P registration is not yet complete.
- Cancellation and reschedule policy — copy the same hours/cutoff the client uses by phone.
- Meeting location — pick the model the client uses: phone callback to the attendee's number, auto-created Zoom link, in-office address. One model per calendar; do not mix.
Step 4 — Apply brand colors
Run GHL Calendar Primary Color SOP against the calendar created in Step 1. Confirm the Neo widget style is selected and the Primary color hex matches the client profile's design system.
Step 5 — Generate the public booking link and embed snippet
- Copy the calendar's permanent public URL from the calendar editor — not a draft preview URL.
- If the destination is an inline embed: copy the embed snippet from the calendar editor. See GHL Asset Handoff to WordPress Dev Team SOP §1.2 for the two hosting models (WP-embedded vs GHL-hosted) and pick the one the client agreed to.
- If the destination is a GHL-hosted funnel (e.g.,
go.[clientdomain]/schedule): confirm the B-007 calendar funnel exists and resolves before linking to it.
Step 6 — Place the link on every booking entry point on the website
This step prevents the "one link works, one 404s" symptom. The handoff record may list one CTA, but real client sites accrue several over time.
- In WordPress, search the entire site for any existing booking link —
/schedule,/book,calendar,consult, the prior platform's booking URL — using the theme search, an Elementor finder (⌘E/Ctrl+Einside the editor), or a database search for the legacy URL. - Before updating any URL, check whether each booking CTA is an Elementor Global Widget. Hover each instance in the editor — a globe icon means it is global (one edit propagates everywhere). Non-global duplicates of the same button are how fragmentation re-introduces itself: you update the homepage button, the link looks fixed, but a bottom-of-page or footer copy still points at the old URL. Promote any duplicate CTA to a single Global Widget before updating the URL. This was the root-cause symptom on Moots Law 2026-06-12 — one button was hidden via the global header instance, but a separate non-global duplicate at the bottom of the homepage stayed visible to prospects until it was found and hidden by hand. See also the elementor-cta-fragmentation working rule.
- Update the Global Widget once to the single permanent URL from Step 5. Confirm every page that uses the widget now resolves to the same destination.
- Hero CTAs, header CTAs, page-section CTAs, footer CTAs, and any in-content links must all resolve to the same destination.
- Save and publish each page. Clear any caching layer (CDN, plugin cache).
Step 7 — Test the full booking flow
Submit a test booking as if you are a prospect, using a test contact's email and phone:
- Visit the destination page in an incognito window.
- Click each CTA on the page in turn. Each one must resolve to a booking page that renders available slots in the client's brand color.
- Book a slot.
- Verify, in order:
- A contact is created in
app.symphonycore.comwith the test details. - The attendee confirmation email arrives.
- The assigned-user confirmation email arrives.
- The event lands on the assigned user's connected Google or Outlook calendar.
- The SMS reminder is scheduled for the configured time.
- A contact is created in
- Cancel the test booking and delete the test contact and event when finished.
Verification
The SOP is complete when the operator can attach all three items below to the ticket or handoff record as evidence (see the validation-evidence-rule in the SC Contractor Task Quality Pre-Work Standard):
- Calendar configuration screenshot showing the assigned user, slot duration, working hours, and notification toggles.
- Public booking page screenshot in an incognito browser, rendering in the client's brand color, slots visible.
- Test confirmation email screenshot from both the attendee inbox and the assigned-user inbox.
Cross-check: items CRM-04 and CRM-05 of the Client Onboarding Checklist are satisfiable by the steps above; update each in the onboarding tracker as the corresponding step closes.
Common Failure Modes
| Symptom | Likely cause | Fix |
|---|---|---|
| Booked slots not received | Assigned user is wrong (commonly the operator's account, not the calendar owner) | Step 3 — reassign to calendar owner; resend a test booking |
| Booked slots received by user but no calendar event lands in their Google/Outlook | Two-way sync not enabled, or the owner connected the wrong external calendar | Step 3 + Prerequisites — re-verify sync in the user's profile |
BOOK A 15-MINUTE CALL-style button on one page works, another 404s | A legacy URL was missed in Step 6 — usually a button placed in an early build or a duplicated page | Step 6 — search the whole site, update every entry point to the same permanent URL |
| Public booking page renders in default platform blue | Step 4 skipped, or Neo widget style not selected | Run the color SOP; confirm Neo is selected |
| Confirmation emails not arriving | Notification settings off, or domain sender not verified | Step 3 — enable confirmations; if domain sender is the issue, raise an A2P / sender authentication ticket |
| SMS reminder configured but no SMS sent | A2P registration not complete or not approved for this sub-account | Disable SMS reminders until A2P is approved; do not block calendar go-live on SMS |
Related Documents
- GHL Calendar Primary Color SOP — Step 4 brand-color procedure.
- GHL Asset Handoff to WordPress Dev Team SOP — §1.2 covers the two calendar hosting models (WP-embedded vs GHL-hosted) referenced in Step 5.
- Client Onboarding Checklist — items CRM-04 and CRM-05, which this SOP satisfies.
- WordPress Post-Go-Live Cleanup SOP — upstream SOP whose calendar step delegates to this one.
- Post-Go-Live Client Status Email Template — the email that flags "calendar integration call needed" as an open item.
- SC Contractor Task Quality Pre-Work Standard — validation-evidence-rule referenced in Verification.
Revision History
| Date | Version | Change | Author |
|---|---|---|---|
| 2026-10-12 | 1.2 | Calendar cross-checks point to items CRM-04 and CRM-05 of the Client Onboarding Checklist, which replaced the onboarding verification CSV. | Symphony Core Systems Team |
| 2026-06-13 | 1.1 | Step 6 hardened with a Global Widget pre-check. Updating a non-global duplicate of a recurring CTA is how fragmentation re-introduces itself — a non-global copy of the BOOK A 15-MINUTE CALL button at the bottom of the Moots Law homepage stayed visible after the global header instance was hidden. Step now requires promoting duplicate CTAs to a single Global Widget before any URL update. Cross-links to the new elementor-cta-fragmentation working rule. | Symphony Core Systems Team |
| 2026-06-12 | 1.0 | Initial release. Created in response to a Moots Law client report that bookings were not reaching the intended user and that one booking link 404'd — symptoms traceable to no end-to-end calendar setup SOP existing (only the color-branding SOP did). Codifies create → availability → routing → color → link → site placement → test as the canonical setup path. | Symphony Core Systems Team |