Product

Telegram

Connect a dedicated warehouse Telegram account to Quoting24: private chats sync and operators reply from the same ticket UI — without provider URLs, API hashes or infrastructure details.

  • Connect from Settings → Telegram
  • Dedicated tenant Telegram account (not an operator’s personal one)
  • Sign-in with phone, code and 2FA when required
  • Private chat sync into Quoting24 tickets
  • Replies and media sent through the linked account

How Telegram connects

An admin opens Settings → Telegram, confirms a dedicated warehouse account, and starts the link. They enter the phone number, request the code Telegram sends, and confirm it; if the account has two-step verification, they also enter the 2FA password.

When status becomes READY, Quoting24 can sync chats and operators work from the ticket. Customers never see provider URLs, API ID/hash or session paths: that stays behind the scenes, like WhatsApp through a dedicated provider.

  • Guided flow in Settings → Telegram
  • Phone + code (and 2FA if needed)
  • READY status before sync and sends

What lands in Quoting24

After connecting you can sync private conversations: contacts, messages and attachments become part of Quoting24’s ticket flow. Operators reply from Quoting24; text and media go out through the linked Telegram account.

Current scope is private user↔user chats. Groups and channels are not the starting operating model: the goal is to bring parts requests from Telegram into the same quote workflow.

  • Private chat sync into tickets and conversations
  • Send text and media from the linked account
  • Read, edit, delete and react on Telegram messages

Disconnect and control

From Settings you can sync again or disconnect the account. Disconnect closes the Telegram session on the provider side and updates status in Quoting24.

A dedicated account keeps operators’ personal chats out of warehouse requests: the team works in Quoting24, Telegram remains the in/out channel.