# 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.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/productlane-all-sources-toggle-before-support-portal-blind-spots/
- Source: [productlane.com](https://productlane.com/docs/support-portal/customer-support-portal)
- GrowthDex source hub: [Productlane Docs: Customer Support Portal](/sources/productlane-docs-customer-support-portal-productlane-com/)
- Last checked: 2026-06-08T03:14:22.000Z
- Rarity: rare
- Budget: low
- Channels: Customer Success, Support, Portal UX
- Stages: portal UX, cross-channel history, customer memory, support operations, self-serve support


## Why this can grow

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.

## Ian's take

From scaling consumer platforms across MENA and Southeast Asia, my default is to distrust growth work that only looks good in a slide. My bias is to treat this as a small market test first. Make the audience narrow, make the promise concrete, and let the first real response decide whether it deserves more work. I would run it small enough to learn quickly, then only scale the parts that real users repeat, save, reply to, or buy from. For this tactic, I would watch one clear growth signal before putting more time or budget behind it.

## Action plan

1. Define one narrow startup segment where productlane all-sources toggle before support portal blind spots can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Customer Success and Support channel.
3. Use the evidence from productlane.com to set the first version of the message, format, and audience.
4. Launch a small test for 7 to 14 days with one success metric: one measurable growth signal.
5. Review the result, keep the winning message, remove weak variants, and turn the learning into a repeatable growth playbook.

## 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.

## Adjacent tactics in the same lane

- [Strict company scope for multi-client support portals](/growth-ideas/strict-company-scope-for-multi-client-support-portals/) - same source, 2 shared channels
- [Productlane client-specific roadmap inside the support portal](/growth-ideas/productlane-client-specific-roadmap-inside-the-support-portal/) - same source, 2 shared channels
- [Saved segmented inbox views for high-value support queues](/growth-ideas/saved-segmented-inbox-views-for-high-value-support-queues/) - 2 shared channels, 1 shared stage
- [Logged-in customer portal for request status](/growth-ideas/logged-in-customer-portal-for-request-status/) - 2 shared channels, 1 shared stage

## Read GrowthDex essays

Browse the plain-English essay index at [GrowthDex Blog](/blog/).

## Related GrowthDex essays

- [The customer-facing answer should keep the context attached](/blog/the-customer-facing-answer-should-keep-the-context-attached/) - support-led growth, brand trust, customer success

## Advisory

If you want help turning this into a working growth system, Ian Goh offers advisory at https://iangoh.com/advisory.