Status

Where ConvoTide actually stands, component by component.

This page states the operational posture of ConvoTide’s integrations as they are today — not a live incident feed. ConvoTide is at pilot stage: nothing here is running as a production service yet, so there are no incidents to report and no uptime percentage to publish. What we can state honestly is which components are built, which are still being connected, and what each one is waiting on.

Component posture

WhatsApp Cloud API (messaging)

In integration — not yet production

The send path — template-state checks, consent enforcement, signed webhook verification, delivery events — is built and covered by the platform’s automated suites. Switching it on for real traffic depends on Meta business verification and app review, an external gate we do not control. No live messages are sent or received through this integration today.

Payment gateway

In integration — not yet production

The billing engine — plans, wallet, invoices, trials and proration — is built and verified, and a signed payment-events ingest API is ready to receive gateway events. Connecting a live gateway account, including failed-payment events and auto-top-up mandates, is an external dependency. No live charges are processed today.

Core platform (workspace, inbox, campaigns, CRM, API)

Built — pilot stage

Built and covered by automated suites, and running behind sample data at pilot stage. What it does and refuses to do is described surface by surface on the product page and the developer documentation.

Incident monitoring

Not yet offered

There is no production service to monitor yet, so there is no public status feed. See the section below for what happens instead.

Live monitoring arrives with production launch

Plainly: a status page that always says “all systems operational” is a decoration, and we will not hang one here. Until ConvoTide runs in production there is no on-call rota and no incident stream — so this page states integration posture instead of simulating a feed. When production launches, this page (or its successor) will carry real, timestamped incident monitoring, and its history will start from that day rather than being back-filled.

How this page is maintained. It is updated by hand when a component’s posture changes, carries the dated review line below, and never shows an uptime percentage we have not measured. For what actually changed and when, read the changelog. How your data is handled is on the trust page.

Content reviewed October 2026 · owner: Zcode (implementation) · independent factual review: Codex QC, pending.

See what actually changed How your data is handled