Use S.A.R.A.H. for public source checks.
Before Telegram
Use this to confirm the request belongs here before opening Telegram.
Request loop
Use one loop: collect the question, check the source, answer briefly, then stop or hand off.
Manual scan path
Confirm the request fits a public-source lane, read the loop to see whether one reply is enough, name the limit, and open Telegram only after the handoff path is clear.
Response path
Start only when a page, source, official-link, or community question can be checked against a public record.
Check official pages, Trust Center disclosures, public records, and official links before S.A.R.A.H. answers.
Use the available evidence to choose a brief answer, a redirect, or a stop for Contact or Business Support.
Keep the reply plain, name the useful source, and stop before the thread becomes support triage.
Support, complaints, account, recovery, or formal requests go to Contact. Qualified commercial follow-through goes to Business Support.
The manual is a decision tool, not a conversation script. It keeps the request public, short, and easy for a human to audit.
Example
Request: "Where should I check official links?"
Point to Mr Lightspeed pages, Trust Center disclosures, and official Telegram/community links. Name the source, then stop before advice, account help, recovery, or commercial follow-through.
Room rules
Use S.A.R.A.H. in a group only when one sourced reply helps. Keep the reply brief and verifiable. Sensitive, formal, account-specific, or recovery-adjacent work belongs on Contact. Qualified commercial follow-through belongs on Business Support.
Room stop points
Keep the group useful: answer the narrow question, skip commentary, and stop when the request leaves public-source scope.
Telegram boundary
Use Telegram only after the source, reply limit, and handoff path are clear. Take support, complaints, account, recovery, or formal requests to Contact. Take qualified commercial follow-through to Business Support.
When to use commands
Hard limits
Platform disclosureSelecting the Telegram CTA opens a third-party platform. Messages are handled by Telegram and are subject to Telegram policies and uptime; do not share private keys, seed phrases, or other sensitive account data.
Human judgmentKeep human judgment in the loop. Never share keys, seed phrases, recovery data, or sensitive commercial terms in Telegram or any bot-assisted flow.
Group entry rule
Add S.A.R.A.H. only after the group needs one public source check. Personal, account, recovery, business, or formal follow-up stays out of the group.
Use Contact for support, complaints, account, recovery, or formal follow-up. Use Business Support for qualified commercial follow-through.
Safe use cases
Escalation routes