TSF BIOS

This page will help you navigate our docs and interfaces in any situation.
It will only be of interest to TSF members. Here's how you become one.

1. Getting started

Answering Questions is our constitution. Come back to it anytime you're in doubt.

The TSupport client is your rifle.
Learn all its features, and use an up to date template file.

1a. Asking teammates for help

Never hesitate to ask for help in your local TSF group. But remember: Not everyone in your group uses the same support account and speaks the same languages as you. When you want to ask something:

Write a summary of the user's question in one message (don't copy-paste, be brief)
Always use English (there are team members in your group who don't speak your language)
Always include the entire footer from the question (all hashtags)

1b. Coming back from the dead

If you notice that you haven't answered any questions lately, go read the Coming and Going manual.

2. Tracing your progress

You can check our TSF Panel to see your stats and how you compare against other TSF members. You can also add a little TSF Bio in the panel, so that others know more about you, what you like, what you do, what devices you have and what languages you can speak.

3. Basic questions

You should be able to handle these easily. Here's where you find information:

Whenever you learn something that was not in the docs,
make sure that this new info finds its way into the docs!

4. Bug reports

Ask in your local group if anything is not clear. Use the bug report groups if you need to test things on devices you don't have.

Reporting bugs from Answering Questions
Bug Handling Manual
Investigating Bugs
Bug Platform Lore

5. User suggestions

Search the bug tracker (it could be a bug, a feature or a known suggestion). You can submit a suggestion yourself — please use common sense and the feature philosophy.

Handling user suggestions from Answering Questions
Feature philosophy
Suggestions Platform

6. Projects and suggestions for the TSF

The Telegram Support Force is full of brilliant and creative people, and there are many more useful things that can be done besides answering questions. Global events are announcements in our notifications chat, and you can also start your own projects together with interested teammates.

If you have suggestions and ideas for the general workings of the TSF, our internal communication, manuals, templates, interfaces, tools and so on, don't hesitate to contact Markus or Daria about it. Oh, and: Rude frescoes. If you have no idea what this last thing was about, read on to the end of this document.

WARNING: If you've just joined the TSF and are still figuring out what's going on, we'd suggest not to get too involved with things like side projects. It's a better idea to first get comfortable with answering user questions before you spread out.

7. Security questions

Stick to the FAQ in case of ordinary users. Always consult Markus (unless the matter is fully covered in the Bestiary). If Markus is not available at the moment, ask in your local group. Don't be afraid to tell an advanced user that you are not a specialist — you don't have to be.

Ask users for the source of their doubts, most likely you'll get a link
Advanced FAQ gives more info about MTProto for advanced users.
Advanced concerns and questions should be mailed to security@telegram.org

8. New language requests

Anyone can use the Translation platform to suggest improvements to our current translations — or create their own custom language packs and translate Telegram into any language.

9. Join support force requests

Don't give our manifesto to just anybody. Try to see if the user is reasonable. If not, you can tell them that finding how to join us is the first test.

10. Media requests

Explain that you're a volunteer and can't handle press requests, but they can submit a request to @PressBot.

Never promise anything. Be extra careful when handling any questions from journalists. If it's something related to simple Telegram features, reply – but make sure they understand that you've volunteered to help users in support and are not a spokesperson for Telegram.

If it's anything more complicated, e.g.:

Touches on any sensitive subjects like encryption, privacy, moderation, etc. in any way
Contains a list of questions

=> Simply direct to @PressBot.

11. Legal stuff

You as our volunteers are not trained in legal matters, so it's safer to do nothing at all, should you encounter any kind of legal requests. Lawyers know how to reach us. So simply ignore those messages, do not open, do not reply, do not worry. We'll handle everything.

12. Secret words

By the way, when reading our manuals, you will sometimes notice words that are definitely out of place. For example, a text may at some point say something like Bionic sycophants out of the blue – only in real life the strange words won't be highlighted in italics. If you find such words in our manuals, talk to @Gladosbot and send her the /sendsecret command (without parameters). The bot will ask you for the secret words you've found and respond if you've entered them correctly.

Try this now with the secret words you've just found in the paragraph above – and keep your eyes opened for more of them in other documents. Please don't neglect this! Secret words help us understand whether or not you are up to date on our docs in a friendly way.

13. Spam-related requests

Some users will complain that they were unfairly limited to only sending messages to their mutual contacts. We at the TSF do not have the tools to handle such requests, but our friendly @spambot is always ready to help them – and it speaks many different languages, including those that we don't. Feel free to send the spambot template to such users. If they keep insisting that you do something about their situation, it is OK to ignore them.

Some users will have you believe that somebody reported them 'for fun' or 'by mistake', but the reality is usually very different. We have a dedicated team of moderators that process every report aided by sophisticated algorithms, so it is not easy to get limited by mistake. Naturally, both humans and algorithms can err, but the @spambot has all the tools necessary for filing an appeal.

And remember: the vast, absolute majority of Telegram users never get reported at all, most reports are declined, and most of the people that do get limited never even notice it. They can talk to anyone they've talked to before, they can reply to any messages other people send them, and the initial limitation lasts for only a short period of time. Most likely, you wouldn't notice if we limited your account for a week or even a month.

Learn more about our antispam systems in the Knowledge Base»

14. Abuse requests

The Telegram Support Force is an organization of volunteers that exists to help Telegram users find their way around the apps; you, our volunteers, are not qualified to solve cases involving illegal content — and neither am I (Markus). It is not an issue of trust, rather consider this:

We would like our volunteers to be safe from possible legal consequences in case of misunderstandings and incorrectly handled cases.
Exposure to certain materials can result in life-long mental scarring, so we want to leave this to professionals that choose to handle such materials for a living.

For these good reasons the Telegram abuse department is completely separate from the TSF and is staffed by professionals and not volunteers. It is their job to deal with any public content and abuse-related disputes. Please tell users to write to abuse@telegram.org and include all the details and links — or use the built-in report buttons in our apps.

Please note: spam@telegram.org is NOT used for complaints about spam. More info

15. Subscription-related requests

Check out this card with common questions we encounter.

If the user gets an error when trying to buy a subscription, please ask for the screenshot, then report it to the local group together their footer and story, and add the #payments hashtag to your report.

16. Stick to the BIOS

This is where you go whenever you're not sure of what to do next. If you don't find your answer in the BIOS, tell Markus about it. It's important to keep this document up to date.