A signal, not a request
The thing about a Story reaction is that it isn’t a customer service event. Nobody’s asking a question or waiting for a reply. A 🔥 emoji on your Story isn’t a request for action.
But it also isn’t nothing. A real customer just looked at your content and chose to respond in the smallest way available. Usually that means they liked it; occasionally it’s the opposite — a 😕 to a shipping update is a small but real complaint. Either way it’s data about them, your content, and your brand.
The mistake every shared inbox tool we’d looked at made was to treat reactions like either questions (drop them into the main inbox) or noise (filter them away). Both answers throw something away. The first throws away your team’s attention. The second throws away the customer’s signal.
Why putting them in the main inbox is wrong
Drop reactions into the main inbox and one good Story buries everything else: hundreds of unread items, a handful of which are real customer messages, and the team’s first job of the morning is finding them.
The cost isn’t just the time spent scrolling — it’s having to triage at all. Real questions get missed, real customers wait, and the team starts treating the inbox like something to bounce off rather than work through.
This is the version of the problem that exists at scale — a popular Story, a viral post, a launch day — but it shows up at smaller scales too. Ten reactions versus two questions still drowns the questions enough to slow you down. The presence of low-information signal in a high-information surface degrades the surface.
Why deleting them is wrong
The other obvious answer is to drop reactions entirely. Filter them out at the webhook. Pretend they never came in. A lot of inbox tools effectively do this — they just don’t surface reactions at all.
But that throws away a real customer signal. The follower who reacts to three Stories in a row this week is telling you something. The repeat reactor in the run-up to a launch is probably interested. The 😕 on a delivery update is a small but real complaint. None of those are urgent, and none of them belong in your main inbox. All of them are useful if you can see them.
The third answer
So we built a third place. Pure emoji reactions to Stories — the ones with no accompanying text — route into their own tab. They’re still received. They’re still attributed to a customer. They’re still rehosted and persisted, so the profile picture doesn’t 404 a week later. They just don’t live in the main inbox.
The main inbox stays clean. Real conversations — questions, complaints, enquiries, follow-ups, Story replies with actual text in them — show up where the team is looking. Reactions are always one click away, ready to be skimmed when the team has the bandwidth.
In code, this is a single flag: igIsStoryReaction. In product terms, it’s the design choice that most defines how Vidual Inbox feels on a busy Story day. We had two obvious answers and chose the third.
What teams started doing with it
This is the part we didn’t plan for. We built the Reactions tab to keep the main inbox tidy. What surprised us was how brands started using the tab itself.
It turned out to be a sales surface. The customer who reacted to three Stories in a row? Worth a friendly “hey, glad you’re enjoying the collection — want me to send you anything?” DM. The repeat reactor on a product launch? Probably ready to buy. The follower who went quiet for two months and just reacted to a comeback post? An opening to re-engage. None of those are customer-service moves. They’re the old shopkeeper’s instinct to remember the person who keeps glancing in the window.
It’s the same logic as our Up Ahead feature, just on a different channel: a reaction that gets noticed is worth more than a hundred that don’t.
What we still get wrong
We treat all reactions the same. A 🔥 and a 😕 land in the same tab, with the same weight, sorted the same way. Functionally, that’s a limitation. A negative reaction probably deserves to bubble up; a positive one can sit until you’re browsing.
We’ve gone back and forth on whether to fix this. The risk is over-engineering — building a sentiment-classification layer that’s wrong twenty per cent of the time and then quietly hiding messages because the model misread an ironic 😂. The current version is honest about what it is: every reaction, in one place, sorted by recency. We’ll probably add some sort of priority cue eventually. We’d rather take the time to get it right than ship something clever that erodes trust.
Why this matters more than it should
The Reactions tab is a small feature. It barely shows up in our feature list. We don’t put it on the home page. But the design choice behind it — that a small customer signal isn’t a ticket and isn’t noise, and so it deserves its own place — defines a lot about how Vidual Inbox feels on a busy Story day.
Most of the design choices we’re proudest of are like this — not the big features, but the small decisions that decide whether a tool earns the team’s trust or loses it. There’s a longer piece about the other small details if that’s the kind of thing you read journals for.
If you’re a small brand whose customer service runs across email and Instagram, and you’ve been wondering whether there’s a shared inbox tool that thinks about IG the way you do — have a look. The trial is fourteen days, no card required, every feature in from day one.
Vidual Inbox is available now at vidualinbox.com. 14-day free trial, no credit card required. £24.99/month after that, every feature, every team member.