SEEDSTREAM

Contact

ROUTE FIRST · MESSAGE WHEN NEEDED
CONTACT WITH CONTEXT

Most issues have a direct route before they need a message.

Use the routes below to solve the issue at the source. When a message is actually needed, include enough operational context to make it actionable without sending passwords, authentication secrets or unrelated sensitive information.

LOGIN / ACCOUNT ACCESSRecover access through the privacy-preserving recovery flow.STALE / UNAVAILABLE DATACheck whether the issue is already reflected in current service or data health.PRODUCT INTERPRETATIONUse the public definitions and interpretation framework for what an output means.NOTIFICATIONSCheck browser permission, eligibility and symbol preferences.STANDARD VS FASTCompare the product boundary before making an access decision.
WHEN YOU DO MESSAGE

Include the facts that make the issue reproducible.

Use this for any issue that does not need one of the structured routes above.

PAGEWhere in SeedStream the issue appearsTIMEApproximate time and session contextEXPECTEDWhat you expected to see or accessOBSERVEDWhat appeared insteadACCESSYour Standard / FAST / public access levelREFERENCEPayment reference only when relevant