Changelog
Moving your business forward.
Explore improvements to WhatsApp campaigns, CRM, lead management and business messaging, with the latest updates first. For current integration availability, visit the status page.
2026-10
Search that reaches the whole conversation
- Conversation search arrived in the inbox: the API accepts a query fragment against message bodies across the full thread, contact display names and phone numbers (case-insensitive, tenant-pinned), and the workspace inbox gained a debounced search field on the same parameter.
- A blank query returns the original conversation list byte-for-byte — search extends the list, it does not replace it.
2026-10
Guardrails moved into the dispatch path
- Quiet hours and frequency caps are now enforced at the campaign dispatch worker itself: a message that would breach a contact's cap is held, not sent, and releases when its window opens.
- Coexistence diagnostics: per-organization daily webhook de-duplication counters with an operator read surface, so double-counted echoes from a parallel setup are visible instead of silent.
2026-10
A harder event pipeline
- Failed provider events are quarantined for inspection instead of being dropped or retried blindly.
- De-duplication became organization-scoped, a retry sweep recovers missed events, and the queue takes SKIP LOCKED row locks so concurrent workers cannot double-process the same event.
2026-10
Bots you can version, trigger and edit
- Publishing a bot flow now creates an immutable version: versions can be listed and inspected, and rollback publishes a prior version rather than mutating history.
- Trigger keywords match by exact, contains or starts-with, with keyword alias arrays beside the built-in modes, plus an optional consent-gated fallback message sent at most once per conversation per day.
- Trigger sources grew beyond keywords: QR and click-to-WhatsApp referrals are captured as provenance, and a signed API-webhook event can start a bot run through the same run engine.
- The journey canvas became editable for drafts — including branch authoring — replacing its earlier read-only view.
2026-10
Commerce connectors, one console
- Shopify and WooCommerce connectors ship with suite coverage, alongside a payment-events ingest API that accepts signed gateway events with health and reconciliation endpoints.
- A single connectors console in the workspace covers all three: connection setup, enable/disable and health in one surface.
2026-10
A sharper sales workspace
- My Day: a prioritized work queue with explainable lead scoring — the reasons behind a score are visible, not just the number.
- New surfaces for contact journeys, campaign reports, the bot simulator, operations trends, plan lifecycle (trials, proration, renewals) and a migration wizard.
- Platform administration gained a WABA fleet view and a console for expiring support access.
2026-10
Reseller economics you can dial
- Margin became per-reseller and per-message: settlements math reads a margin dial instead of one flat rate, on top of the existing reseller tree, settlement statements and white-labelling.
2026-10
convotide.in itself
- The public site now carries sixteen canonical routes, each with an asserted sitemap entry, canonical URL and OpenGraph metadata.
- This changelog and the status page launched — both stating real posture, with a dated content-review line on every content page.
Stay informed. These updates cover ConvoTide. Availability of third-party services, including Meta and payment providers, is listed on the status page.