Feedback Channel

Customer comments never arrived in one place. Questions piled up in a support inbox, two-star reviews appeared in the app store, a salesperson wrote complaints from a meeting into a notebook, and in community forums people criticized the product without the company knowing at all. Everyone saw only what landed in front of them, so nobody saw the whole.

Meetings kept stalling at the same point. Somebody would say customers find search awkward, somebody else would ask how many said so, and there was no answer. Support had three such tickets, sales had heard it twice in last month's meetings, and something similar sat in the app reviews, but nobody had ever put the three side by side and added them up. With no number to offer, whoever spoke loudest became the decision.

The word channel came about to handle that scattering. Instead of lumping customer comments together, each entry point gets a name and gets counted separately. That makes it visible how much arrives at each doorway and which doorway is blocked — and above all, it makes it visible that a different kind of person speaks at each one.

For a channel to actually run, three things have to be settled. Miss one and the doorway is merely open: it carries nothing.

1. The entry point — where the customer leaves the comment. It might be a support email address, or a feedback button tucked into a corner of a product screen. It has to sit somewhere customers can find, and cost little effort to use.
2. The store — where what arrives piles up. One person's inbox or private notes is not a store. When that person takes a holiday nobody can see it, and at quarter end it can't be found to count.
3. The owner and the cadence — who opens that store, and when. Support tickets get read daily, app store reviews get scanned weekly, survey free-text gets read in one batch each quarter. Each channel gets its own rhythm.

A record in the store holds five things per row: the customer's own words, the date it arrived, which channel it came through, which customer it was, and whether they are on a free or paid plan. The field people get wrong is the first one. If whoever transcribes it shortens the entry to "search complaint," two months later nobody can tell whether the customer meant the results were wrong or that they couldn't find the search box. Paste the customer's sentence as written.

The payoff of separating channels shows up once you count. "Twenty comments about search this quarter" says less than "eighteen of them were support tickets and two were survey responses." Support tickets are written by people blocked right now and angry about it, so those eighteen point at something urgent.

Even one company usually has five or six channels open at once. Here are the common ones, and who turns up at each doorway.

1. Support ticket — a queue where each inquiry gets its own number. People who are stuck right now and need an answer come here. Complaints arrive at their rawest, but the customer is already angry, so the tone runs hot and they describe symptoms rather than causes.
2. In-product feedback button — an input box placed on the screen itself. Thoughts that occur mid-use land immediately, and which screen they were left on gets recorded along with them. The trade-off is that most entries run one or two sentences, so context is thin.
3. Survey free-text — the open field at the end of a survey such as Net Promoter Score (NPS) or customer satisfaction score (CSAT). It comes with the reason behind a score attached, which makes it easy to work with. But the people who answer are the ones with enough slack to answer a survey, which skews toward customers getting along fine.
4. Sales and customer success notes — what was heard in a meeting, written down. Comments from people who aren't customers yet mix with requirements from a company about to sign a large contract. Words spoken where the money is large carry weight easily, and whether that one person represents anyone else has to be checked separately.
5. App store reviews and community posts — records of someone talking to other users instead of to the company. This is where people who expect nothing from the company leave their comments. They never intended to file a ticket, so complaints often appear here that exist nowhere in support.

"Which channel did this request come in through?"

A question about who was speaking. A support ticket means an existing customer; a sales note might mean someone still pre-contract.

"We opened the in-app feedback channel two months ago and nobody has pressed it yet."

The doorway is open but customers aren't finding it, so it's time to revisit the button's placement or its wording.

"We haven't been counting app reviews as a channel. Let's include them from this quarter."

A proposal to bring a previously uncounted doorway into the tally.

At Pagedeck, Mia looks at volume per channel first each quarter. Support tickets suddenly doubling is a signal that something happened to the product, and a channel that stays empty means the doorway is broken or sits where nobody looks.

What Sofia brings back from sales meetings gets marked separately by Mia. Requirements raised where a contract is large carry weight in a meeting, and until the same requirement turns up in support or a survey it may be one company's situation. Last quarter's request for permission settings, for instance, appeared three times in meeting notes and in no other channel at all.

It's easy to assume more channels are better, since more doorways ought to bring in more comments. But every channel needs an owner and a cadence attached, and while opening one is cheap, reading it costs effort forever. Six months on there's a doorway nobody answers, and the customers who left comments there learn that this company takes but does not reply. A dried-up channel is worse than one that never existed. Three channels with all three read beats ten with three read.

Reading what arrives as the opinion of all customers is the other common mistake. When twenty people say the same thing it's tempting to read it as how everyone feels. But the people who leave comments in a channel are either very angry or very attached, and most customers just put up with an annoyance and carry on. Ignore that gap and the product moves to follow the vocal minority while the quiet majority leaves one day without a word. Use channel records to find out what the problem is, and check how widespread it is with something that measures everyone, such as usage metrics or a survey.