One engine from customer data to proven revenue.
Unify, segment, engage, track and grow — in one product that works the same for consumer brands and distribution networks. Only the data labels change.
Start from the data that actually records a sale
Not app events or pixels — receipts and invoices. PulseIQ joins your customer master to receipt-level purchases and your store and product masters, refreshed nightly with a visible run history.
Customer master
Every column becomes a segment field automatically — text, numbers and dates.
Receipts or invoices
POS receipts, delivery-app orders, own-app orders or secondary-sales invoices.
Store master
Outlet, city and outlet type — or distributor, city, distributor type and beat.
Product master
Category, sub-category, item and attributes, so codes read as names.
Audiences built on what people bought
Combine customer fields with purchase behaviour in any window, group rules with AND / OR, and exclude anyone who did — or didn’t — do something.
- Readable — every segment reads back in plain English, with every campaign that uses it.
- Inspectable — open any customer in Customer 360, codes mapped to names.
- Private — phone numbers are masked to the last four digits on screen and in exports.
Every building block of a segment
| Building block | Options |
|---|---|
| Text fields | is · is not · contains · is any of · not any of · is set · is not set |
| Number fields | equals · greater than · less than · between |
| Date fields | in the last N days · exactly N days ago · on or before · on or after · between |
| Purchase measure | made a purchase · number of visits · total spend · single receipt amount · average order value |
| What was bought | any product · category · sub-category · specific items · product attributes (e.g. veg / non-veg, premium / mass) |
| Where and how | store · city · store type · sales channel (B2B: distributor · city · distributor type) |
| When | in the last N days · exactly N days ago · on or after · on or before · between two dates · any time |
| Logic | rules AND-ed inside a group · groups joined by AND or OR · exclusion groups joined by AND or OR |
One customer, their whole story
Look up any customer and see everything on one timeline — when they were acquired, every bill with its items, every message and whether they read it, and which messages were followed by an order.
Journey timeline
Bills, WhatsApp and SMS on one timeline, with monthly spend underneath.
Every bill, itemised
Open any bill for its store, channel, covers, line items and offers.
Every message, tracked
Delivered, read or failed — and the order that came after it.
The full profile
Favourites, preferred day and store, recency status and opt-in flags.
Seven guided steps from idea to launch
Basics → audience → message → delivery schedule → test on real phones → suppression and exact final count → review on one page.
- Per-recipient variables — map each placeholder to a customer field with a default, or a fixed value.
- Codes become names — store and item codes turn into readable names in the message.
- Checked before launch — DLT template ids, headers, routes and the WhatsApp catalogue are validated.
Send it once, on a calendar, or on a rhythm
| Mode | What it does |
|---|---|
| Draft | Saved, never sent |
| Send now | One-time, fires on save |
| Scheduled | One-time at a date and time |
| Recurring · calendar | Chosen weekdays × months at a set time, with a stop date |
| Recurring · rhythm | Every N days from a start time |
Guardrails that prevent the expensive mistakes
- Past start times and stop-before-start are blocked.
- Drafts can never fire by accident.
- Overdue runs are parked as “missed” instead of sent late.
- Pause stops a live send at the next batch; interrupted sends resume where they stopped.
- Filter every campaign by status, channel, name, id or tag.
Personal messages, automatic recovery
WhatsApp first, SMS when WhatsApp can’t reach. Channel studios let you build, preview and monitor every template.
- Primary + fallback — when WhatsApp can’t reach a customer, the message goes out on SMS instead. Nobody is double-messaged.
- WhatsApp studio — build templates with buttons and media, preview on a phone, sync your provider’s catalogue.
- Delivery by template — delivered, read and failed with daily trends and the campaigns using it.
- Your providers — the WhatsApp Business provider is switchable, and fallback can be turned on or off per campaign.
Each customer hears from you only as often as you decide
Frequency caps across every campaign, suppression built in, and an exact final count before you press send.
Caps across all campaigns
Each customer hears from you only as often as you decide, however many campaigns are live.
Max N in 7 or 30 days
Plus a minimum gap between messages.
Shadow mode
See how many customers a cap would remove before you switch it on.
Exact final count
Matched, suppressed, over the cap and will-be-sent — before launch.
Seven flags per number
Blacklisted, DND, dummy, internal, and SMS / WhatsApp / RCS subscriber.
TRAI-aware routes
Each SMS template is transactional or promotional, and sent on the right route.
Opt-outs honoured
Blacklist and DND flags apply to every campaign automatically.
Learn from failures
Numbers that keep failing can be marked DND in one click.
DPDP by design
Phone numbers are masked on screen and in every export.
Revenue and ROI for every campaign
Results come from your own sales data. Every campaign gets a deep-dive — sends, delivery, customers who ordered, revenue and ROI against spend — and recurring campaigns are tracked run by run.
- Command centre — reachable customers, active customers and delivery health at a glance.
- Delivery quality — why messages failed, from operator status codes.
- Roll-ups by tag — compare whole programmes: winback, seasonal, launch.
- Download anything — every table view exports, with phone numbers masked.
The whole base by recency, every month
See who is slipping before they are gone — and what each month’s new customers turn out to be worth.
- Recency bands — new, active, 31–90 days, inactive, dormant, deep dormant and lapsed.
- Movement since the 1st — watch the base shift band by band through the month.
- Reach by band — what share of each band you messaged, and actually delivered.
- Acquisition cohorts — revenue, orders or visits per acquired customer by months since acquisition, filterable by city, store type and store.
Nightly data and admin controls
Refresh history
Customer master and receipt roll-up refreshed nightly, with a run log of what changed.
Channel rates
Per-message costs per channel, with history, so ROI reflects what you really pay.
Users and roles
Admins configure; viewers read. Accounts are provisioned by your workspace admin.
Fallback settings
Switch the SMS fallback on or off per campaign.
Exports
Download any table view — with phone numbers masked.
Tags
Group campaigns into programmes and compare them side by side.
Start with one campaign.
In 30 days you will know, in rupees, what your messages earn — and which audiences to message again.