Comparison
Refik and Kustomer, read on the same day.
One of these two prints its prices on a page anyone can open. The other says in its own sentence that it does not, and offers an estimator and then a person who will build a number for your team. That is the first row of the table below and the reason the rest of it looks the way it does — and every row carries the date it was read and the page it came from.
Method
Two sides, two dates, and two different kinds of empty cell.
The right-hand side of every row was read out of Kustomer’s own pages on 10 October 2026 — the home page, the pricing page and a feature page, and nothing else. No analyst report, no review site, no reseller listing. All three pages answered with a page of their own rather than a redirect or an error, so the reader had their text in front of it; the quotes are theirs, word for word. The left-hand side was read out of our own source code on 4 October 2026, and the plan figures come from the pricing page in this same directory, which fails its build if a price in the code changes without the page changing with it.
An empty cell is a third state and it is deliberate. It does not mean “they do not have it”. It means we did not read it on that day, so printing a dash there would turn a gap in our reading into a claim about their product. Every empty cell on this page is named underneath, with the reason it is empty.
And there are two kinds of empty here, which is unusual enough to separate out. Where an amount is missing from the right-hand column, that is a reading: the pricing page states in its own words that it does not post prices, and no currency symbol or figure appeared anywhere in its visible text. Where a trial length or a channel list is missing, that is a gap: those pages simply did not carry it on the day we looked. In a table the two look identical. They are not the same sentence, so each one is labelled below as one or the other.
Two things are absent from this page by design. There is no verdict row and no score: a published band price and a figure quoted after a scoping call are not the same kind of number, and dividing one by the other would produce something that looks like a measurement and is not one. And there is nothing here about how well either assistant answers a shopper, because we did not measure that on either side.
The rows
What each side charges for, and where it runs.
Read the first three rows together. A price you can read before you install and a price that arrives after a conversation put the buying decision in different places: one of them you can make alone at midnight, the other needs someone on the other side to be awake. Everything below those rows is downstream of that.
Kustomer read from kustomer.com, kustomer.com/pricing and a feature page on the same site; Refik read from this repository and the pricing page.
| What the row measures | Refik | Kustomer |
|---|---|---|
| What you are billed for | ||
| The billing unit | Conversations in a billing period. Three bands: 300, 1,000 and 3,000, for the whole shop rather than per person. | No unit is published on the pricing page read that day, and the page gives its own reason: “Every CX team’s setup is different, so we don’t post one-size-fits-all pricing.” |
| Entry tier, list price and currency | Starter, $39 a month or $390 a year. Printed in USD; what a merchant is finally charged in runs through Shopify’s billing, and we did not read that on 4 October. | In the visible text of the pricing page no currency symbol and no figure appeared at all. The word “Custom” appeared eight times. |
| Tiers above the entry one | $99 and $249 a month; $990 and $2,490 a year — the Growth and Premium bands, at 1,000 and 3,000 conversations. | |
| Charges on top of the subscription | On monthly billing, $0.15, $0.12 or $0.10 for a conversation above the band, capped at one band’s worth. On yearly billing, none. | |
| Free trial | 14 days on every plan, with a conversation allowance scaled to the plan. There is no free tier after it. | |
| How you arrive at a number | You read it off a public page before installing anything, and the page is checked against the code that charges you. | “Then we’ll connect you with someone who can build out exact pricing for your team.” |
| What the pricing page does instead | Lists the three bands, what each one covers, and what happens when a shop goes past its band. | It is an estimator. Its own title is “Pricing & ROI Calculator | Kustomer”, and the page says: “Complete this two-minute assessment to estimate: Annual cost savings Estimated ROI & payback period Hours your agents could save AI automation opportunities”. |
| Where it runs | ||
| Platforms it connects to | Shopify only. The catalogue, the policies and the order lookups all come from one store’s Admin API, and there is no second platform anywhere in the code. | Across the visible text of all three pages read that day, “Shopify” appeared no times. All three had answered with a page of their own, so the reader was not looking at an error. |
| Channels a shopper can use | The web storefront, and only that. WhatsApp, Instagram, Messenger, email and SMS are not built, and that is written on the integrations page rather than left to be discovered after payment. | |
| Opening a ticket in the other product | The server can open a ticket in one help desk. Kustomer is not that one, and the settings screen for choosing a target is not built, so a shop running Kustomer cannot wire the handover up from our panel today. | |
| How each side describes itself | A shopping assistant on the storefront: it recommends, it looks up an order, and it hands a hard question to a person. | “Deliver faster, personalized support with Kustomer’s AI customer service CRM. Unify conversations, automate workflows, and power omnichannel CX in one platform.” |
- Tiers above the entry one, their cell is empty — a reading, not a gap. The pricing page publishes no figures at all, so there was no ladder to read off it. Whether one exists above an entry plan is not something those pages told us, and a dash there would turn our silence into a statement about their product.
- Charges on top of the subscription, their cell is empty — a gap. None of the three pages read that day stated a usage charge. That is a gap in our reading and nothing else.
- Free trial, their cell is empty — a gap. The pages read did not carry a trial length. Ours is in the cell because it is on our own pricing page.
- Channels, their cell is empty — a gap, and we declined to fill it. Their channel list was not among the pages read. Their home page calls itself omnichannel in the sentence quoted in the last row, and a word in a marketing sentence is not a channel list, so the cell stays empty instead of being filled from it. Ours is written out because a missing channel is the kind of thing a shop finds out after it has paid.
- Opening a ticket, their cell is empty — a gap. We read nothing on their side about what can push a conversation into their product from outside. Ours is spelled out, shortcoming included, because a shop that already runs a help desk asks that question first.
- One of the three pages is identified only by kind. Our note records the home page and the pricing page by address and the third one only as a feature page. All three returned a page; which feature page it was is not written down, so it is not written here either.
- Neither side’s answer quality is here. Not theirs, not ours. Measuring it would need the same shoppers asking the same questions of both, on a real catalogue, and that has not been done.
The difference that matters
A published price and a quoted price are answers to different questions.
A published price answers: can I work out what this costs me, on my own, right now. It lets a shop compare, forecast a year ahead, and decide without talking to anyone. A quoted price answers a different question: what does this cost given my particular setup. That is a real question, and for a support organisation with several teams, several channels and a volume nobody can guess from outside, it is the more honest one — a single printed figure would be wrong for most of the people reading it.
So the difference is not that one side is hiding something. It is a consequence of scope, and it cuts both ways. We can print three figures because the product is narrow: one platform, one channel, one store’s catalogue and policies. Narrow the inputs enough and a price becomes printable. Widen them — a platform that unifies conversations across channels for a team of agents — and a printed figure stops meaning anything. The cost of that generality is paid by the smallest and most ordinary buyer, who has to spend an assessment and a call to learn a number that a page could have told them.
That is also why the two are not straightforwardly alternatives. A shop whose support arrives through several doors and is answered by several people has a help desk problem, and a storefront assistant does not solve it. A shop whose owner is the only person answering, and whose cost is the same nine questions arriving before anyone decides to buy, has a storefront problem — and a platform built for a team is a lot of product to buy for a queue nobody is standing in.
There is a case where both are true at once, and it is common: a shop already running a help desk that wants the storefront to stop sending it the easy questions. For that case the handover matters more than the price, and here is the honest state of ours. The server can open a ticket in one help desk; Kustomer is not that one; and the settings screen for choosing a target is not built, so the wiring is not something you could set up from our panel today. The integrations page lists what is connected and what is not, in the same words.
Who each one fits
Where we would tell you to buy the other one.
A customer service platform fits you if support arrives through more than one door — email, phone, a social inbox — and more than one person answers it. If you need a shared queue, assignment between agents, one customer record that survives across channels, or reporting that spans all of them, that is its job and not ours. Our channel list is one channel long, and we would rather say so here than have you discover it in week two.
We fit you if the questions that cost you money arrive before the order exists: which of these two is right for me, is this in stock in my size, where is the order I placed on Friday, can I send this back. Those are storefront questions, they arrive on a product page, and answering them needs the catalogue, the stock and the policies of one shop rather than a cross-channel record of a customer.
Buy on a quote rather than a price list if your setup is genuinely unusual — unusual volume, unusual channels, unusual compliance. A printed figure would be wrong for you in both directions, and an assessment that ends in a scoped number is the right shape of answer. If your shop is ordinary, the same process is a cost you pay before you learn anything.
Neither of us fits you if what you actually need is a person. Both products put a human at the end of the path; ours does it by opening a handover and telling the shopper that someone will pick it up, and it is instructed never to say a refund is approved. If there is nobody to pick it up, no assistant on either side of this table fixes that.