Dispatch is a customer data platform (CDP) for retail businesses that sell both in person and online. It performs identity resolution across those channels — matching records to the same real person, phone number first — and keeps a single unified profile per customer that your marketing, suppression and win-back lists are then built from.

How is this different from the messaging tool I already use?

Your messaging tool sends. It takes the list you give it and messages everyone on it, including the same customer three times if they're on it three times. Dispatch sits underneath and decides who should be on the list in the first place. It isn't a replacement for your messaging tool — it feeds it.

Do I have to connect anything to try it?

No. The duplicate audit takes two CSV exports you already have and runs entirely in your browser, with no account and no integration. The demos need nothing at all. Connecting your live systems is a later conversation, after you know the number is worth it.

Does my customer data leave my computer?

Not for the audit — the file is read in your browser and never uploaded, so there's nothing for us to store, retain or delete. The live product is different by definition: it stores the customer records it merges, and that's covered in our Privacy Policy under the Digital Personal Data Protection Act.

Can the rules be changed to match how we work?

Yes — who's excluded from a broadcast, how long counts as inactive, what makes a customer worth a call rather than a message, and the column layout your exported lists come out in. That's the part we expect to fit to each business.

How long does it take to get running?

The audit gives you a number in a couple of minutes. Beyond that it depends entirely on what you sell on — which is why we ask before quoting a timeline. What we won't do is describe it as a months-long integration, because it shouldn't be one.

One customer list, however they bought.

Dispatch takes the customers in your billing software, the ones in your online store and the ones sitting in old exports, and keeps them merged into a single list — matched on the mobile number, as the orders come in.

One person stops being four contacts. You stop paying to message them four times, and you can finally see what a customer is worth across the counter and the website together.

Check your own list Or watch it run on sample data →

No signup, no card. Your file is read in your browser and never uploaded — Dispatch never receives it.

Three rows in your files

9876543210: at the counter
+91 98765 43210: online store
09876543210: last bulk import

+919876543210 one customer

What Dispatch actually does

It sits between the systems you already sell on and the tool you already message from. It doesn't replace either one.

Everything arrives in one place

Sales from the counter, orders from your online store, and the years of history sitting in spreadsheets all land on the same profile. One place to look, instead of one export per system and a person to reconcile them.

The same person stops being four people

Every number is read as a number, not as text — so +91 98765 43210, 09876543210 and 9876543210 are one customer. The phone leads, because that's what a counter actually captures; an email rarely is.

You act on the merged list

Pull out the list you need — everyone worth messaging, everyone who just bought and shouldn't be, your best customers by combined spend — already formatted for the tool you'll upload it to. And every action is written down, so you can check it.

Fast to stand up, and shaped to fit — a new sales source is a small addition rather than a project, and the rules that decide who gets left out are yours to set. If your setup is unusual, tell us what it is and we'll say honestly whether it fits today.

What you get

Everything below is running today, except where it says otherwise. We'd rather mark something unfinished than have you find out later.

One profile per customer

Counter sales, online orders and imported history merge onto a single record as they arrive — not in an overnight batch you have to wait for.

Matched on the number, not the spelling

Country code, leading zero, spaces, bare ten digits — every written form of a mobile number resolves to the same customer. This is the single most common cause of duplicates.

Every match is on the record

A logged entry for each event — what came in, which customer it matched, what it matched on, and what happened next. You can check the system's work instead of trusting it.

Spend from both sides, added up

What someone spends in the shop and what they spend online become one number. Your best customers are usually not the ones either system shows on its own.

Customers who've gone quiet

Anyone who's stopped buying gets flagged, and un-flagged the moment they come back — through either channel, so a return visit to the shop counts.

Leave out whoever just bought

Someone who walked in and bought this morning shouldn't get the cart-recovery message this afternoon. They're marked, and kept out of the list you pull.

Lists your messaging tool will accept

Download your contacts, your suppression list, your top spenders or your lapsed customers — with the columns already in the shape your tool expects, so there's no reshaping by hand.

Years of history, brought in at once

Upload past orders in bulk and watch them merge into the same graph, with live progress and a count of anything that didn't parse. Your history is where the good customers are.

Sending straight into your messaging tool

Coming soon

Today the handoff is a file you download and upload. Writing the list into your messaging tool directly is next — the lists themselves already work.

See it on a business like yours

Each of these is a scenario you can click through end to end — the event arrives, the customer resolves, the rule fires. Worked examples on invented data, so you can see the mechanism before handing over anything of your own.

Apparel & fashion

Cart abandoned online, bought in the shop two hours later — and the recovery message gets called off before it sends.

Jewellery & high-value retail

A bridal enquiry with no purchase in five days, from someone who's spent before — so a person calls, instead of a broadcast going out.

Specialty coffee & cafés

Regulars who visit three times a month but have never subscribed, and launch broadcasts filtered to the PIN codes around a new outlet.

Beauty & skincare

A 60-day serum bought in-store, browsed again on day 45 — restock timing worked out from what they actually bought, not a guess.

Fitness studios & gyms

Fourteen days without a class booking, checked against what they still spend in the online shop before anyone nudges them.

Pet care & specialty pet

Puppy food bought at the counter, the dog's age worked out from the purchase history, and the transition to adult food timed off it.

Or start with the mechanics

Identity unification and the win-back loop on their own, without an industry wrapped around them — including the duplicate resolver collapsing three written forms of one mobile number into a single customer.

These run on invented data, and they say so on the page. For a number from your own file, use the audit below.

How many of your customers are in your list twice?

Before any of the above matters, it's worth knowing the size of the problem in your own data. Three steps, nothing to install, nothing to connect. You need two files you already have.

Step 1 — Bring your two lists

A customer export from your billing or POS software, and one from your online store. Any CSV with a phone number column works — you don't have to connect anything or match the columns up yourself.

Step 2 — Numbers get matched, not text

Dispatch reads every number to what it actually is, so +91 98765 43210, 09876543210 and 9876543210 stop being three customers. Phone, because that's what a counter captures — an email rarely is.

Step 3 — See what it's costing you

You get the count of customers appearing more than once, the duplicate groups themselves so you can check them, and a cleaned list to download. Multiply the duplicates by your own per-message rate and you have the number.

Check your own list

Runs entirely in your browser — your customer file is never uploaded and Dispatch never sees it.

Your setup probably isn't the standard one

Most businesses we talk to bill on one thing, sell online on another, message on a third, and have a fourth that nobody wants to talk about. Dispatch is built to be shaped around that rather than to insist on a particular stack.

Where the data comes from

Sales come in through one general-purpose entry point rather than a separate integration per vendor, so adding the system you actually bill on is a small piece of work, not a rebuild. A limited set is connected today — ask about yours.

What counts as a customer

Who gets left out of a broadcast, how long counts as gone quiet, what makes someone worth a phone call rather than a message — those are rules, and they can be written to match how you actually run things.

What comes out the other end

Lists come out in the column layout your messaging tool expects. Several common ones are already built in; a new one is a preset, not a project.

If you're not sure whether your setup fits, ask. We'll tell you straight whether it's possible today, possible with work, or not something we do — a wasted call costs us more than it costs you.

Tell us how you sell

What you bill with at the counter, what you run online, and how you message customers. If you've run the audit, tell us what number came back — that's the most useful first sentence you can send us.

We'll come back on whether Dispatch fits your setup as it stands, and what it would take if it doesn't.

Questions people ask first

What is Dispatch?: Dispatch is a customer data platform (CDP) for retail businesses that sell both in person and online. It performs identity resolution across those channels — matching records to the same real person, phone number first — and keeps a single unified profile per customer that your marketing, suppression and win-back lists are then built from.
How is this different from the messaging tool I already use?: Your messaging tool sends. It takes the list you give it and messages everyone on it, including the same customer three times if they're on it three times. Dispatch sits underneath and decides who should be on the list in the first place. It isn't a replacement for your messaging tool — it feeds it.
Do I have to connect anything to try it?: No. The duplicate audit takes two CSV exports you already have and runs entirely in your browser, with no account and no integration. The demos need nothing at all. Connecting your live systems is a later conversation, after you know the number is worth it.
Does my customer data leave my computer?: Not for the audit — the file is read in your browser and never uploaded, so there's nothing for us to store, retain or delete. The live product is different by definition: it stores the customer records it merges, and that's covered in our Privacy Policy under the Digital Personal Data Protection Act.
Which billing software and storefronts do you support?: A limited set today, and we'd rather name them on a call than overstate it here. Sales arrive through one general-purpose entry point rather than a separate integration per vendor, so adding a new source is a contained piece of work. Tell us what you bill on and we'll answer directly.
Can the rules be changed to match how we work?: Yes — who's excluded from a broadcast, how long counts as inactive, what makes a customer worth a call rather than a message, and the column layout your exported lists come out in. That's the part we expect to fit to each business.
How long does it take to get running?: The audit gives you a number in a couple of minutes. Beyond that it depends entirely on what you sell on — which is why we ask before quoting a timeline. What we won't do is describe it as a months-long integration, because it shouldn't be one.