A voice-of-the-customer program reaches the people who already bought, and the product decision depends on the people who bought something else. Sena reads the stated want across the whole category, market by market, beside what those buyers took home.
A voice-of-the-customer program collects what people say about a product and routes it to the teams that can act. Three patterns keep the collected want narrower than the decision it feeds.
The reachable population is the customer list, the support queue, and the review page. Everyone in it has already chosen the product, so the population is favorable by construction.
Most collection happens once the product has shipped and money has moved. That timing answers how the product performed and leaves the question of what to build next open.
A single questionnaire runs across countries, translated and otherwise unchanged. The attribute deciding the choice differs enough between markets to change which product wins.
Sena is the decision AI with access to real-world data. It reaches category buyers across 190+ countries, including the ones buying a rival today, so the stated want covers the population the product competes for.
Sena reaches people buying the category now, whoever they buy from, and records what each of them states they want.
Every stated want sits beside a dated purchase from the same people, so preference reads against action.
Buyers state which attribute decided the choice and what would move them, in their own words.
Voice of the customer is the practice of collecting what people want from a product and feeding it into what the team builds. The practice is well established. Where it lands depends on who was reached and when.
The voice of the customer gathers stated preference, complaint, praise, and request into a ranked account of what people want from a product, then routes that account to the teams who set the roadmap, the pack, and the claim.
| Reading | Who gets reached | What it answers |
|---|---|---|
| Customer voice | People who bought this product. | How the product performed, and what to fix. |
| Category voice | Everyone buying the category, per market. | What to build, and which attribute decides the choice. |
The first reading is the established one, served by customer-experience platforms and measured through satisfaction and recommendation scores. The second is what a product decision runs on, because the buyer who has yet to choose the product holds the answer to what would make them.
Analysis turns collected statements into a ranking the roadmap can use. Four steps carry it, applied per market.
List every product a buyer in that market would weigh alongside this one. Who counts as a category buyer follows from that list, and every ranking below inherits it.
Include buyers of every product inside it, current, rival, and lapsed. A ranking drawn from one product's customers describes that product's customers.
Ask which attribute decided the last purchase and which would change the next one, then rank by market, holding the global total aside.
Set each stated want beside the dated purchase from the same people. Where the two disagree, the disagreement is the result.
The process runs on a cycle, and the cycle length follows the product decision it feeds.
| Stage | The question | The evidence that settles it |
|---|---|---|
| Define | Which category, which markets. | The products a buyer weighs, per market. |
| Reach | Who states the want. | Category buyers across the boundary, rival buyers included. |
| Collect | What decides the choice. | Ranked attributes, plus dated purchase from the same people. |
| Rank | Which want leads here. | The ranking per market, held apart from the global total. |
| Act | What changes in the product. | The concept, pack, format or claim the ranking points at. |
| Recheck | Did the change land. | Recorded purchase and repeat after the change shipped. |
Four collected inputs build the ranked want, applied per market.
| Input | What it answers |
|---|---|
| Stated preference | Which attribute decided the last purchase, and what would change the next one. |
| Receipts | What the same people took home, dated, so preference reads against action. |
| Store captures | Which products sat in the outlet on the day, so a stated want reads against availability. |
| Geo-verified photos | The outlet as it stood, with the market and date attached. |
The team's own numbers form a separate row. Support tickets, review exports, satisfaction scores, and product records join through 250+ integrations, so the customer reading and the category reading sit in one place.
Four questions sit outside a satisfaction program, and each one changes a product decision. The rival's buyers are the growth, and a customer questionnaire structurally excludes them. A global ranking averages eight markets into one answer, and each of the eight sits at a distance from it.
A stated preference and a dated purchase from the same person read together, or they read as two separate claims. And the buyer who would move states the condition, only if asked before moving.
Sena reads the category, and a customer-experience program is a separate job. Satisfaction and recommendation scoring, ticket routing, in-product prompts, closed-loop follow-up, and account health scoring belong to the customer-experience platforms built for them. Sena adds the population those platforms leave open: the category buyers who chose something else, per market, with dated purchase beside every statement. The two read together in a roadmap conversation.
Real people share what they buy and prefer, under explicit consent. Sena captures it directly at the source, so every figure traces back to where it came from whenever a number comes under question.
Consented purchase and stated preference arrive from the same people, and every statement carries the market and the day it was given.
Buyers rank the attribute that decided the choice, so a ranking reaches the roadmap where an opinion is used.
Every stated want sits beside a dated purchase from the same people, so preference and action read together.
The ranking holds per market, so a global average stays out of the market being decided.
Most rankings in a roadmap review come from people who already bought. Sena collects from real-world signals captured when the question needs it, from a buyer ranking an attribute through to the receipt showing what they took home.
Records the purchase each buyer made inside the category, so a stated want reads against that person's own receipt.
Reads which products sat in each outlet off images captured in real stores, so a want reads against what was available to choose.
Signal arrives from the consumer network under explicit consent. The attribute a buyer ranked first comes from that buyer.
Support records, review exports, satisfaction scores, and product data join over 250+ integrations, so both readings of the term sit together.
Every statement holds its market, its segment, and the day it was given, so a roadmap claim opens back onto the buyer who gave it.
Sena sets historic questionnaire exports, ticket archives, and stated preference records beside the market they came from, covering every cycle the product has run.
Four teams read the same ranked want, and each one needs a different cut of it before they can act.
The roadmap. Needs the attribute ranked first by category buyers, per market.
The claim. Needs the driver that decided the last purchase in that market.
The next product. Needs the want stated by buyers of every rival inside the boundary.
The program. Needs the category reading beside its own satisfaction record.
The same ranked read, put in the attribute each category actually competes on.
Which pack, format, and price the category buyer ranked first, per market.
Which specification decided the last purchase, and what would move the next one.
Which pack size and claim the counter buyer asked for, market by market.
Which plan attribute ranked first among buyers holding a rival handset.
One mechanism, applied per market and per category. Each step is documented, which is what carries a ranked want through a roadmap review.
Real contributors buying the category across the markets named rank the attribute that decided their last purchase and record the receipt behind it under explicit consent.
Sena orders the stated attributes per market and per segment and sets each ranking beside the dated purchase from the same people.
Current buyers, rival buyers, and lapsed buyers read against each other, so the growth population shows up separately.
Most voice-of-the-customer work reaches a reachable population and measures how it feels about a product it already owns. Sena reaches the category and records what it did.
| Capability area | Typical setup | Sena |
|---|---|---|
| Who gets reached | The customer list and the support queue. | Category buyers across 190+ countries, including rival buyers. |
| When the want is collected | After the purchase. | Before the next one, with the last one dated. |
| What the output is | A satisfaction score and a theme list. | A ranked attribute set, per market and segment. |
| Preference against action | Two separate records. | One population, so both read together. |
| Market resolution | One translated program. | A ranking held per market. |
| The growing population | Outside the frame. | Buyers of every rival inside the category boundary. |
| Evidence in a review | An aggregate score. | Open any figure onto the statements and receipts underneath. |
Three situations where the category reading decides a product question the customer reading leaves open.
Rank the attributes category buyers state across the markets in scope, and take the ranking into the concept slot ahead of an internal preference.
Lead with the attribute buyers in that market ranked first, and hold the global ranking aside while doing it.
Reach buyers who moved to a rival, record the attribute that decided it, and set that beside the purchase they made.
A ranked want opens the roadmap question. The four decisions below are what a product team asks around it.
Every product decision Sena answers, in one place
The want supply leaves open
Takes the stated want and finds where supply in that market sits absent.
Explore market gap analysis 02Against the real alternative
Reads this product against the specific alternative a buyer in that market weighs.
Explore competitive product analysis 03Which launch to run
Chooses the launch type and the market order once the want is ranked.
Explore product launch strategy 04How it performed after
Reads what the market did with the product once the ranked want shipped.
Explore product analyticsThe remaining decisions
The walkthrough takes one category in one market, reaches buyers of every product inside it, and ranks the attribute that decided the last purchase while the team watches.
Tell us the category and the market, and we will rank the want.