Stories in progress — told the way we count
Comver publishes a result only when it is counted from a store’s own orders and the brand agrees to be named. Until then, here is what a rollout looks like: three anonymised, illustrative playbooks with the modules and agents used and the metrics Comver would count. No invented customers. No invented numbers.
What a rollout looks like
Illustrative playbookWhat Comver would count
Dashes stay dashes until a store has run it. We publish results only when they are counted and the brand agrees.
Four rules before a story is published
They are the same rules the product follows on every screen — which is why the case-studies page is the last page on this site to fill up, not the first.
Counted, never modelled
A published result is attributed revenue from real orders — by discount code, by cart token, or because an order followed a Callio message. Estimates stay marked ≈ and never become headlines.
The window is stated
Before-and-after figures come with the period, the traffic and the confidence they were measured at. An A/B winner below ~100 sessions per variant is “low confidence” and is not a winner.
Named with permission
Brands are named only when they agree, with the modules and campaigns they actually ran. Until then playbooks are anonymised and labelled illustrative.
Nothing borrowed
No competitor benchmarks dressed as your numbers, no demo datasets presented as a store, no reference-store proof reused as a customer story.
Routines, replenishment and the shoppers who left
An illustrative skincare brand whose product pages sell single serums while the margin lives in routines. The rollout starts with a read-only scan, switches on the modules that turn a serum into a routine, and points Callio at the two moments the store already loses: an abandoned checkout and a VIP who has gone quiet.
- Week 1 — connect the app, run the scan, read the CRO score and the ranked action plan
- Week 2 — Bundling & Upsells and Subscribe & Reward live under add to cart; reviews imported into Trust AI
- Week 3 — buy a local number, verify the sending domain, switch on Abandoned order; Cart Rewards added
- Week 4 — VIP follow-up on the Slipping-away column; template A/B on the bestseller; read the call log
Beauty DTC brand
Skincare · routines · replenishment · illustrative store
Revenue modules
Configured in Comver, not the theme editor
Agents on the store
Working the same customer and behaviour data
First campaign · Abandoned order
Wait 20 min · call first, text when the call cannot connect, email when the phone cannot reach
What Comver would count
starts at — · never modelledTurn a repeat purchase into a subscription — and call the ones who lapse
An illustrative supplements brand with a natural 30 / 60 / 90-day cadence and a customer base that reorders by hand. The playbook leans on Subscribe & Reward for the cadence, Sticky ATC and stack bundles for the first order, and Callio for the returning customer who is browsing again without buying.
- Week 1 — connect, scan, sync customers; Copilot’s daily brief on from day one
- Week 2 — routine builder with 30 / 60 / 90-day plans (native Shopify selling plans); Sticky ATC and bundles live
- Week 3 — Known customer looking again switched on: call first, text, email; popups for Subscription Candidates
- Week 4 — VIP customer follow-up on the pipeline; Trust AI summaries with disclosure on the product page
Supplements brand
Daily formulas · 30 / 60 / 90-day cadence · illustrative store
Revenue modules
Configured in Comver, not the theme editor
Agents on the store
Working the same customer and behaviour data
First campaign · Known customer looking again
Wait 1 h · call first, text when the call cannot connect, email when the phone cannot reach
What Comver would count
starts at — · never modelledDrops, deals and a cart that earns its milestones
An illustrative apparel brand with seasonal drops, a large newsletter list and a cart that leaks at delivery cost. The playbook builds the cart drawer around reward milestones, fills the deals drawer only from real compare-at products, and lets Callio phone the newsletter clickers who did not order.
- Week 1 — connect, scan, Behaviour embed on; funnels and heatmaps start filling with real visits
- Week 2 — Cart Rewards with milestones and delivery urgency; Sticky ATC; photo reviews in Trust AI
- Week 3 — Offers & Rewards deals drawer (collect three, unlock a real code); Abandoned order switched on
- Week 4 — newsletter from the store’s own domain; Newsletter click without an order calls one hour later
Fashion brand
Apparel · drops · seasonal offers · illustrative store
Revenue modules
Configured in Comver, not the theme editor
Agents on the store
Working the same customer and behaviour data
First campaign · Abandoned order
Wait 20 min · call first, text when the call cannot connect, email when the phone cannot reach
What Comver would count
starts at — · never modelledFour weeks from install to a number you can trust
Different verticals, the same order of operations — because the order is what keeps the numbers honest.
- 1
Connect and scan
One Shopify app, the app embed switched on, a read-only scan in 60–90 seconds. The CRO score and the action plan set the priorities; nothing is applied to the store.
- 2
Switch on the storefront
The revenue modules the vertical needs, configured in Comver — not the theme editor — with one Style skin. Attribution by discount code or cart token starts at the first order.
- 3
Give Callio a voice
A local, mobile or toll-free number bought inside Comver, a sending domain verified with DNS, and the first campaign — with what it is worth shown as ≈ before it runs.
- 4
Read the log, count
Runs, answered, messages and attributed revenue per campaign; every call with recording and outcome; every module with the orders it earned. Dashes stay dashes until then.
Four marks, and what each one means
When a launch partner agrees to be named, the story will show exactly these figures — from their own store, with the window stated.
$
Attributed revenue
From Callio: orders that followed an email or text · From modules: by code or cart token
≈
What was estimated first
The recoverable figure the store saw before switching a campaign on — kept for comparison, never added in
—
Until it has run
Anything not yet measured is a dash, not a plausible number
0
Borrowed numbers
No benchmarks, demo datasets or reference-store proof presented as a customer’s result
Typical uplift ranges shown in the product (for example +8–20% AOV for Bundling & Upsells) are labelled “typical, not measured” and are never quoted as a customer’s outcome.
Be one of the stores these stories are about
A small number of Shopify brands roll out with the team beside them: the scan read together, the modules and the first Callio campaign configured with you, and every number counted from your own orders. You decide afterwards whether the story is published — and under which name.
Hands-on rollout
Connect, scan, modules, number and domain, first campaign — configured with the team, in the order above.
Your numbers, counted
Attributed revenue by code, cart token or a Callio message; estimates stay marked ≈; nothing blended.
Your call on publishing
Named, anonymised, or not at all — and only the modules and campaigns you actually ran.
Write the first counted story with us
Install Comver, connect your store and switch on the first campaign. When the numbers are in — and only then — we will tell it the way we count.
14-day free trial · Live on Shopify in minutes · Checkout stays in Shopify