Skip to main content

​
Next Steps

The previous version of this document described the v0.1.0 implementation sequence. All items from that sequence have been completed or superseded. This page now reflects the current roadmap. For the full backlog, see the Linear project board.

​
Current Priorities

The following items are actively tracked and represent the near-term delivery focus. They are ordered by dependency and business impact, not by calendar.

​
BORD-88 — Click-to-Chat Webhook

The click-to-chat flow needs a production webhook handler to receive delivery receipts and read events from Meta. Currently, click-to-chat messages are sent but status updates are not captured. This blocks accurate message state in the inbox for click-to-chat-initiated conversations. Scope: webhook route registration, message status reconciliation, inbox state update.

​
BORD-97 — Inbox MVP Parity

The inbox must reach feature parity with the original MVP before the legacy interface can be decommissioned. Remaining gaps include thread-level search, bulk action support, and contact-side panel completeness. Scope: thread search, bulk read/unread/archive, contact detail panel, template send from inbox.

​
BORD-99 — Flows Builder

A visual flow builder for constructing WhatsApp conversation flows (menus, branching logic, conditional routing). This is the highest-value product differentiator on the current roadmap. Scope: drag-and-drop canvas, node types (message, condition, action, wait), flow persistence, flow execution engine.

​
BORD-118 — Mobile Responsiveness

The dashboard and inbox must be fully usable on mobile viewports. Current layouts break below 768px. This is required for operators who monitor conversations on mobile devices. Scope: responsive breakpoints, collapsible sidebar, touch-friendly inbox actions, mobile navigation.

​
BORD-112 — Meta API Monitoring

Continuous monitoring of the Meta WhatsApp Business API health, including webhook delivery reliability, rate-limit tracking, and error-rate alerting. Ties into the account alerts system (BORD-189). Scope: Meta API health dashboard, rate-limit utilization tracking, webhook delivery metrics, alert integration.

​
Completed from Previous Sequence

The following items from the v0.1.0 sequence are done:
  • Canonical model alignment — completed
  • Single ingress/runtime decision — completed
  • Durable Supabase-backed webhook and compatibility slice — completed
  • Coherent feature-flag and migration control system — completed
  • Inbox read-path hardening and one real template-send path — completed
  • Auth/RBAC and workspace scoping — completed (see Authentication)