Back to GrowthDex
Growth idea action plan

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.

rare tacticlow budget

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.

Company 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 and metric

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.

Customer SuccessSupportPortal UXportal UXcross-channel historycustomer memorysupport operationsself-serve support
GrowthDex operator note

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.

Founder checklist

  1. Read Productlane Docs: Customer Support Portal and identify what is directly supported.
  2. Choose one channel context: Customer Success, Support, Portal UX.
  3. Define the test around Productlane frames the all-sources toggle as the setting that lets customers see support requests from outside the portal, not only portal-native ones..
  4. Set an owner, evidence window, and stop condition before launch.

Explore the context

Advisory bridge

Apply this with an operator

Connect activation, customer value, retention, and referral into one measurable loop.

Work with Ian