Intercom · Product sense · Mid · 45 to 60 minutes

How should Intercom rate support conversations?

Intercom makes messaging software that helps businesses talk with customers for support, sales, and onboarding. Answer this product management case and get it graded line by line against a weighted rubric.

product sense
user empathy
trade-off analysis
metrics thinking
written communication

The situation

Your GM for Respond asks you to propose a simple way for support teams to measure conversation quality inside Intercom. Today customers can see volume and speed metrics, but many support managers say that does not tell them whether their team is actually helping people well. As these teams grow, that gap becomes more painful, and some competitors already offer satisfaction widgets, so sales and customer success want Intercom to close the gap soon. The challenge is that Intercom's messenger reaches end users around the world, and support conversations feel personal and human. Whatever you ship may be used by managers to coach teams and assess individual performance, so unclear data could create bad incentives. A quick copy of a common pattern might be easy to launch, but it could produce ratings that users interpret differently, results that managers cannot act on, or an experience that feels clunky in a natural messaging product. Recommend what Intercom should ask at the end of a closed conversation, how users should respond, what information should be captured for managers, and how you would validate the design before a broad launch.

What to produce

Write a 1 to 2 page product recommendation memo.

Your answer must

State the primary user problem and distinguish it from broader company or product satisfaction.
Recommend the end of conversation rating design, including the prompt, response scale, and whether users can leave comments.
Compare at least two credible alternatives and explain trade-offs for end users and support managers.
Define the key success metrics and a validation plan for testing the design before broad rollout.
Call out major risks, misuse cases, and how the output should and should not be used in teammate evaluation.

Constraints

The experience must feel lightweight and natural inside Intercom's messaging product.
The scale should be interpretable consistently by a global audience.
Managers must be able to understand the results quickly and use them for coaching.
Do not assume a long survey, a heavy new analytics platform, or a major workflow change for support teams.

Format

Use short sections with clear headings, and include a small comparison table for options if helpful.

How Intercom actually played it

Intercom wanted a simple way for teams to measure support quality, and what looked like a small feature request hid a lot of complexity. The post explains why emoji ratings were chosen over stars, citing global clarity and a response rate lift. A clear example of product principles guiding a design decision.

Seemingly trivial requests can hide large complexity.
Pick a scale users around the world read the same way.
Make the result easy to interpret at a glance.

Built from Product principles: emoji and conversation ratings by Michelle Fitzpatrick.