Event-triggered research message with two questions
Ask for feedback immediately after the user does the relevant thing, and keep the message to one or two direct questions.
Why this can grow a startup
Research messages get vague when they are sent long after the behavior or padded with survey language. Intercom's cheat sheet is useful because it turns the message into a small operating pattern: send it right after the event, know the decision you are trying to make, define the audience tightly, and keep the ask short enough that a busy user can answer without opening a separate form. That raises the odds of getting usable detail instead of polite noise.
Source-backed example
Intercom's research-message cheat sheet says to ask right after the customer has done something or visited somewhere in the product and to keep the prompt to ideally one but no more than two questions.
Source-reported evidence
Source: Intercom Blog PDF: Research Message Cheat Sheet
Intercom recommends one or at most two questions in the message, with a survey used only when more is needed.
Attributed to the cited source; GrowthDex has not independently verified it. Use this as context, not as a forecast, benchmark, or recommended target.
Evidence scope: claims and metrics are attributed to the linked source; GrowthDex has not independently replicated the reported result. Check the original context and validate fit before applying it. Read the evidence methodology.
Source discovered: May 30, 2026
When to use it
Use this when Research, Lifecycle Messaging, Product is relevant to user research, feedback timing, activation and you can run a bounded test with a free budget.
When not to use it
Do not use it as a substitute for customer evidence, a clear owner, or a measurable stop condition. Local platform rules and market behavior still need checking.
How to do it
- Choose one target segment and define the exact next action this tactic should prompt.
- Adapt the tactic to Research and Lifecycle Messaging, using evidence from Intercom Blog PDF: Research Message Cheat Sheet as context—not as a promised result.
- Record a baseline for: Share of target users completing the product's first-value action. Set a guardrail that would make you pause the test.
- Run a narrow pilot and choose a test window that fits the normal decision or use cycle; do not scale before you have observed the full cycle.
- Compare the signal with its baseline. Scale only if the intended action improves without crossing the guardrail; otherwise revise one variable or stop and record what you learned.
Compare a stack for your situation
Compare source-backed tactics against your product, stage, budget and channel strengths, then choose one experiment to test.
Explore the context
Did you launch this experiment?
Report a launch to help us understand which growth ideas founders put into practice.
Apply this with an operator
Build creator and community systems around real incentives, trust, and repeat participation.