Skip to content
Platform overview

One platform over one dataset.

Behaviour, delivery, consent and contact data are the same data in one system. A journey can branch on all four without an integration.

Book a Demo
The starting point

Start with the customer, not the channel.

Every interaction begins with what a person has done, what they've received, where they engage, and what they've agreed to. That context shapes the next step.

The loop, page by page

Five stages. One dataset underneath all of them.

Each stage is a module you can open on its own. Results from the last stage arrive as events for the first.

  1. 01

    Capture

    → Customer Intelligence

    Events from app, web and servers, anonymous history stitched to the known customer, a contact record that tells you when and where to send.

    EventsApp, web and serverSDKsAndroid, iOS, Flutter, React NativeWeb TrackerAnonymous history, stitchedIngest APIQueued, absorbs spikesContactsBest time, best channel, consentSegmentsSix condition families, live size
  2. 02

    Ask

    → Analytics & Asklytics

    Plain-language answers, boards, funnels, live KPI trees, RFM, session analysis.

    AsklyticsAsk in plain languageBoardsInsights and reachabilityFunnelsPer-contact, in orderMetric TreeLive KPI model, owned nodesRFMChampions to Lost, maintainedSession AnalyzerRules for what did not happen
  3. 03

    Act

    → Journey Automation and Campaigns

    24 journey blocks; campaigns with reach and cost known before launch.

    Journeys24 blocks, no releaseCampaignsReach and cost before sendStoriesFull-screen, in your live appTemplatesOne message, every channelSmart LinksResolve to the exact messageSending APIsSend by intent from your systems
  4. 04

    Send

    → Messaging & Delivery

    Six channels, routing you control, fallback on real carrier signals, push on our own network.

    Push & InboxOver our own networkWhatsAppTemplates, buttons, cost protectionSMSLanes, replies, limitsEmailBlocks, not an HTML boxVoice & IVRA step in the graphRoutingYour order, effective on save
  5. 05

    Measure

    → Back into the record

    Every message keeps its route and outcome, and every result lands back as an event.

    Campaign AnalyticsLift against a baselineDelivery LogsRoute, attempts, outcomeDashboardsEight standing viewsConversion EventsWhat counts, what it is worth
↻ BACK TO CAPTUREEvery result lands back as an event, so the next turn starts sharper.
ACROSS EVERY STAGEAI agents, built in and yours.Four agents that do a named job and show their working, plus an MCP Server so your own agents can work the platform within the scope you grant.
See the AI page
Different teams, one context

The work differs. The customer context shouldn't.

Marketing builds audiences and campaigns. Product investigates drop-offs. Operations handles replies and exceptions. Technology evaluates the connections and the deployment. The work differs. The customer context shouldn't.

START SMALL

Start where the need is strongest.

Send transactional traffic through the API today with none of the rest switched on. Add a campaign. Build one response-driven journey. You don't turn on the whole platform to prove value.

  1. 1Transactional traffic through the API
  2. 2Add a campaign
  3. 3One response-driven journey
KEEP WHAT WORKS

Keep the systems that already work.

A journey can ask your core system a question mid-flight and branch on the answer, while that system keeps owning the rule.

The pilot

One use case. Six to eight weeks. A number you agreed first.

Book a Demo