OOctwin Platform Guides
Octwin Platform — Features

Octwin by Cequens

Conversational agents for WhatsApp and the web.

Build, launch, and operate AI agents that talk to your customers where they already are — then handle the whole journey, from first hello to paid order.

Explore the guides See how it works
WhatsApp Business Web chat widget
Multi-tenant No-code flows Tap & free-text Commerce CRM & cases Journey analytics Voice & image

How it fits together

One platform between your customers and your domains.

Messages arrive from any channel, the platform routes and runs the conversation, and your business logic lives in self-contained packs — each with its own data, isolated per tenant.

CHANNELS PLATFORM CORE YOUR PACKS WhatsApp Web chat Conversation engine • Inbound routing & signatures • Dual routing — AI turn or direct tap • YAML flow runtime (pause & resume) • Channel-agnostic rendering Real-estate broker Commerce Your domain… Per-tenant data — isolated by workspace

Channels → conversation engine → packs, over per-tenant data. Add a channel or a pack without rewriting the middle.

How a turn works

Two lanes for every message — one smart, one instant.

Free-text goes to the AI agent to interpret. A button or list tap is already a decision, so it routes straight to the right step — no model call, which is what keeps high-volume conversations cheap and fast.

Inbound message AI agent interprets free text FREE TEXT Direct route no model call BUTTON / LIST TAP Flow / tool runs the step Reply per channel

The same agent handles both lanes; taps skip the model entirely.

What it does

One agent, the whole customer journey.

Every capability below ships today and works across both channels — the agent expresses intent, and the platform renders the right experience for WhatsApp or the web.

Reach

Meet customers on their channel

Run the same agent on WhatsApp and a web widget. Lists, buttons, and carousels are composed once and adapted to each channel's limits automatically.

WhatsApp · web widget

Build

Author in flows, not code

Describe conversations as declarative YAML flows. They pause for input and resume exactly where they left off on the next message.

declarative · pause & resume

Route

Taps and free text, together

Free-text runs the AI agent; taps route straight to the answer — faster replies and lower cost, with no model call when it isn't needed.

dual routing

Sell

Commerce built in

Show a catalog, send single- and multi-product messages, build a cart, turn it into an order, and take payment — inside the chat.

catalog → cart → order → pay

Serve

Cases, records & contacts

Escalate to case queues with routing, SLAs, and dispositions; keep customer records so the agent always has the full picture.

queues · SLA · records

Understand

See the journey and the cost

Track how conversations move through your funnel with journey analytics, and watch token usage and cost per workspace as you scale.

journey · usage

Listen

Voice & image, understood

Customers can send a voice note or a photo; the platform transcribes and reads them so the agent responds to what was actually said or shown.

transcription · vision

Notify

Reach back out, in the service window

Scheduled and event-driven notifications — reminders, updates, follow-ups — reach the customer on the web widget, and on WhatsApp inside the 24-hour service window Meta allows. Business-initiated sends outside that window require an approved WhatsApp template; that path is still landing.

reminders · 24h window

Operate

A console for your team

Manage everything from a multi-tenant console with real per-user sign-in and role-based access. Each workspace sees only its own data.

multi-tenant · RBAC

Pluggable by design

One platform, many domains.

Each business vertical is a self-contained pack — its agents, flows, data, and channels declared in a single manifest. Add a new bot for a new industry without touching the platform underneath.

SK
Starter kitA minimal pack to scaffold your own vertical from
MP
Everything else, from the marketplaceEach pack's capability list is derived from what it declares — never a claim an author typed
+
Your domain nextDeclare a manifest, author flows, provision — and go live