Product Roadmap

What we're building — and what we won't.

Most companies hide their roadmap behind a sales call. We'd rather show you exactly where Klaros is headed so you can decide if it's the right fit — today or in three months.

Last updated: June 2026 · Request a feature →

Already shipped

Live in production

These are in your hands today — not "coming soon," not behind a flag.

✓Core messagingText, media, interactive, templates via official Cloud API. Retryable error handling, 24h window gating.

✓Inbox + AI reply assistConversation list, thread view, compose, media. AI "suggest reply" — never auto-sends.

✓Zero-markup cost dashboardReal Meta conversation costs by category, per campaign, cost-per-reply. Pre-send estimates.

✓Broadcast campaignsTemplate sends to segments with consent enforcement, delivery funnel, scheduling.

✓Contacts + consent ledgerImport, tag, segment. Full opt-in/opt-out audit trail, GDPR erasure + export.

✓REST API + OpenAPI specSend messages, manage contacts, trigger campaigns. Full OpenAPI 3.1 documentation.

✓Outbound webhooksHMAC-signed events (message.received, status.updated, optout) with retry + DLQ.

✓Multi-number supportConnect multiple WhatsApp numbers. Per-line inbox, per-line send, display name labels.

✓Automation basicsGreeting, away, keyword auto-replies. Consent opt-in/opt-out flows.

✓Self-hosted on CloudflareWorkers + D1 + R2 + Queues. Your account, your data, your infrastructure.

✓Template managementCreate, edit, submit for approval. Status tracking via Meta webhooks.

✓Full data exportExport contacts, conversations, consent records. Leave any time, keep everything.

✓Team inboxMulti-agent seats, per-agent login, admin/agent roles, conversation assignment, per-agent API keys.

Now — actively building

In development

Code is being written. These will ship within weeks, not months.

Building

Onboarding wizard

Guided, stepped connect-your-number flow with display-name validation, number eligibility check, and Meta billing walkthrough. Prevents the #1 rejection cause.

Why it matters: The biggest drop-off is new users failing to connect their WhatsApp number because of Meta policy edge cases. This wizard catches problems before they happen.
What's done: Embedded signup, token exchange, app subscribe, phone register all work. The wizard UX is being built.

Onboarding

Building

Campaign audience builder

Composable audience sources — segments, contact lists, groups, broadcast lists, or all opted-in contacts. Mix and match per campaign with deduplication.

What's done: Unified audience source model (migration 0054), resolver with dedup/pagination, UI audience builder component. Consent enforcement wired.

Campaigns

Next — planned, not started

Planned

Designed and scoped. Will begin after the "Now" items ship. Roughly 2–4 months out.

Planned Wedge

Relationship context panel

When you open a conversation, see the full relationship history: consent provenance, conversation cost, message timeline, tags, notes, and assignment history — in one panel alongside the thread.

Why this is different: BSPs show you a contact card. Klaros shows you the relationship — including exactly what you've spent on this customer and whether they're engaged. This is data no BSP can surface because they don't have your consent graph or cost transparency.

Inbox & AI

Planned

Click-to-WhatsApp Ads attribution

When someone messages you from a Facebook/Instagram ad, Klaros captures the ad source, campaign ID, and headline — then attributes every reply and conversion back to the ad that earned it.

What this unlocks: True cost-per-conversation from ad spend through to reply. The webhook payload already arrives; we just need to parse the referral object and surface it.

Acquisition

Planned

Canned replies + quick actions

Pre-written responses with / slash-insert in the compose box. Team-shared library. Cuts response time for common questions from minutes to seconds.

Team & collaboration

Planned

Conversation labels + saved views

Tag conversations (VIP, Urgent, Billing, Support). Create saved inbox views that filter by label, assignment, or status. Replace 4 overlapping inbox tabs with one inbox, many views.

Inbox UX

Planned

Drip sequences

Time-based message sequences: enroll a contact or segment, send template at day 0, follow up at day 3, final nudge at day 7. Pause on reply. Consent-checked at every step.

Status: The drip engine exists in code (enroll/unenroll/advance) but is behind a feature flag. Needs UI polish and segment enrollment UX.

Automation

Planned Wedge

AI next-best-action

Graph-driven suggestions: "Priya hasn't replied in 7 days — follow up?", "Rahul overlaps with 3 other contacts — merge?", "This segment's reply rate dropped 40% — pause campaign?" Powered by Workers AI on the consented relationship graph.

Why this is a wedge: BSPs can build chatbots. They can't build next-best-action on a consented relationship graph they don't have.

Planned

Agent performance + SLA

Response time tracking, resolution metrics, SLA timers, working hours configuration. Agent leaderboard and bottleneck detection. Depends on the multi-user model shipping first.

Team & collaboration

Planned

Interactive message builder

Send reply buttons, list messages, and CTA buttons from the inbox and campaigns — not just plain text and templates. Visual builder in the compose area.

Messaging

Planned

Zapier / Make / n8n integration

Connect Klaros to 5,000+ apps through Zapier or Make. Built on the existing REST API + outbound webhooks — the hard part is already done.

Integrations

Later — exploring

3–6 months

On the radar, not committed. We'll build these when a paying customer pulls — not when a roadmap says we should.

Exploring

Visual flow builder

Drag-and-drop conversation flow editor: if/then branching, wait nodes, API calls, human handoff. The BSP flagship feature — but our developer buyer often prefers code.

We'll build this when a tenant pulls for it. Until then, the API + webhook + n8n path is more flexible for our primary buyer.

Automation

Exploring

Mobile PWA inbox

A progressive web app that works on your phone — reply to conversations, see notifications, check costs. Not a native app (yet), but close enough for most teams.

The dashboard already works on mobile browsers. This is about push notifications, offline, and a proper app-shell experience.

Platform

Exploring

Catalog + product messages

Connect a Meta product catalog, send single/multi-product messages, capture cart and order events. Table stakes for e-commerce use cases.

Commerce is a different race — and we're relationship-first, not transaction-first. We'll build the minimum viable commerce layer when pulled, not lead with it.

Commerce

Exploring

FAQ AI agent

An AI agent grounded in your knowledge base that handles tier-1 questions automatically — escalates to a human when it's unsure. Powered by Workers AI.

Exploring

Shopify / WooCommerce app

Order event notifications (confirmed, shipped, delivered), abandoned cart recovery, product feed sync. Built on top of catalog + webhook infrastructure.

Integrations

Exploring

WhatsApp Flows (forms)

Meta's native in-chat forms for collecting structured data — feedback surveys, appointment booking, lead qualification. Rich UX without leaving the conversation.

Messaging

Not planned — by design

Won't build

These are deliberate choices, not oversights. Knowing what we won't build is as important as knowing what we will.

Instagram / Facebook / SMS / multichannel inbox

Klaros is WhatsApp-only. We don't believe in "unified inboxes" that do everything poorly. WhatsApp is the highest-ROI messaging channel in our markets — we go deep on one channel instead of shallow across five.

Per-message markup or hidden fees

We will never add a per-message markup. Our code literally has markup: 0. Revenue comes from the annual software license — your messaging cost is Meta's rate, period. This is load-bearing architecture, not a marketing promise.

Hosted / multi-tenant SaaS

We won't host your data. Klaros runs on your Cloudflare account because data sovereignty is the point. If you want a vendor holding your customer conversations, there are plenty of BSPs. That's not what we are.

Enterprise RBAC / SSO / department routing

We're building a light, effective team inbox — not an enterprise ticket routing system. If you have 50+ agents and need Salesforce-grade role hierarchies, we're not the right tool (and won't pretend to be).

WhatsApp Pay / payment collection

Payment is market-specific (India-only today), tightly regulated, and orthogonal to our value prop. Your payment stack is your problem — we'll surface order events, but we won't touch money.

How we decide what to build

Pull, not push

We don't build features because a competitor has them. We build when a paying customer needs something and can't work around it. Competitor parity is a losing race.

Wedge over parity

Features that deepen our moat (cost transparency, consent, relationship context, self-hosted sovereignty) get priority over features that just match what BSPs already have.

Depth over breadth

We'd rather be the best WhatsApp platform than a mediocre omnichannel tool. One channel, done right, beats five channels done half-way.

Ship, then polish

Every feature on this page ships as the minimum useful version first. We iterate based on real usage, not guesses about what "complete" looks like.

Get notified when features ship

Drop your email — we'll ping you when the features you care about go live. No spam, no drip sequences (ironic, we know).