Updates
Product changelog
Changes shipped to the EchoCody platform and public site. Entries are written from repository history and signed release notes only. Where verification is incomplete, it is stated on the entry.
- Voice
- Integrations
- Reliability
- Compliance
- Analytics
- Experience
- Compliance
Service role data boundary documented and access denials monitored
The five server-only tables covering call transcripts, call receipts, latency telemetry, the consent ledger and the security log now carry an explicit service role policy with no grants for browser or signed-in roles, and the intended pattern is recorded in a register the internal console renders. Any permission or policy refusal from those tables is classified, logged as a security event with a hashed client fingerprint and no row data, and alerted on the first occurrence in production.
- Client roles hold no grants on these tables, so a mistaken query returns a permission error rather than data.
- Experience
Interactive Simulate stage, blueprint export and stage analytics
The System page Simulate stage is now an interactive, clearly labelled illustrative sandbox: you choose an intent, the qualification fields captured and a scenario, and the page shows the Connect, Build and Launch evidence that configuration would produce. Nothing is booked, written or sent. Every selectable stage can be exported as a formatted Agent Blueprint PDF containing the disclosure, supported intents, qualification fields, approved objections and prohibited claims. Approved objections are now expandable question and answer pairs, and each stage interaction emits an analytics event so progression from Connect to Improve can be measured against bookings.
- The Simulate sandbox is an illustrative workflow demonstration. It creates no booking, no CRM record and no call.
- Exported blueprints are sample specifications, not a customer configuration.
- Experience
Public workflow and outcome documentation
The System page now documents one governed workflow in five stages: Connect, Build, Simulate, Launch, Improve, each with inputs, outputs and exit evidence. The homepage adds a deterministic, clearly labelled illustrative replay of what exists after a call ends.
- The replay is an illustrative demonstration. It writes nothing to a CRM and creates no lead or call record.
- Reliability
Web demo P0 hardening: mode integrity, durable receipts, consent ledger
The web demo no longer degrades silently. Each session is labelled live or demo, and when the live line cannot be reached the interface states Demo mode, live line unavailable instead of pretending the call is real. Every session now carries a unique call event id used as an idempotency key, and terminal call records are delivered with bounded retries and backoff so a single network failure does not lose the record. A server-side, append-only consent ledger records granted, revoked and superseded events with an evidence hash, and outbound actions fail closed when no verified active consent exists.
- Schema for the receipt and consent ledgers is committed in the repository migration set.
- Verification of the migration against the production database has not been independently confirmed here. Treat remote schema state as unverified until an owner-run check is recorded.
- Compliance
Inbound-only voice boundary enforced in code
Outbound call initiation is disabled at the policy layer rather than by convention. The voice stack answers inbound calls and web sessions only, and the same policy text is surfaced on the compliance and trust pages.
- Reliability
Voice session health endpoint
A health endpoint checks the realtime voice path and returns a non-cached failure status when the live line cannot be established, so a broken session surfaces as an explicit error rather than a hung interface.
- Analytics
Conversion and demo analytics events
Book a demo interactions and voice demo starts emit structured analytics events, and the footer carries a build revision indicator so a reported issue can be tied to a specific deployed build.
- Compliance
Call and latency records locked down
Voice call and turn latency tables were restricted to service-role access with row level security enabled, and security events are logged for anomaly review.
This log covers platform and site changes. Customer deployments are configured per account, so an entry here does not mean the capability is enabled on your line.