Skip to main content

Telegram choices and limits

Who this is for​

Use this guide if you want to share a course or receive personally selected professional updates through Telegram. Personal pairing, destination verification and the complete alert journey are not yet verified. No bot username, pairing command or code-scanning process is established by this guide.

Start here​

For the current course-sharing control:

  1. Find a course in Professional development.
  2. Open More actions. Share in Telegram opens a share link for that course. You choose the recipient and decide whether to send it.
  3. Continue this search in Telegram, when shown, is conditional on an entitled member application and a resolved search location. It may fail or offer a copied link if a popup is blocked. Opening a share link does not establish a personal professional-alert destination.

For future personal updates, require a verified pairing to your own Abe identity and exact personal context before selecting Telegram as a destination. Choose your own criteria and timing in Alerts. If Telegram is not an offered verified destination, do not substitute another destination or assume payment enables it. Funding and app permissions do not supply notification consent.

What success looks like​

For a course share, the share window or copied link is visible; you still control any send. It is not proof that the recipient received it. For a future personal update, an accepted status would need Telegram's matching message and private-chat confirmation for your verified destination. Acceptance would confirm the provider accepted the message, not that you read it. An uncertain response must remain uncertain. Local receipt checks have been tested; personal pairing and actual update delivery remain unavailable.

If it does not work​

Use the direct professional-development finder if continuation fails. A blocked popup or unavailable location is not a reason to send private search details to an unknown bot. For an uncertain provider result, check the existing delivery record first; do not blindly retry. Use Troubleshooting.

Stop or change your choices​

Pause alerts in Abe independently of any Telegram setting. Disconnect any supported app permission through Manage and cancel, then check the resulting state. Do not treat a pending remote disconnect as confirmed. Disconnection does not cancel paid funding. Keep patient text and consultation content out of sharing and channel setup.