The same upsell or question can help or annoy depending on when it appears. On this site contextual timing covers in-context upsells (premium themes marked inside a picker you're already using, a guest-to-member upgrade naming the colleague you just worked with), cross-sells in quiet moments, and the failures: a feedback survey covering a dashboard before you've seen it, or a demo offered only after setup is done.
Research on interruptions shows timing changes the cost. Piotr Adamczyk and Brian Bailey (CHI 2004) found that interruptions at better moments within a task, such as between subtasks, led to less annoyance and frustration than those at worse moments. Shamsi Iqbal and Bailey (CHI 2008) found that holding notifications until natural breakpoints reduced frustration and reaction time compared with delivering them right away. NN/g's Maria Rosala applies this to permissions: requests triggered by a related action are less surprising than prompts at launch.
For growth teams the practical rule is that an offer converts best right after the user hits the need it solves, and costs the most goodwill when it interrupts the task that would create that need.
How to use it
- Trigger upgrades from the moment of need: a limit reached, a locked feature tapped, a collaborator invited.
- Ask for feedback or ratings after the user has seen the result, at a task boundary, not on first render.
- Offer shortcuts like demo data or templates at the first step, before setup effort is spent.
Watch out
- Firing offers at every possible trigger turns relevance into nagging.
- Interrupting a task in progress, for example a modal over content that is still loading, reads as the product caring more about the sale than the user.
