> ## 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.

# Ngrok

> Connect DialNexa calls to Ngrok for incident, alert, issue, repository, deploy, monitor, log, build, or technical escalation workflows.

Ngrok creates secure tunnels to locally hosted applications, enabling developers to share and test webhooks or services without configuring complex network settings.

<Note>
  Use Ngrok with DialNexa when a caller reports a technical failure, API problem, broken workflow, regression, outage, or engineering escalation.
</Note>

## Where Ngrok fits in a DialNexa workflow

Ngrok should receive DialNexa output when the conversation affects a incident, alert, issue, repository, deploy, monitor, log, build, or technical 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="Avoid noisy escalations" icon="check-circle">
    Separate true incidents from setup questions, product confusion, account configuration, and known limitations.
  </Card>

  <Card title="Create incident-ready reports" icon="check-circle">
    Capture affected customer, service, error, region, severity, start time, workaround, and business impact.
  </Card>

  <Card title="Create reproducible issues" icon="check-circle">
    Record expected behavior, actual behavior, steps, endpoint, screenshots or logs mentioned, and account context.
  </Card>

  <Card title="Connect calls to alerts" icon="check-circle">
    Link customer symptoms to monitors, deployments, incidents, repositories, or on-call ownership.
  </Card>
</CardGroup>

## What DialNexa should capture for Ngrok

* Customer, account, plan, environment, region, product area, endpoint, and error message
* Severity, business impact, affected users, start time, workaround, and urgency
* Steps described by caller, logs referenced, repo, deploy, monitor, alert, owner, and escalation channel
* Transcript link, recording link, DialNexa call ID, support ticket, CRM account, and status page link
* Privacy note, customer-facing update status, and next update time

## High-value Ngrok workflows

<AccordionGroup>
  <Accordion title="Caller gives reproducible bug steps">
    DialNexa should write the symptom, expected behavior, actual behavior, affected area, business impact, and evidence links into Ngrok. A teammate should be able to triage the issue without replaying the call.
  </Accordion>

  <Accordion title="On-call needs customer impact">
    For this workflow, DialNexa should send Ngrok 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="Security or abuse issue needs escalation">
    For this scenario, DialNexa should treat Ngrok 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="Status update should be sent after fix">
    For this workflow, DialNexa should send Ngrok 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="Support needs logs linked to the ticket">
    For this workflow, DialNexa should send Ngrok 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="Customer reports an outage">
    For this scenario, DialNexa should treat Ngrok 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="Use create event subscription">
    Use create event subscription only when DialNexa has a matched caller, a clear destination object, and enough call context to justify opening a new technical record. If the caller is unclear, route to review instead of creating noise.
  </Accordion>

  <Accordion title="Use update event subscription">
    Use update event subscription when the caller changes a field, status, owner, date, priority, note, consent choice, or next step on an existing Ngrok record. Include the old value, new value, and reason from the call.
  </Accordion>
</AccordionGroup>

## Workflows that pair Ngrok with other integrations

* [Ngrok](/integrations/ngrok) + [Google Docs](/integrations/googledocs): Google Docs for incident notes.
* [Ngrok](/integrations/ngrok) + [HubSpot](/integrations/hubspot): HubSpot for affected-account visibility.
* [Ngrok](/integrations/ngrok) + [Datadog](/integrations/datadog): Datadog for monitor context.
* [Ngrok](/integrations/ngrok) + [GitHub](/integrations/github): GitHub for linked code issues.
* [Ngrok](/integrations/ngrok) + [Google Sheets](/integrations/googlesheets): Google Sheets for incident review logs.
* [Ngrok](/integrations/ngrok) + [Zendesk](/integrations/zendesk): Zendesk for customer-facing support records.
* [Ngrok](/integrations/ngrok) + [Slack](/integrations/slack): Slack for on-call alerts.
* [Ngrok](/integrations/ngrok) + [Jira](/integrations/jira): Jira for engineering tasks.

## Implementation notes

* Use the DialNexa call ID as the idempotency key before running Ngrok actions.
* Write a short operational summary into Ngrok 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 makes a support handoff useful?">
    Issue, affected product, customer expectation, what DialNexa already checked, urgency, owner, next step, and transcript link.
  </Accordion>

  <Accordion title="When should a call become a product bug?">
    When the caller provides reproducible behavior, expected result, actual result, affected product area, and business impact.
  </Accordion>

  <Accordion title="How should angry customers be routed?">
    Tag sentiment, repeat contact, account value, cancellation language, and SLA risk, then notify the escalation owner.
  </Accordion>

  <Accordion title="How do callbacks get tracked?">
    Create a callback task with phone number, preferred time, timezone, owner, attempt count, and the reason for the callback.
  </Accordion>

  <Accordion title="How are duplicate tickets avoided?">
    Search open tickets and recent conversations by customer, phone, email, and issue category before creating anything new.
  </Accordion>

  <Accordion title="What should stay internal?">
    Private account details, agent-only notes, escalation reasoning, and full transcripts should stay internal unless approved for customer messaging.
  </Accordion>

  <Accordion title="How should product feedback be captured?">
    Separate feature request, bug, confusion, missing documentation, and churn risk so product teams can use the signal.
  </Accordion>
</AccordionGroup>