Maintenance Release · June 2026

Patch Notes

One booking template, one automated set of widgets, one home for every credential, and one current calendar — the month the roster of slightly-different installs became a single standardized platform.

Release Window June 2026
Theme Consolidation
Upgrades 11 enhancements
Coverage Full agency roster

May found the sprawl; June collapsed it. Every agency moved onto a single standardized booking template and a single current calendar.

Calendar Migration — Survey → Thank-You + Embedded Calendar

What
Standardized the on-site booking path across every agency landing page: a short survey routes to a thank-you page with the calendar embed, and every lead is captured to the CRM pipeline even when the visitor doesn't book on the spot.
Why
A bare calendar embed only captures the people who book immediately and loses everyone else. Routing through a survey means the lead is in the pipeline the moment they engage — booked or not — so nothing leaks.
Impact
One booking template across the roster. Leads are captured on engagement, not just on booking.

New Calendar ID — Workflow Rewire + Registry

What
Pointed every booking workflow at the new calendar, stored the calendar ID centrally, and ran an end-to-end functioning check on each agency.
Why
New embeds mean new calendar IDs; the workflows have to write into the right one. Storing the ID centrally means the platform can verify the workflow and the embed agree — instead of finding out they don't when a booking silently fails.
Impact
Booking workflows target the correct calendars, auditable from one place. Closes out the Calendar v2 migration started in April.

Widgets now embed themselves, and the chat backend connection got the fix it needed to stop dropping messages.

Voice & Chat Agents

Automated Widget Embedding

What
Voice and chat widgets now embed onto an agency's website automatically as part of provisioning, replacing the hand-placed, per-site embed.
Why
Hand-placing widgets on every site is slow and error-prone — a missed embed means an agency is paying for an agent that never appears. Automating it makes "all three widgets live" the default state, not a checklist item that can be forgotten.
Impact
Voice and chat widgets go live consistently across sites without manual placement.

Workflow Engine

Chat Webhook — Fix

What
Fixed the chat trigger webhook so the embedded chat widget connects reliably to its workflow backend.
Why
A chat widget that renders but can't reach its backend is worse than no widget — it looks live and silently drops every message. The webhook fix closes that gap.
Impact
Embedded chat widgets resolve and respond reliably.

The internal website builder got a major overhaul, and two long-tail rendering and seeding bugs got closed out.

Website Builder v2 — Overhaul

What
Overhauled the internal website builder: a conversational intake replaced the scripted form, builds are now type-aware (landing, business, portfolio, SaaS), previews render multiple pages with real routing, and a version history lets any build be restored in one click. A self-healing preview auto-fixes common build errors instead of failing.
Why
The old builder produced one-shape sites from a rigid form and had no undo. Type-aware builds, real multi-page previews, and restore-able version history turn site creation from a fragile one-way process into something an operator can iterate on safely.
Impact
Faster, more resilient site builds with history and restore built in.

Favicon Rendering — Fix

What
Fixed favicons that weren't rendering across a batch of agency landing pages.
Why
A missing favicon is a small thing that reads as "unpolished" in every browser tab and bookmark. It's exactly the kind of regression that hides in plain sight for months.
Impact
Correct branded favicons rendering across the affected pages.

Site Template Seed Gap — Fix

What
Fixed a gap in the website template's seed data that could cause a fresh site build to fail.
Why
A seeding gap turns a routine new-site build into a failed install. Fixing the template means every new build starts from complete, known-good data.
Impact
Fresh site builds start from a complete template. No more seed-gap install failures.

We moved every production integration off personal accounts and gave every agency ownership of its own.

Integrations — Company-Owned Accounts

What
Migrated all production integrations — database, AI provider, voice agent, workflow engine, hosting, and monitoring — off personal accounts and onto company-owned accounts, re-stored under encryption.
Why
Production running through someone's personal account is a single point of failure and an audit red flag: it can't be rotated cleanly, and it disappears if that person does. Company-owned accounts make ownership explicit and recoverable.
Impact
Production credentials live in company-owned accounts, encrypted at rest, with clear ownership.

Per-Agency Account Ownership

What
Each agency now provisions and owns its own service accounts — AI provider, voice agent, workflow engine, vector knowledge base, and messaging — rather than sharing centrally-held credentials.
Why
When an agency owns its own accounts, its usage, billing, and limits are its own — one agency's spike or suspension can't affect another's, and the agency keeps its data if it ever leaves.
Impact
Clean per-agency isolation of credentials, billing, and usage.

Reliability and security hardening beneath the surface — keeping connections live and the consolidated credential store locked down.

Connection Token Auto-Refresh

What
Added automatic renewal for CRM connection tokens after a recurring expiry pattern was periodically dropping agencies' integrations offline.
Why
When a connection token silently expires, the affected agencies go blind — leads stop syncing and no one notices until a report comes back empty. Auto-renewal removes the manual recovery step and the window where agencies are dark.
Impact
CRM connections stay live through token renewals instead of lapsing.

Access Controls + Credential Encryption

What
Verified row-level access across every role, confirmed dashboard authentication, and validated at-rest encryption for stored credentials, alongside a secret-hygiene sweep of the codebase.
Why
Consolidating credentials centrally only helps if the store itself is locked down. Row-level access, authenticated dashboards, and encryption-at-rest are what make centralization safe rather than a bigger target.
Impact
Verified access controls and encrypted credential storage underneath the consolidated accounts.
Cross-Month Theme

Audit, then consolidation

May was the audit — walking every account and cataloguing the sprawl. June was consolidation — collapsing that sprawl into one booking template, one automated set of widgets, one home for every credential, and one current calendar. The month turned a roster of slightly-different installs into a single, standardized platform.