A new touchpoint

Listrak Converse

Verified, two-way conversations that sell, serve, and remember — inside the message thread your customers already live in.

Marketing earns the moment. Converse has the conversation.

RCS isn’t a message you send. It’s an app inside text messaging.

Verified sender, every channel

RCS · Apple Messages for Business · WhatsApp · SMS fallback

One workflow, authored once — delivered on whichever rail the customer answers.

Start building free See how it works Point your AI at us
Your brand✓ verified business
Hi Matt — around this time last year you found the perfect anniversary gift. Shall we plan this year’s together?Last year · the small heart box
Yes, please!Same as last year
Wonderful — three ideas coming right up.

The idea

A touchpoint that talks back — and transacts.

Proactive, from a verified sender

Your signals decide the moment; Converse opens a real conversation — not a blast with a link.

Buttons and pretty pictures, never a form

Guided questions, tappable choices, product carousels, live checkout — all native to the thread. No app. No login.

Every tap is structured data

Answers land as fields on the customer record the moment they happen — who it is for, the occasion, the budget, the product — ready for segmentation.

It remembers

Occasions, preferences, people. The thread becomes relationship history, not a transcript.

58%
higher click-through
RCS vs. SMS · text sends
200%
higher revenue per send
RCS vs. SMS · per-send revenue
1 sec
always-on replies
with warm handoff to your own team

RCS lift: Listrak in-market beta, retail brands, 2024–25.

Picture it

Imagine intake finished, validated and filed — before the patient walks in.

Everyone gets this backwards

You are not sending a message. You are shipping an app.

Ask most teams what RCS is and they describe a nicer text — a logo, a picture, a link. That is the smallest thing it does. It carries cards, carousels, lists, quick replies, forms, location, payments and state. A person taps, chooses, uploads a photo, pays, and comes back tomorrow to a thread that remembers.

So you do not write a message. You design a conversation — the questions, the branches, the things you must collect — publish it, and it runs. Several of them together become a kit: an entire branded experience living in the thread. Returns and reorders and loyalty are not three campaigns. They are one place your customer already is.

A campaign ends. A conversation keeps working.

From idea to working app

Drop a PDF. Get a working conversation.

The hardest part of building on a new channel has always been the blank page. So do not start there. Hand us whatever you already have — the returns policy, the intake form, the flowchart on the whiteboard, the process somebody described in an email — and the AI turns it into a real, running, branching conversation you can open on your own phone in minutes.

A document

A PDF form, a spec, a policy, an SOP. It reads the fields, the rules and the order, and builds the steps.

A picture of a process

A flowchart, a diagram, a whiteboard photo, a napkin. Branches become branches.

A sentence

“Let customers return an item, pick a reason, photograph it and get a QR code.” That is enough to start.

Then you edit it like a normal person — drag, rename, add a step, change a rule. The AI writes the first draft. You stay in charge of it.

Bring your own AI

Point Claude at us. Go make coffee.

Every capability here is a plain REST endpoint and a typed AI tool — the same engine either way. Connect your assistant to /mcp with your API key and it reads the docs itself, learns your data model, and builds the thing end to end.

Claude Code, claude.ai, ChatGPT connectors, Replit, Cursor, your own agent — anything that speaks MCP. And if you would rather not use AI at all, the visual builder and the API do everything the agent can.

MCP connectorREST APIVisual builderYour key or ours
An AI agent connected over MCP, building on the platform

An agent building it for you, over /mcp

A few of the things running today

If a person follows steps on a phone, it belongs here.

Marketing automation sends. This runs process. Same channel, entirely different job.

Returns, without the portal
Pick the item, choose a reason, photograph the damage, get a QR code or book the pickup. No login, no app, no call centre.
Retail
Replenishment in one tap
“Time for new blades?” A carousel of the right options and a reorder that finishes inside the thread.
Retail
Loyalty people actually use
Balance, rewards, redemption and a personal offer — interactive, not an email nobody opens.
Loyalty
Ordering & in-thread shopping
Browse a real catalogue as rich cards, multi-select into a cart, pay in the thread. Commerce without a browser.
Commerce
Post-purchase onboarding
Setup that branches by model, accessories and skill level — so the product gets used instead of returned.
Onboarding
Booking & rescheduling
Real availability, confirmation, reminders and a one-tap change — without a phone tree.
Service
Customer service, AI-assisted
An assistant answers in the thread, follows a real process, and hands to a human the moment it should.
Support
Intake & onboarding forms
Patient intake, claims, applications, KYC. Structured answers, validated, with the documents attached.
Regulated
Field & contractor work
Dispatch, checklists, photo proof and GPS — for crews and subcontractors who install nothing. ServiceProof ›
Operations

Every market, one build

Author it once. It speaks their language.

Your customers are not all English speakers, and the usual answer is to build the whole conversation again per market — then maintain every copy of it forever. That is why so many brands quietly serve one language and lose the rest.

Here one authored conversation runs in the language each person is actually using, and every answer lands in your storage language, normalised. Your analytics do not fragment by market. Your team reads one set of results.

Out of the box

English, Spanish, German and French ready today. Korean, Chinese, Portuguese and more are a click away — not a rebuild.

One workflow, every market

Change a step once and it changes everywhere. No per-language fork to keep in sync, and no market left on last quarter's version.

Data stays comparable

Answers normalise to your storage language, so a report spans every market instead of one per locale.

EnglishEspañolDeutschFrançais한국어中文Português+ more

Going multilingual should not mean building it twice.

Not instead of your app — the on-ramp to it

Your best channel for getting the app installed.

Most of your customers will never install your app, and the ones who would need a reason bigger than a banner. So give them the value first, in the thread, with nothing to download — then hand them into the app at the exact moment it is obviously worth it. Immediacy of SMS, capability of an app, and a deep link at the point of intent.

Reach the 100%

Everyone has the messaging app. Run the experience there, and stop losing the majority who never downloaded yours.

Hand off at the peak

Deep-link straight into the right screen while the person is already engaged — not from a push notification days later.

Re-engage the lapsed

A thread is still there months later. Bring somebody back without asking them to reinstall anything.

Your systems, in the conversation

Connect anything. Then trigger everything.

A conversation is only as good as what it knows. Sync from your ERP, OMS, CRM, PIM or warehouse — a packaged platform, a REST API, or your own SQL Server or Postgres, which is the deepest integration there is. Live product data, real order history, actual entitlements.

Then every tap becomes an event. Fire a webhook, call your API, start the next workflow, page a human, or hand the thread to an AI agent — the moment it happens, structured and validated.

Zapier waits for your software to do something. We wait for your customer to.

Sync from any system, enrich in the conversation, hand the results back

In from your systems, back out as events

Why this does not exist anywhere else

Everyone else sells pipe. This is the workflow engine.

A dozen providers will deliver an RCS message for you. Their journey builders are marketing sequences — send, wait, follow up. None of them orchestrates work: parallel paths a person can take in any order, branching on who the customer actually is, loops, approvals, signatures, validated capture, memory across sessions.

That is the difference between a nicer newsletter and an application that happens to live in a thread.

You never touch a carrier

Brand verification, sender provisioning and deliverability are handled — through Infobip, at planetary scale. You get one contract and one API.

You arrive verified

Your name, your logo, a checkmark at the top of the thread. Not a short code nobody recognises.

Write once, render native

Author the step once; RCS, Apple Messages for Business, WhatsApp and SMS each render it in their own real shape. Add a channel later and nothing you built changes.

Who builds here

Brands, agencies, and platforms who ship it as their own.

Brands & retailers

Retail · DTC · Subscription · Grocery

Returns, replenishment, loyalty, ordering and post-purchase — in the one place every customer already has. Start with a single workflow and grow it into the whole experience.

Agencies & consultancies

Build once · Reuse per client

Build a workflow library and deploy it client after client, each under their own verified sender. A new channel to sell that nobody else can deliver yet.

SaaS platforms & ISVs

Embed · White-label · Per-tenant

Put the whole engine inside your product under your own brand. Your screens, your customers, our rails — rich messaging becomes a feature you ship instead of a vendor you resell.

Who is Listrak?

Twenty-five years of messaging at planetary scale.

Listrak is the cross-channel personalization platform — email, SMS, push, web, in-store, and now RCS — sending billions of messages for over a thousand brands. Listrak Converse extends that to work: you do not just reach people in the thread anymore, you do real business there.

One platform. One conversation. Real business, everywhere.

Start free

Tell us what you want to build. See it on your phone today.

Bring a PDF, a flowchart, or one sentence. Free sandbox, a real tenant, and it publishes to a real handset the first day.

Start building free Get a demo Developer portal & API