Website and public pages

Public marketing and resource surfaces are available.

Authentication surfaces

OIDC and token-based application access are part of the live platform surface.

Inbound telephony handling

Webhook-driven Twilio call handling and continuation routes are in the current backend surface.

Public incident history

Not yet productized as a full uptime and incident timeline. This is still a gap.

Current status communication

Status communication is still manual. The product should eventually expose a dedicated public status feed with incident history and subscriber updates.

Core monitored surfaces

Authentication, inbound telephony handling, routing logic, background jobs, and website access are the operational components that matter most today.

Support path

Urgent issues should escalate through a clear support address and internal operating process rather than generic website contact forms.

What still needs to happen

A production-grade public status page should eventually add uptime history, incident posts, and component-level state over time.

Operational visibility and support path.