mirror of
https://github.com/MarshalX/telegram-crawler.git
synced 2024-12-13 02:11:00 +01:00
270 lines
18 KiB
HTML
270 lines
18 KiB
HTML
<!DOCTYPE html>
|
||
<html>
|
||
<head>
|
||
<meta charset="utf-8">
|
||
<title>Telegram Support Force</title>
|
||
<meta name="twitter:card" content="summary"></meta>
|
||
<meta property="og:title" content="Answering Questions">
|
||
<meta property="og:description" content="We answer questions. This document holds general ideas on how to handle them.
|
||
This was intended for volunteers of the Telegram…">
|
||
|
||
<link rel="icon" type="image/svg+xml" href="/img/website_icon.svg?4">
|
||
<link rel="apple-touch-icon" sizes="180x180" href="/img/apple-touch-icon.png">
|
||
<link rel="icon" type="image/png" sizes="32x32" href="/img/favicon-32x32.png">
|
||
<link rel="icon" type="image/png" sizes="16x16" href="/img/favicon-16x16.png">
|
||
<link rel="alternate icon" href="/img/favicon.ico" type="image/x-icon" />
|
||
<script>document.cookie="stel_dt="+encodeURIComponent((new Date).getTimezoneOffset())+";path=/;max-age=31536000;samesite=None;secure"</script>
|
||
|
||
<link href="//telegram.org/css/font-roboto.css?1" rel="stylesheet" type="text/css">
|
||
<link href="//telegram.org/css/bootstrap.min.css?3" rel="stylesheet">
|
||
<link href="//telegram.org/css/bootstrap-extra.css?2" rel="stylesheet">
|
||
<link href="/css/telegram.css?238" rel="stylesheet">
|
||
<link href="/css/tsf.css?7" rel="stylesheet">
|
||
<link href="/css/jquery-ui.min.css?1" rel="stylesheet">
|
||
<link href="/css/health.css?136" rel="stylesheet">
|
||
<link href="/css/tchart.min.css?10" rel="stylesheet">
|
||
<link href="/css/billboard.css?17" rel="stylesheet">
|
||
|
||
</head>
|
||
<body class="emoji_image no-transition">
|
||
|
||
<div id="aj_progress" class="progress-bar"></div>
|
||
|
||
<div id="aj_content"><div class="tr-container">
|
||
<header>
|
||
<div class="container">
|
||
<div class="header-wrap">
|
||
<div id="header-panel" class="header-panel">
|
||
<div class="header-auth">
|
||
<div class="header-auth-item"><a class="header-search-btn"></a></div><div class="header-auth-item"><a class="header-auth-link login-link" href="/auth">Login</a></div>
|
||
</div>
|
||
<div class="header-breadcrumb header-breadcrumb-simple">
|
||
<ol id="breadcrumb" class="header-nav breadcrumb"><li><a href="/">Telegram Support Force</a></li></ol>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
</header>
|
||
<main class="container">
|
||
<nav class="tr-menu">
|
||
<div class="tr-menu-section">
|
||
<div class="tr-menu-header">
|
||
<div class="tr-menu-header-label">Resources</div>
|
||
</div>
|
||
<ul class="tr-menu-items"><li>
|
||
<a class="tr-menu-item" href="/">
|
||
<span class="nav-label">Introduction</span>
|
||
</a>
|
||
</li><li class="active">
|
||
<a class="tr-menu-item" href="/manuals">
|
||
<span class="nav-label">Manuals</span>
|
||
</a>
|
||
</li></ul>
|
||
</div>
|
||
|
||
|
||
</nav>
|
||
<section class="content clearfix">
|
||
<section class="tr-content"><div id="dev_page_content_wrap" class=" ">
|
||
<div class="dev_page_bread_crumbs"><ul class="breadcrumb clearfix"><li><a href="/" >Telegram Support Initiative</a></li><i class="icon icon-breadcrumb-divider"></i><li><a href="/manuals" >Manuals</a></li><i class="icon icon-breadcrumb-divider"></i><li><a href="/manuals/answering_questions" >Answering Questions</a></li></ul></div>
|
||
<h1 id="dev_page_title">Answering Questions</h1>
|
||
|
||
<div id="dev_page_content"><p>We answer questions. This document holds general ideas on how to handle them.<br>This was intended for volunteers of the <a href="/">Telegram Support Force</a>, but anyone else is free to take a look as well.</p>
|
||
<h3><a class="anchor-link" href="#general"><i class="anchor-icon"></i></a><a class="anchor" name="general"></a>General</h3>
|
||
<ol>
|
||
<li><p>Our goal is to bring human support to human beings. To achieve this goal, we rely on volunteers. Your pay is perfection in what you do, so be cool.</p>
|
||
</li>
|
||
<li><p>Corporate support standards do not apply here. Treat people in a kind, personal, informal manner. No need to pretend to be something you are not (unless you're a dog in disguise — keep human appearances in this case).</p>
|
||
</li>
|
||
<li><p>Never lie to people.</p>
|
||
</li>
|
||
<li><p>Check everything before you reply. Things change or may no longer work the way you remember. This includes interface details, links (!) and, well, everything.</p>
|
||
</li>
|
||
<li><p>Support is a form of Art, so be fun and creative.</p>
|
||
</li>
|
||
</ol>
|
||
<h3><a class="anchor-link" href="#the-result"><i class="anchor-icon"></i></a><a class="anchor" name="the-result"></a>The result</h3>
|
||
<p>As support volunteers, we need to provide a <strong>solution</strong> for the user. Remember, that this doesn't always have to be the solution the user was asking for. So first, we want to understand the <strong>problem</strong> that drove them to ask the question. And then find a way of solving — completely or partially — that problem.</p>
|
||
<p>For example, some users ask us for an option to send sketches or drawings to their friends. While this is not possible directly, one could take a photo with their thumb on the camera (to get a black picture), then use the drawing tools built into the photo editor to make their doodle.</p>
|
||
<p>This isn't what the user was looking for, but it solves the problem — and it is even more flexible and customizable than the original idea (since you could also add stickers and emoji out of the box). Some solutions are less elegant. For example, right now you can't email your Telegram conversations. While there is much less need to do so, since you can access everything in the cloud from any of your devices, this may be a problem in some cases. What one could do then, is open the conversation in Telegram Web (or any other desktop client), select multiple messages with the mouse, then copy and paste them into a text document. Any solution is better than no solution at all.</p>
|
||
<p>There will be cases, when it is not possible to solve the problem at all. As a user in this situation, I want that people on the other end of the line <strong>understand</strong> me and <strong>care</strong> about the whole thing. Therefore, two things become important:</p>
|
||
<ul>
|
||
<li>Make it clear that you understand the issue. 'No, you can't do that' is not a good answer. 'No, I'm afraid it is not possible to make Telegram wash your dishes in a fast and securely encrypted way' — is better.</li>
|
||
<li>Be gentle. Gentle doesn't mean soft — if we really can't do something, it means just that — we can't. But adding 'Sorry about that' helps a lot.</li>
|
||
</ul>
|
||
<p>Lastly, whatever the outcome, I always look for help from a human being, not a dumb interface. When you're casual and witty, the user feels more at ease. On the other hand, human beings, as opposed to dumb interfaces, usually understand what is appropriate in which situation. For example, when a user is in distress, he most likely needs help first — and jokes can wait until the crisis has been dealt with.</p>
|
||
<hr>
|
||
<p>To sum up, we need to be: <strong>smart</strong> (to identify the problem and find an approach to the user), <strong>inventive</strong> (to find a solution, not always the obvious one), <strong>compassionate</strong> (in case there is no immediate solution) — and <strong>witty</strong> (otherwise it gets boring). I'm sure we are.</p>
|
||
<h3><a class="anchor-link" href="#what-if-i-don-39t-know-the-answer"><i class="anchor-icon"></i></a><a class="anchor" name="what-if-i-don-39t-know-the-answer"></a>What if I don't know the answer</h3>
|
||
<p>Happens to all. Don't worry, you can always find one. The <a href="/manuals/bios">TSF BIOS</a> will tell you what to do in most situations. In case it doesn't or you're not sure, ask your fellow volunteers in the group — they should know. If worst comes to worst, consult Markus.</p>
|
||
<p>Admitting you don't know something is <strong>infinitely</strong> better than trying to cover it up. So when cornered use this mantra: 'I'm afraid I don't know this. Will ask my teammates and get back to you'. Just make sure that the question is not in the FAQs before you say this.</p>
|
||
<h3><a class="anchor-link" href="#handling-user-suggestions"><i class="anchor-icon"></i></a><a class="anchor" name="handling-user-suggestions"></a>Handling user suggestions</h3>
|
||
<p>The three rules for requests and suggestions are: don't lie, don't promise anything, and don't give an exact timeframe.</p>
|
||
<ul>
|
||
<li>Telegram has an <a href="https://suggestions.telegram.org">open platform</a> where users can vote for feature suggestions and submit new ones.</li>
|
||
<li>For insights into the decision making process, check our <a href="/manuals/feature_philosophy">Feature Philosophy</a>.</li>
|
||
</ul>
|
||
<p>Plans change frequently, so it's best if we only talk about things that exist. Never say that something will be done. 'We may do this', 'we will definitely add this at some point in the future' or 'this is coming soon' — is as far as we can go.</p>
|
||
<p>Same applies to the negative: never say we will never do something (except steal users' spouses and enslave their children, as mentioned in the general FAQ). The worst thing that can happen is 'we are currently not working on this', 'we may consider this', etc.</p>
|
||
<p>Even if you know something is happening tomorrow, say 'in the next few days'. People love it when they get things earlier than they expected — and get downright angry if we get 5 minutes (or a few months) late.</p>
|
||
<h3><a class="anchor-link" href="#reporting-bugs-in-telegram"><i class="anchor-icon"></i></a><a class="anchor" name="reporting-bugs-in-telegram"></a>Reporting bugs in Telegram</h3>
|
||
<p>Telegram has an <a href="https://bugs.telegram.org">open platform</a> where users can report issues with the apps, view existing entries and vote on them.</p>
|
||
<ul>
|
||
<li><a href="https://bugs.telegram.org/c/746/47">Public card about the platform</a></li>
|
||
<li><a href="https://bugs.telegram.org/c/452">Bug Plaform Lore for the TSF</a></li>
|
||
<li>The <a href="/manuals/bugs">Handling Bugs</a> manual</li>
|
||
</ul>
|
||
<p>If you are not part of the team and are looking for advanced troubleshooting tips, you may find the <a href="/manuals/bugs#troubleshooting-common-issues">Troubleshooting</a> section interesting.</p>
|
||
<h3><a class="anchor-link" href="#chatting"><i class="anchor-icon"></i></a><a class="anchor" name="chatting"></a>Chatting</h3>
|
||
<p>Truth is, most users come to simply say 'hello'. Hello them back if you have the time. Sometimes these users do have a question after all. In other cases they may be new to Telegram, without many friends to chat with or show them around. So you can tell them more about Telegram, point to interesting features — or even other <a href="//telegram.org/apps">Telegram apps</a>. No need to advertise, just explain what needs explaining.</p>
|
||
<p>Remember: we’re here to help those we can help and talk to others that we feel we have the time to talk to, but not more. If kids get too insistent without any real needs, it’s ok to ignore them after a few replies. If somebody seems to be a nice conversation partner, it’s always a good idea to discuss Telegram, see what the user thinks is missing. Maybe tell them about our <a href="/">Support Initiative</a>.</p>
|
||
<h3><a class="anchor-link" href="#real-life-problems"><i class="anchor-icon"></i></a><a class="anchor" name="real-life-problems"></a>Real-life problems</h3>
|
||
<p>Unfortunately, we cannot really help people with real-life problems. A few kind words wouldn't hurt, but generally we should send those users to places where they can get actual help, like a crisis line or chat. (Now, if you want to be a member of the TSF and read this far, go send a picture of a kangaroo to the auditions account. No, this is not a joke. It is a test that helps us understand whether or not you actually read this. And don't tell others. If you're already a member, you know what to do: humpa viceroy squid)</p>
|
||
<h3><a class="anchor-link" href="#insults"><i class="anchor-icon"></i></a><a class="anchor" name="insults"></a>Insults</h3>
|
||
<p>Yep, everyone gets their share of those. First of all, remember that these people are not really talking to you. They just see an abstract 'Telegram' entity. My advice is to humor them — I usually send a ‘well, that escalated quickly’ picture and it helps many users. Joke around with them and you’ll be surprised how that can humble people. And never insult back, even if they manage to get you angry for some reason. Nonviolent irony is always your best — and only — weapon.</p>
|
||
<hr>
|
||
<h5><a class="anchor-link" href="#other-tsf-documents"><i class="anchor-icon"></i></a><a class="anchor" name="other-tsf-documents"></a>Other TSF documents:</h5>
|
||
<p><div class="dev_page_nav_wrap"></p>
|
||
<ul>
|
||
<li><a href="/">TSF Manifesto</a></li>
|
||
<li><a href="/manuals/bios">BIOS</a></li>
|
||
<li><strong><a href="/manuals/answering_questions">Answering questions</a></strong> (you are here)</li>
|
||
<li><a href="/manuals/bugs">Bug handling and troubleshooting</a></li>
|
||
<li><a href="/manuals/feature_philosophy">Feature Philosophy</a></li>
|
||
</ul>
|
||
<p></div></p>
|
||
</div>
|
||
|
||
</div></section>
|
||
</section>
|
||
</main>
|
||
</div><div class="popup-container login-popup-container hide" id="login-popup-container">
|
||
<div class="popup">
|
||
<div class="popup-body">
|
||
<section>
|
||
<h2>Log In</h2>
|
||
<p>Log in here to access your TSF stats. Please enter your <b>phone number</b> in the <a target="_blank" rel="noopener" href="https://telegram.org/faq#login-and-sms">international format</a> and we will send a confirmation message to your account via Telegram.</p>
|
||
|
||
<form id="send-form" class="login-form">
|
||
<div class="form-group">
|
||
<input type="tel" class="form-control tr-form-control input-lg" id="phone-number" placeholder="+12223334455" autocomplete="off"/>
|
||
</div>
|
||
<div class="popup-buttons">
|
||
<a class="btn btn-link btn-lg login-cancel-btn">Cancel</a><button type="submit" class="btn btn-link btn-lg">Next</button>
|
||
</div>
|
||
</form>
|
||
|
||
<div id="login-form" class="hide">
|
||
<div class="form-group">
|
||
<span class="form-control tr-form-control input input-lg input-disabled"><strong id="phone-number-field"></strong> (<a class="login-back" href="/auth">Incorrect?</a>)</span>
|
||
<p class="help-block dots-animated">We've just sent you a message.<br/>Please confirm access via Telegram</p>
|
||
</div>
|
||
<div class="popup-buttons">
|
||
<a class="btn btn-link btn-lg login-cancel-btn">Cancel</a><a class="btn btn-link btn-lg login-back">Back</a>
|
||
</div>
|
||
</div>
|
||
</section>
|
||
</div>
|
||
</div>
|
||
</div></div>
|
||
<script src="//telegram.org/js/jquery.min.js?1"></script>
|
||
<script src="//telegram.org/js/bootstrap.min.js"></script>
|
||
<script src="//telegram.org/js/main-aj.js?69"></script>
|
||
<script src="/js/main.js?47"></script>
|
||
<script src="/js/tsf.js?3"></script>
|
||
<script src="/js/jquery-ui.min.js?1"></script>
|
||
<script src="/js/tchart.min.js?18"></script>
|
||
<script src="/js/billboard.min.js?1"></script>
|
||
<script src="/js/stats.js?18"></script>
|
||
|
||
<script>ajInit({"version":810,"apiUrl":"\/api?hash=telegram-crawler","unauth":true});</script>
|
||
<script id="aj_script">Aj.onLoad(function(state) {
|
||
function requestConfirmation(event) {
|
||
event && event.preventDefault();
|
||
var phone = $('#phone-number').val();
|
||
$.ajax({
|
||
type: 'POST',
|
||
url: '/auth/request',
|
||
data: {
|
||
phone: phone
|
||
},
|
||
success: function(result) {
|
||
$('#phone-number-field').text(phone);
|
||
$('#send-form').addClass('hide');
|
||
$('#login-form').removeClass('hide');
|
||
checkAuth(result.temp_session);
|
||
},
|
||
error: function(xhr) {
|
||
showAlert(xhr.responseText || 'Server error');
|
||
},
|
||
dataType: 'json'
|
||
});
|
||
return false;
|
||
}
|
||
function cancelConfirmation(event) {
|
||
event && event.preventDefault();
|
||
$('#phone-number-field').text('');
|
||
$('#send-form').removeClass('hide');
|
||
$('#login-form').addClass('hide');
|
||
$('#phone-number').focus();
|
||
clearTimeout(window.authTimeout);
|
||
return false;
|
||
}
|
||
function checkAuth(temp_session) {
|
||
clearTimeout(window.authTimeout);
|
||
window.authTimeout = setTimeout(function doCheckAuth() {
|
||
$.ajax({
|
||
type: 'POST',
|
||
url: '/auth/login',
|
||
data: {
|
||
temp_session: temp_session
|
||
},
|
||
success: function(result) {
|
||
if (result) {
|
||
location.reload();
|
||
} else {
|
||
checkAuth(temp_session);
|
||
}
|
||
},
|
||
error: function (xhr) {
|
||
showAlert(xhr.responseText || 'Server error');
|
||
},
|
||
dataType: 'json'
|
||
});
|
||
}, 700);
|
||
}
|
||
$('#login-popup-container').on('popup:open', function() {
|
||
$('#phone-number').focus();
|
||
});
|
||
$('#login-popup-container').on('popup:close', function() {
|
||
cancelConfirmation();
|
||
if (location.pathname == '/auth') {
|
||
window.history && history.replaceState(null, null, '/');
|
||
}
|
||
});
|
||
$('#login-popup-container #send-form').on('submit', requestConfirmation);
|
||
$('#login-popup-container .login-cancel-btn').on('click', function(e) {
|
||
e.preventDefault();
|
||
closePopup('#login-popup-container');
|
||
});
|
||
$('#login-popup-container .login-back').on('click', cancelConfirmation);
|
||
$('.login-link').on('click', function(e) {
|
||
e.stopImmediatePropagation();
|
||
e.preventDefault();
|
||
openPopup('#login-popup-container');
|
||
});
|
||
});
|
||
Aj.onUnload(function(state) {
|
||
$('#login-popup-container').off('popup:open');
|
||
$('#login-popup-container').off('popup:close');
|
||
$('#login-popup-container #send-form').off('submit');
|
||
$('#login-popup-container .login-cancel-btn').off('click');
|
||
$('#login-popup-container .login-back').off('click');
|
||
$('.login-link').off('click');
|
||
});
|
||
</script>
|
||
<script>Aj.pageLoaded();</script>
|
||
|
||
</body>
|
||
</html>
|
||
|