Delivery Channels: In-App, Email, CS/Sales—How to Choose and Combine for Maximum Adoption
An overview of different Delivery channels (In-App, Email/Messages, CS/Sales) and their role in delivering value to the user, with practical recommendations on their selection and combination.
Delivery Channels: In-App, Email, CS/Sales—How to Choose and Combine for Maximum Adoption
"Value Delivery" is not just about deploying code to production. It's an active process that ensures the right users not only learn about a new feature but are also able to use it and gain real value. Choosing the right channel for "delivery" plays a key role here.
Within the PTOS framework, there are several main Delivery channels, each with its own strengths.
1. In-App
This is the most powerful and contextual channel. Messages and tooltips appear at the exact moment the user is in the product and performing a specific action.
- Tools: Contextual tooltips, nudges, onboarding checklists, empty states with examples.
- Strength: Maximum relevance. You're not just saying "we have a new feature," but showing it exactly where it can be beneficial.
- Runbook (Self-Serve):
- Entry point: Determine where and when to show the message (on which screen, after which action).
- Message: 1–2 lines about "why" this is useful to the user.
- CTA: A clear call to action ("Take the first step," not "Learn more").
- Guide: Walk the user through the steps with tooltips or a short checklist.
- Safety: Alleviate the fear of making a mistake ("You can undo," "It's safe").
- Completion & Repeat: Confirm success and gently nudge for repeated use.
- Metrics: Percentage of users who reach the
value-eventand repeat it.
- Anti-Pattern: Measuring only impressions/clicks. Only the final result matters.
2. Email / Messages
This channel is great for "warming up" users who haven't been in the product for a while, or for bringing them back to a specific scenario.
- Strength: Ability to reach users outside the product.
- Weakness: Less contextual. It's only effective if the link leads directly to the relevant scenario, not the homepage.
- Runbook (Email):
- Segmentation: Strictly define who to send to (e.g., "users who did not complete onboarding").
- Reason: Explain why you are writing right now.
- One Benefit: Focus on one key benefit.
- One Path: The link must lead directly to the action.
- Repeat and Stop Rule: Schedule a reminder and a rule for when you stop "bothering" the user.
- Anti-Pattern: "Emailing everyone" is a direct path to noise, unsubscribes, and a poor signal.
3. CS / Sales (High-Touch)
This channel is indispensable in B2B, for complex products, or when working with high-value clients. Nothing replaces personal communication for mitigating risks and building trust.
- Strength: Direct contact, ability to answer complex questions, personal approach.
- Weakness: Poorly scalable.
- Runbook (CS / Sales):
- List: Identify a list of accounts or users to contact.
- Meaning Script: Prepare a 20-second pitch on "why the client needs this."
- First Win Together: Go through the
activation pathwith the client on a call. - Risk Mitigation: Explain how security, control, and rollback options work.
- Success Confirmation: Clearly define what you both will consider a "win."
- Follow-up: Agree on the next step and a return to the scenario.
- Anti-Pattern: "Giving a demo" instead of "guiding to a
value-event." A demonstration is not the same as a real result achieved by the client.
Mixed Channels—The Best Choice
In most cases, the most effective strategy is a combination of channels.
- Example:
- An
In-apptooltip guides the user to an action within the product. CSproactively contacts high-value clients to help them with setup.Emailbrings back those who "dropped off" midway, reminding them of the value.
- An
By consciously choosing and combining Delivery channels, you significantly increase the chances that your new feature will become not just a line in the release notes, but a genuinely working tool that benefits your users.