Support
How to reach TelegramOS: the in-app support chat, the public Telegram bot, security and abuse reports, and privacy requests.
Contact methods
| Need | Where |
|---|---|
| Anything while signed in (billing, accounts, bugs, sales) | The Support bubble at the bottom of every dashboard page |
| Questions before you sign up | Message @TelOsNotif_Bot on Telegram |
| Security vulnerability | In-app Support; process on /security |
| Abuse, spam, impersonation, takedown | In-app Support; what to include is on /legal/abuse |
| Privacy and data requests | In-app Support; policy on /privacy, processor terms on /dpa |
There are no support, sales, security or abuse mailboxes. The only address the platform sends from is no-reply@telegramos.net, for sign-in and verification codes, and it does not receive mail. The /contact page routes every topic to the in-app Support chat.
In-app support
The Support bubble opens a chat panel. Each conversation is a ticket.
- Press New conversation and describe the problem. Attach a screenshot if it helps: images only, up to 10 MB, one per message.
- The ticket is mirrored to our team's Telegram as a topic. Replies land in the same panel in real time, and the bubble shows an unread badge.
- If you signed in with Telegram and are not on the site when we answer, the login bot sends you one direct message with a button that opens the ticket.
- Close the ticket yourself with Close ticket, or we close it when it is resolved. A closed ticket cannot be replied to; open a new one instead.
Limits: 8 open tickets at a time and 4,000 characters per message. The chat works in English and Persian.
Response times
The targets published on /contact are one business day for most topics, 24 hours to acknowledge a security report, and one business day to acknowledge an abuse report with resolution within five. These are targets, not a contractual SLA, and there is no priority queue by plan and no formal escalation path. If a ticket stalls, reply in the same ticket.
Security disclosures
Report vulnerabilities through in-app Support. The disclosure process, scope and out-of-scope list are on /security: acknowledgement within 24 hours, remediation of verified high-severity issues targeted within 14 days, and no action against good-faith researchers acting within scope. There is no bug bounty.
Platform status
There is no status page. /changelog is a release log of shipped features and fixes; it does not show live service status, incident history or maintenance schedules, and there is nothing to subscribe to. The security page says the team aims to publish a write-up on the blog for incidents affecting more than one tenant.
Privacy requests
Access, correction, export, deletion and objection requests go through in-app Support from the account that owns the data. The privacy policy commits to a reply within 30 days. There is no self-service export or delete-workspace button; deletion is carried out by the team after you ask.