Maintenance Release · April 2026

Patch Notes

Reliability, deliverability, observability, database migration, dashboard infrastructure, and the Calendar v2 closeout — turning last month's correctness work into provable, monitorable infrastructure.

Release Window April 2026
Theme Infrastructure
Upgrades 16 enhancements
Coverage Full agency roster

April closed out the booking-flow modernization started in March: new calendar embeds replaced the old ones across every agency website.

Calendar v2 — New CRM Calendar Embeds

What
Embedded the new (post–video-meeting-removal) CRM calendar widget directly on each agency website, replacing the old embed.
Why
The March upgrades invalidated the old embed's expected schema. The new embed is the post-cleanup version that matches what the CRM actually serves now.
Impact
On-site booking now uses the current calendar. No stale meeting-link references in the embed.

Voice and chat got tighter together this month, while the workflow engine moved to a new database backend.

Voice Agent

Voice Agent API — Replacement

What
Replaced the voice agent API key/integration in each agency's flows with the new key issued through the Platform API key registry.
Why
The old keys predated the centralized registry. Migrating onto the registry means the dashboard can actually report on voice agent health per agency.
Impact
Voice calls now flow through registry-managed credentials. Visible in the dashboard.

Chat Agent

Prompt Update v2 — AI Team Consciousness

What
Rolled out the second iteration of the unified "AI team consciousness" prompt across both the voice and chat agents.
Why
v1 (March) brought voice and chat into alignment. v2 layers in a shared identity / context-awareness layer so the agents reference each other's prior turns correctly when a conversation crosses channels (voice → chat handoff).
Impact
Cross-channel handoffs feel continuous to the end client instead of a hard reset.

Workflow Engine

Workflow Database Layer — Migration

What
Migrated the workflow data layer onto our managed database backend, replacing the prior persistence layer.
Why
The new backend gives us row-level security, real-time subscriptions, and a relational query surface that's easier to work with than the prior storage. Critical for the application dashboard work.
Impact
Workflow state now lives on the new database layer. Foundation for the dashboard initiative.

Calendar v2 — New Calendar ID in Workflows + Stored in Platform APIs

What
Updated each booking workflow to point at the new CRM calendar ID, and stored that calendar ID in the centralized Platform API registry.
Why
New calendar embeds = new calendar IDs. The workflows need the new ID to write into. Storing the ID in the registry means the dashboard can validate that the workflow points at the right calendar.
Impact
Booking workflows correctly target the new calendars. Calendar IDs are auditable from the dashboard.

Re-audit pass after March, catching any account that newly suspended or fell behind on payment.

Account Status — Re-Audit

What
Re-audited AI provider account status per agency post–March audit; categorized as Paid/Not Paid, Banned/Not Banned, or N/A.
Why
Status evolves between months. The April audit catches accounts that newly suspended or newly went unpaid since March, before they break a flow.
Impact
Up-to-date AI provider account state per agency in the maintenance tracker.

Frontend polish, SEO baselines, and analytics instrumentation across the agency roster.

Favicon — Coverage Check

What
Verified each agency website has a correct, branded favicon at every required size (16, 32, 180, 192, 512) and that the manifest references resolve.
Why
A missing favicon is a small thing that signals "unpolished" to the agency's clients. It's also the kind of regression that sneaks in during a deploy and goes unnoticed for months.
Impact
Favicon coverage verified across the agency roster.

Search Console — Verification

What
Confirmed each agency website is verified in Search Console and that sitemap submission is current.
Why
Without Search Console verification you can't see indexing problems, you can't see crawl errors, and you can't request re-indexing after a content update. Every site needs this baseline.
Impact
Search Console coverage in place across the agency roster.

Web Analytics — Verification

What
Confirmed analytics is installed correctly and reporting on each agency website, including the booking conversion event.
Why
Without analytics, conversion claims are vibes. With analytics, the booking widget can be A/B tested and the impact of any maintenance upgrade can be measured.
Impact
Analytics reporting verified. Booking conversion is now an instrumented metric.

Canonical Tags — www. Sites

What
Added/audited canonical link tags on the four canonical pages of each agency site: main (/), terms of service, privacy policy, contact.
Why
Without canonical tags, www.example.com/ and example.com/ look like duplicate content to search engines and split SEO juice. Canonical tags collapse them into one indexable URL.
Impact
SEO consolidation across the agency sites. No more split indexing on apex vs. www.

Two parallel DNS hardening passes — one for each sending identity an agency uses.

DNS / SMTP — CRM Sending Domain

What
Updated each agency's DNS records (SPF, DKIM, DMARC, MX where applicable) for the CRM email-sending domain, against our canonical deliverability standard.
Why
Email deliverability is the silent killer. A misconfigured DKIM record lands appointment confirmations in spam, and the agency never finds out until clients start no-showing.
Impact
CRM email auth is now correct across the agency roster. Confirmation deliverability restored.

DNS / SMTP — Business Email

What
Same DNS hardening as the CRM sending domain, applied to each agency's business-email–backed sending identity.
Why
Many agencies send some traffic through the CRM and other traffic (e.g., human reply emails) through their business email. Both sides need correct auth or one side gets quarantined.
Impact
Both sending paths now pass SPF/DKIM/DMARC.

The cross-cutting infrastructure work — dashboard, key registry, stress test, end-to-end check — that turns "works for us" into "we can prove it works."

Stress Testing — Booking Stack

What
Ran controlled load tests against the booking + voice agent stack (Voice Agent → AI Workflows → CRM) for each agency.
Why
The March release tightened the booking flow; April was the first chance to confirm the tightened flow holds up under concurrent traffic. Stress testing surfaces race conditions that a single happy-path call never reveals.
Impact
Confirmed the booking pipeline stays stable under concurrent load. Identified per-agency outliers needing follow-up.

Application Dashboard — Launch

What
Stood up a centralized application dashboard, version-controlled and deployed via our application hosting stack, that surfaces per-agency platform state.
Why
Maintenance was being run out of a spreadsheet. A real dashboard gives the team a live view of which agencies are healthy, which need attention, and what the last patch did to them.
Impact
Single pane of glass for agency health. The maintenance spreadsheet is now the input, not the interface.

Platform API Keys — Centralized Registry

What
Provisioned a per-agency platform API key set, stored centrally and surfaced through the dashboard.
Why
Keys were scattered across services (voice, workflows, AI provider, calendar, database). Centralizing them in a managed registry lets us rotate, revoke, and audit without paging through five different consoles.
Impact
Key inventory is now centralized. Rotation and revocation are O(1) instead of O(n services).

Calendar v2 — End-to-End Functioning Check

What
End-to-end functional check: booking through the new website embed → AI workflow → CRM calendar with the new calendar ID → confirmation email via the freshly-DNS-hardened sending path.
Why
This is the integration test that ties the deliverability work, the database migration, the dashboard, the Platform API keys, the new calendar embed, and the new calendar ID storage all together. None of those individually prove the booking path works; this check does.
Impact
Confirmed end-to-end booking pipeline operates on the new stack.
Cross-Month Theme

Correctness, then infrastructure

March was correctness — make the booking flow stop lying about availability and stop creating duplicate calendar artifacts. April was infrastructure — the deliverability, observability, credential management, and dashboard work that turn the cleaned-up flow from "works for us" into "we can prove it works, for every agency, at any time."