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: 13 August 2026 · See what shipped → · 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 (v25.0). Retryable error handling, 24h window gating.

✓Categorized inboxInteractive / Inbound / Outbound tabs with smart sections (Your turn, Window closing, Waiting 6h+), endless scroll, name+number identity on every row, keyboard flow (↑/↓/Enter/Esc, "/" to search), message-content search, thread history with day separators and an unread divider.

✓Broadcast truth & retryEvery broadcast is a collapsible inbox group: sent / replied / failed / awaiting reply, failure reasons in plain language (marketing caps, unreachable numbers), one-click policy-gated retry, plus automatic staggered retry for capped sends.

✓Inbox productivityCanned replies with "/" insert, conversation labels + label-filtered views, internal notes, resolve/reopen with bulk-resolve, inline assign/rename popovers, per-thread draft memory, auto-growing composer.

✓Rich messaging + AI reply assistInteractive buttons, list menus, CTA URLs, quote-reply, reactions, typing indicator, read receipts. AI "suggest reply": never auto-sends.

✓AI auto-replyAnswers customers on its own, but only from facts you've explicitly given it. Won't improvise about your pricing or policies. Runs on a schedule you set, and hands off to a human quietly on anything outside scope. Off by default; you turn it on per workspace.

✓Two-way translationDetects the language a customer writes in and translates your reply into it automatically. Shown as a second line under each message so you see exactly what was sent; the original is never replaced.

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

✓Broadcast campaignsTemplate sends to composable audiences. Live WhatsApp-bubble preview, delivery funnel, rate-limit-aware retry, scheduling.

✓Contacts + consent ledgerImport, tag, segment. Payload-based consent buttons, full opt-in/opt-out audit trail, GDPR erasure + export.

✓Full REST API (97 endpoints)Headless access to every platform capability: contacts, segments, campaigns, sequences, inbox, products. OpenAPI 3.1 spec, idempotency keys, rate-limit headers, error code contract.

✓Named developer API keysCreate named, scoped (send/read/manage), independently revocable API keys. Last-used tracking, optional expiry, up to 20 per workspace. Managed from the Developers tab or via the API itself.

✓Outbound webhooksHMAC-signed events (8 event types: messages, status, optout, contacts, consent, assignment, campaigns) with retry + DLQ visibility.

✓n8n / Zapier / Make integration pathConnect Klaros today via each platform's generic webhook and HTTP modules, no published app required yet. Every API operation has a stable id, so OpenAPI import into n8n just works.

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

✓Automation basicsGreeting, away, keyword auto-replies. Welcome messages, ice-breakers, persistent menu. Consent flows.

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

✓Template managementCreate, edit, resubmit approved templates. Media library reuse for headers. Status tracking via Meta webhooks.

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

✓Team inbox + auto-routingMulti-agent seats, per-agent login, admin/agent roles, conversation assignment, per-agent API keys. Auto-assignment with round-robin, least-busy, and sticky strategies. Skill-based filtering and per-agent capacity caps.

✓Real-time push inboxWebSocket-powered live updates via Cloudflare Durable Objects. Inbound messages, delivery receipts, and typing indicators arrive instantly. Automatic reconnect with exponential backoff and 30-second polling fallback.

✓Contact detail panelRight-pane identity panel alongside the thread: avatar, name, consent/known/business badges, editable lead stage, internal notes, company details, and linked numbers for multi-number contacts.

✓WhatsApp FlowsCreate, publish, manage Meta's in-chat forms. 10 pre-built flows: booking, lead qual, feedback, and more.

✓WhatsApp Business ToolsProfile editor + photo, QR code manager, welcome messages, ice-breakers, persistent menu, from the dashboard.

✓Campaign audience builderComposable audience sources: segments, contact lists, groups, all opted-in. Mix, match, deduplicate per campaign.

✓Interactive message composerSend reply buttons, list messages, CTA URLs from inbox and campaigns. Visual buttons builder in compose area.

✓System health & monitoringToken expiry alerts, DLQ depth, number quality tracking, setup readiness checks, inbound deduplication.

✓Drip sequencesTime-based message sequences with pause-on-reply. Segment or individual enrollment, consent-checked at every step.

✓CTWA ad attributionClick-to-WhatsApp ad referral capture: ad source, campaign ID, headline shown as "From ad" context chip in threads.

✓Cost guardrailsBudget-cap alerts, template category-drift detection, cost anomaly flagging, spend trend/forecast with 30/60/90-day projection.

✓Onboarding wizardConversational + interactive guided setup. Number connection, display name validation, eligibility check, Meta billing walkthrough.

✓Product library & catalogR2-backed media product library with optional numeric price and stock. Meta Commerce Catalog integration for single and multi-product messages.

✓Commerce: orders & payment requestsA received cart becomes a tracked order (received → payment requested → paid → fulfilled), not a dead-end chat bubble. Multi-item payment-request composer, works with any payment provider's link, one automatic reminder on an unpaid request. Opt-in per deployment.

✓Overview cockpitOutcome funnel, do-next action row, zero-markup cost strip, consent funnel, network stats: your operations at a glance.

✓Relationship context panelSynthesis-first "relationship brief": consent provenance, conversation cost, message timeline, tags, notes alongside the thread.

✓Behavior sequences + Milestones APIOne API call from your backend when a customer acts. Your rule sends the next-step template from your number. React to what customers do, not what day it is. Consent-gated, one send per contact per rule.

✓Contact import & syncPull contacts from Google, Outlook, iCloud via Apps Script or CardDAV. Upload CSV/vCard/JSON with auto-format detection. Nightly auto-sync, source provenance badges, progressive WhatsApp verification.

✓Meeting schedulerTappable time proposals sent as WhatsApp reply buttons, resolved back into the same thread. Booked-state confirmation, reschedule-at-confirmation, pre-call reminder template. No booking links, no app switches.

✓Operational intelligence engineGeneric entity model (projects, matters, sites) with structured capture, auto-routing, contact assignment, and record timelines. Per-workspace opt-in via vertical packs.

✓Vertical solution packsSix turnkey packs, opt-in per workspace from the Extensions catalog: Construction PMC, Field Sales, Sales Deals & CRM Pipeline, Commerce & Payments, AI Tools, and QR Codes & Public Pages. Each wires the entity engine, watchdogs, and digests into a domain-specific configuration.

✓Entity enrollment via WhatsAppInvite team members into entity roles via WhatsApp. Enrollment lifecycle: invite, accept, assign role. Pack provisioner auto-configures capture forms and watchdog rules per vertical.

✓Proactive watchdogsRule-based monitoring on entity records: missing daily reports, stale projects, field-match triggers. Auto-escalation with cooldown and dedup. Fires WhatsApp alerts before problems compound.

✓Auto-generated digestsThree work products delivered via WhatsApp: per-project narrative summaries (client-ready), contractor performance briefs, and morning priority pushes. Generated from structured records, not manual reports.

✓Cost advisorDetects avoidable spend: free-window waste (templates sent when a free reply was possible), marketing-cap waste (sends that hit Meta's daily cap), and real category mix vs. what you intended.

Now: actively building

In development

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

Building

CTWA rollup analytics

Aggregate Click-to-WhatsApp ad performance into Overview and Costs dashboards: cost-per-conversation from ad spend through to reply, broken down by ad campaign.

What's done: Referral capture, ad source parsing, campaign ID extraction, and "From ad" context chip in threads are all live. Rollup analytics dashboards and attribution reporting are next.

Acquisition

Building

Relationship-stage progression

Contact rows in the inbox gain a relationship-stage chip: from first-touch through active conversation to retained. The stage derives from consent state, reply cadence, and conversation history. Filters and lenses let you focus on contacts at each stage.

What's done: Collapsible Your-turn / Their-turn sections, unread rollup, 24h-window countdown on rows, relationship context panel, contact detail panel (identity, badges, lead stage, notes, linked numbers), real-time WebSocket updates, and auto-assignment routing are all live. The stage chip and progression filters are next.

Inbox UX

Building

Visual flow builder

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

What's done: The branching data model and resolution engine are built and live. A contact can now take different paths through a sequence, not just march down one ordered list. What's next: a way to author that branching without writing to the API directly, working up toward a full drag-and-drop canvas.

Automation

Next: planned, not started

Planned

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

Planned Wedge

Threads that need a person, surfaced before they rot

The groundwork shipped in August: Klaros already detects a conversation where the customer spoke last and nobody replied, works out how long is too long from that business's own median reply time, and alerts the operator. On its first run it found a real enquiry that had been waiting 62 hours. What's next is turning that same detection into a short, ranked list of relationships that need attention today, each one carrying the reason it is on the list.

What's done: The sweep, the alerting, and the acknowledgement that fires when somebody writes again while still unanswered are all live. What's next: three more detectors on data that already exists (consent asked and never answered, a customer gone quiet after a purchase, an enquiry that never got a first reply), writing into the recommendation surface that is already built and currently switched off. Deliberately no AI in this phase: it is a scheduled job and a set of database queries.

Relationships

Planned Wedge

Conversation memory that survives the context window

Today the assistant reads the most recent stretch of a thread. That is a window, and a window is a truncation: on a long relationship it cannot know how the relationship began. The plan is to summarise a conversation when it ends rather than discard it, so a five-year customer costs the same to answer as a stranger and is answered better.

Honest status: designed, not built, and gated on two things first. Data import has to exist, because memory that dies when you migrate from the hosted edition to your own infrastructure is worse than no memory. And the extraction has to carry provenance: every remembered fact clickable back to the message it came from, because a claim you cannot check is one you cannot correct. Where a managed service can do this better than we can, we intend to use it rather than rebuild it.

Relationships

Planned Wedge

Four more vertical packs

Legal Firm, Fleet & Logistics, Facility Management, and Healthcare Clinic join the six packs already live in the Extensions catalog. Same entity engine, same watchdogs and digests, a new domain configuration each.

What's done: The pack registry, provisioner, and Extensions catalog UI are all live, already carrying six packs (Construction PMC, Field Sales, Sales Deals & CRM Pipeline, Commerce & Payments, AI Tools, QR Codes & Public Pages). What's next: backend registration for each of these four, following the same pattern as the packs already shipped.

Platform

Planned Wedge

Portfolio dashboard

A single screen that shows every active entity (project, matter, site): status, last update, team responsiveness, flagged interventions. Built for the person who manages 10 projects and currently scrolls 10 WhatsApp groups every morning.

What's done: The entity engine, watchdog alerts, silence detection, and escalation are all live. What's next: a cross-entity portfolio view that rolls up entity status, intervention history, and digest outputs into one dashboard.

Operations

Planned

AI extraction: photos, voice, documents

When someone sends a site photo, a voice note, or a PDF report, the system reads it. A photo gets classified ("rebar installation, level 3, appears complete"). A voice note gets transcribed and tagged. A progress report gets its key numbers extracted. All filed under the right entity, automatically.

How it works: Schema-driven extraction powered by Workers AI. Each vertical pack defines what to look for: activities, completion percentages, issue severity, materials. The structured path (WhatsApp Flows + entity capture) handles 80% of data collection; AI extraction handles the unstructured 20%.

AI · Operations

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

Cross-entity performance scorecards

When the same contractor, vendor, or team member works across multiple projects, their performance pattern becomes visible: responsiveness, issue frequency, delay correlation. The data already flows through WhatsApp. We just connect the dots.

Operations

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

Published Zapier / Make app

A listed app in the Zapier and Make directories, so connecting Klaros is a search-and-click instead of pasting in a webhook URL. The integration path itself already works today via each platform's generic HTTP/webhook modules and our OpenAPI spec (see "n8n / Zapier / Make integration path" above). This is the packaging layer on top of that, not new plumbing.

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

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

Commerce: recurring orders + native checkout

Recurring orders for repeat-purchase verticals (jewellery, FMCG), plus a native in-chat checkout (WhatsApp Pay / UPI) that doesn't need a payment link at all. Table stakes for commerce-first use cases.

What's done: Product library with numeric pricing, cart capture into a tracked order record, multi-item payment-request composer, order status tracking (received → payment requested → paid → fulfilled), an automatic unpaid-reminder, and connecting your own Razorpay gateway so payment links generate automatically (no manual paste-in) are all live. What's remaining: recurring/subscription orders, native in-chat checkout without a payment gateway in the loop, and Shopify/WooCommerce integration. Commerce is a different race; we'll build deeper when pulled.

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

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 ship auto-assignment (round-robin, least-busy, sticky, skill-based) and per-agent capacity caps. What we do not build: Salesforce-grade role hierarchies, department-level queue routing, or SSO federation for 50+ agent call-center teams. The line is practical team routing versus enterprise ticket infrastructure.

Becoming a payment processor

We ship the order tracking and the in-chat payment request (India, WhatsApp's order_details message), but the payment link itself comes from your own provider (Razorpay, PayU, whoever you already use), and the money never touches us. We won't become a PSP or hold funds. That's market-specific, tightly regulated, and orthogonal to our value prop.

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-deployed 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).