Productlane all-sources toggle before support portal blind spots
Turn on requests from all sources before you push customers to the support portal so the page shows the full cross-channel history instead of a misleading slice of portal-native threads.
Why this can grow a startup
A customer portal feels broken when it pretends the relationship started the moment the portal link appeared. Productlane is unusually direct here: teams should turn on the all-sources setting so customers can see requests that did not originate in the portal itself. That is important because support memory usually lives across email, Slack, tickets, and product requests. If the portal only exposes the subset created in one surface, the customer reads the page as incomplete and keeps going back to private follow-ups. The better pattern is to let the portal become the shared record after the fact. Ian's operator lens: buyers trust a system that remembers them. They distrust a system that makes them restate the same context every time the interface changes.
Source-backed example
Productlane's support-portal docs tell teams to turn on 'Requests from all sources' so customers can see requests that did not come only from the portal.
Source-reported evidence
Source: Productlane Docs: Customer Support Portal · Browse Productlane Docs: Customer Support Portal tactics
Productlane frames the all-sources toggle as the setting that lets customers see support requests from outside the portal, not only portal-native ones.
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.
When to use it
Use this when Customer Success, Support, Portal UX is relevant to portal UX, cross-channel history, customer memory and you can run a bounded test with a low 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 Customer Success and Support, using evidence from Productlane Docs: Customer Support Portal as context—not as a promised result.
- Record a baseline for: Users who resolve the issue and complete the next useful 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
Connect activation, customer value, retention, and referral into one measurable loop.
SOURCE HUB
More tactics from Productlane Docs: Customer Support Portal
Explore related GrowthDex examples and evidence connected to Productlane Docs: Customer Support Portal.
Open Productlane Docs: Customer Support Portal source hub