> ## Documentation Index
> Fetch the complete documentation index at: https://dialnexa.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Telegram

> Connect DialNexa calls to Telegram for vault item, access request, identity check, security review, policy exception, or suspicious-call escalation workflows.

Telegram is a cloud-based messaging app with a focus on security and speed. Build bots to send messages, manage chats, and interact with users.

<Note>
  Use Telegram with DialNexa when the caller asks for access, recovery, permission changes, vault help, or anything that could expose sensitive systems.
</Note>

## Where Telegram fits in a DialNexa workflow

Telegram should receive DialNexa output when the conversation affects a vault item, access request, identity check, security review, policy exception, or suspicious-call escalation. The handoff should explain what the caller asked for, what DialNexa learned, which record or object is affected, and who owns the next step.

<CardGroup cols={2}>
  <Card title="Route policy exceptions" icon="check-circle">
    Send unusual access requests to the correct security or IT owner with the policy, reason, and urgency attached.
  </Card>

  <Card title="Verify the caller before access changes" icon="check-circle">
    Capture who called, what access they requested, which workspace is affected, and whether identity confidence is high enough for review.
  </Card>

  <Card title="Escalate risky requests" icon="check-circle">
    Flag callers asking for secrets, emergency access, admin changes, recovery help, or unusual account actions.
  </Card>

  <Card title="Keep secrets out of notes" icon="check-circle">
    Store a safe summary and links to restricted evidence instead of writing passwords, tokens, keys, or recovery codes.
  </Card>

  <Card title="Preserve the audit trail" icon="check-circle">
    Attach call ID, owner, decision, timestamp, and review outcome so security can reconstruct what happened.
  </Card>
</CardGroup>

## What DialNexa should capture for Telegram

* Caller identity, organization, role, account, phone, and verification confidence
* Requested permission, policy exception, recovery action, affected system, and severity
* Risk reason, suspicious phrases, urgency, approval requirement, and escalation owner
* Safe summary, transcript link, recording link, DialNexa call ID, and review status
* Redaction flag for secrets, tokens, passwords, keys, or recovery codes

## High-value Telegram workflows

<AccordionGroup>
  <Accordion title="A caller mentions leaked credentials or phishing">
    For this workflow, DialNexa should send Telegram a concise, action-ready handoff: matched caller, affected record, reason for the update, urgency, owner, next step, and links to call evidence.
  </Accordion>

  <Accordion title="A manager wants an audit trail for an access exception">
    For this workflow, DialNexa should send Telegram a concise, action-ready handoff: matched caller, affected record, reason for the update, urgency, owner, next step, and links to call evidence.
  </Accordion>

  <Accordion title="A suspicious caller repeats failed verification attempts">
    For this scenario, DialNexa should treat Telegram as an escalation destination. Send the impact, urgency, affected customer or object, owner, and transcript link so the right team can act before the issue gets colder.
  </Accordion>

  <Accordion title="Security needs a post-call incident note">
    For this scenario, DialNexa should treat Telegram as an escalation destination. Send the impact, urgency, affected customer or object, owner, and transcript link so the right team can act before the issue gets colder.
  </Accordion>

  <Accordion title="Caller asks for emergency account recovery">
    For this workflow, DialNexa should send Telegram a concise, action-ready handoff: matched caller, affected record, reason for the update, urgency, owner, next step, and links to call evidence.
  </Accordion>

  <Accordion title="Employee requests access to a restricted vault">
    DialNexa should keep this people workflow minimal and private: identity, role or case, requested next step, owner, timing, and sensitivity flag. Do not copy unnecessary personal details into Telegram.
  </Accordion>

  <Accordion title="Use send document">
    Use send document only after DialNexa confirms recipient, consent, channel, message purpose, and the exact follow-up promised during the call.
  </Accordion>

  <Accordion title="Use delete message">
    Treat delete message as a controlled workflow. DialNexa should capture the caller's reason, identity confidence, approval owner, and rollback path before anything destructive or irreversible happens in Telegram.
  </Accordion>
</AccordionGroup>

## Workflows that pair Telegram with other integrations

* [Telegram](/integrations/telegram) + [Google Docs](/integrations/googledocs): Google Docs for audit notes and incident summaries.
* [Telegram](/integrations/telegram) + [Google Sheets](/integrations/googlesheets): Google Sheets for access-review queues.
* [Telegram](/integrations/telegram) + [HubSpot](/integrations/hubspot): HubSpot for account-owner awareness on enterprise customers.
* [Telegram](/integrations/telegram) + [Gmail](/integrations/gmail): Gmail for approved follow-up after review.
* [Telegram](/integrations/telegram) + [Zendesk](/integrations/zendesk): Zendesk for the support ticket that triggered the access request.
* [Telegram](/integrations/telegram) + [Slack](/integrations/slack): Slack for urgent review by security or IT.
* [Telegram](/integrations/telegram) + [Jira](/integrations/jira): Jira for longer remediation work.

## Implementation notes

* Use the DialNexa call ID as the idempotency key before running Telegram actions.
* Write a short operational summary into Telegram and link to the full transcript or recording for audit.
* Map required fields before launch: destination object, owner, status, urgency, next step, and record URL.
* Create review paths for low-confidence matches, sensitive requests, high-value customers, and actions that change money, access, legal terms, or customer commitments.

## FAQs

<AccordionGroup>
  <Accordion title="What should happen after failed verification?">
    Stop the account-changing workflow, create a restricted review item, and include the attempted request, failed checks, call ID, and escalation owner.
  </Accordion>

  <Accordion title="What belongs in the audit trail?">
    Caller identity, requested action, reviewer, decision, timestamp, policy reason, DialNexa call ID, and links to restricted transcript or recording evidence.
  </Accordion>

  <Accordion title="How should suspicious callers be routed?">
    Tag the risk reason, avoid giving sensitive details, and notify the security or IT channel with the safe summary and evidence links.
  </Accordion>

  <Accordion title="What should stay out of Slack or CRM?">
    Secrets, recovery phrases, private keys, full transcripts, and detailed internal security reasoning should stay in restricted systems.
  </Accordion>

  <Accordion title="Should DialNexa ever store passwords or secrets here?">
    No. Store a safe summary, risk reason, and restricted evidence links. Do not write passwords, recovery codes, tokens, API keys, or private credentials into broad-access records.
  </Accordion>

  <Accordion title="When should a call become a security review?">
    Create a review when the caller asks for account recovery, admin access, permission changes, shared secrets, unusual exceptions, or anything that changes security posture.
  </Accordion>
</AccordionGroup>