Practical guide
A practical workflow for a shared Telegram support account
Use separate CS identities, a clear primary owner and explicit handovers to keep shared Telegram customer service accountable.
1. Assign individual CS access
Give each agent their own Tracker login. Have the admin authorise the business Telegram account, bind it to the correct workspace and assign CS access. Several CS can share one Telegram workspace, while an individual CS may be assigned more than one workspace.
2. Verify the working account
Before replying, confirm that Tracker recognises the Telegram account and corresponding workspace. Account verification pauses protected actions until the account is matched. Test each assigned account before putting a new multi-workspace workflow into daily use.
3. Start responsibility with a successful reply
For supported chats, the first verified successful CS reply can create Handle when no owner exists. Do not treat text typed into the input box as a reply. During setup, use a test customer and verify the ownership event in Backend after sending.
4. Separate assistance from handover
If another agent helps without receiving responsibility, record that assistance as Intervention. If the original agent is leaving or transferring the case, use Handover. A team should agree when a handover is expected and what context the incoming agent needs.
5. Close and review the round
Use Done when the round has ended, and check My Open Chats for unfinished work. Review the ownership history together with response speed and QA evidence. Start with a small test team and confirm text and the media types your team actually uses before rolling out more widely.