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

# Token Metrics

> Connect DialNexa calls to Token Metrics for charge, invoice, customer balance, subscription, refund, receipt, or finance approval workflows.

Token Metrics provides an API offering real-time, AI-powered cryptocurrency data and insights for developers to build trading bots, dashboards, and portfolio tools.

<Note>
  Use Token Metrics with DialNexa when the call involves money, billing trust, refunds, payment status, subscriptions, taxes, or invoice documents.
</Note>

## Where Token Metrics fits in a DialNexa workflow

Token Metrics should receive DialNexa output when the conversation affects a charge, invoice, customer balance, subscription, refund, receipt, or finance approval. 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="Protect revenue workflows" icon="check-circle">
    Escalate VIP payment blockers, failed renewals, duplicate charges, and collections-sensitive calls.
  </Card>

  <Card title="Resolve billing questions" icon="check-circle">
    Identify the invoice, charge, customer, amount, due date, and what the caller believes is wrong.
  </Card>

  <Card title="Route refunds and disputes" icon="check-circle">
    Capture reason, policy context, amount, order or subscription link, and approval requirement.
  </Card>

  <Card title="Send documents safely" icon="check-circle">
    Verify the recipient before resending invoices, receipts, statements, tax forms, or payment links.
  </Card>
</CardGroup>

## What DialNexa should capture for Token Metrics

* Customer, account, email, phone, invoice number, payment ID, subscription ID, and tax region
* Amount, currency, due date, payment status, refund reason, dispute reason, and credit request
* Approval threshold, finance owner, escalation reason, promised next step, and follow-up deadline
* Transcript link, recording link, DialNexa call ID, CRM link, support ticket, and payment platform link
* Suppression flag for card numbers, bank details, tax identifiers, and private billing documents

## High-value Token Metrics workflows

<AccordionGroup>
  <Accordion title="Refund request needs approval">
    Use Token Metrics to keep the money-related context precise: reference number, amount if mentioned, customer claim, policy or approval need, and the safe follow-up path. Do not put private payment details into broad-access notes.
  </Accordion>

  <Accordion title="Tax or billing address must be corrected">
    Use Token Metrics to keep the money-related context precise: reference number, amount if mentioned, customer claim, policy or approval need, and the safe follow-up path. Do not put private payment details into broad-access notes.
  </Accordion>

  <Accordion title="VIP customer has a payment blocker">
    For this scenario, DialNexa should treat Token Metrics 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="Collections call requires careful notes">
    For this workflow, DialNexa should send Token Metrics 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="Receipt needs to go to a verified email">
    Use Token Metrics to keep the money-related context precise: reference number, amount if mentioned, customer claim, policy or approval need, and the safe follow-up path. Do not put private payment details into broad-access notes.
  </Accordion>

  <Accordion title="Caller disputes a charge">
    Use Token Metrics to keep the money-related context precise: reference number, amount if mentioned, customer claim, policy or approval need, and the safe follow-up path. Do not put private payment details into broad-access notes.
  </Accordion>

  <Accordion title="Use get price">
    Use get price before answering, routing, or creating follow-up. DialNexa should verify the lookup result against the caller and send low-confidence matches to a human queue.
  </Accordion>

  <Accordion title="Use get tokens">
    Use get tokens before answering, routing, or creating follow-up. DialNexa should verify the lookup result against the caller and send low-confidence matches to a human queue.
  </Accordion>
</AccordionGroup>

## Workflows that pair Token Metrics with other integrations

* [Token Metrics](/integrations/token_metrics) + [Gmail](/integrations/gmail): Gmail for approved billing follow-up.
* [Token Metrics](/integrations/token_metrics) + [Slack](/integrations/slack): Slack for urgent finance approvals.
* [Token Metrics](/integrations/token_metrics) + [Zendesk](/integrations/zendesk): Zendesk for customer-facing billing tickets.
* [Token Metrics](/integrations/token_metrics) + [Google Drive](/integrations/googledrive): Google Drive for storing invoices and credit notes.
* [Token Metrics](/integrations/token_metrics) + [Google Sheets](/integrations/googlesheets): Google Sheets for exception review queues.
* [Token Metrics](/integrations/token_metrics) + [Stripe](/integrations/stripe): Stripe for payment and subscription status.

## Implementation notes

* Use the DialNexa call ID as the idempotency key before running Token Metrics actions.
* Write a short operational summary into Token Metrics 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="When can refunds be automated?">
    Only when identity, policy, amount, and approval rules are clear. Route exceptions, high-value refunds, and disputes to finance review.
  </Accordion>

  <Accordion title="What should a billing note include?">
    Invoice or charge reference, amount if mentioned, customer claim, policy context, owner, deadline, and safe evidence links.
  </Accordion>

  <Accordion title="How should invoice resends work?">
    Verify the recipient and customer identity first. Log what was sent, where it was sent, and why the caller requested it.
  </Accordion>

  <Accordion title="How are disputes handled?">
    Capture dispute reason, transaction reference, subscription or order link, urgency, and whether the caller expects a callback.
  </Accordion>

  <Accordion title="Where should tax details live?">
    Use the billing or accounting system with the right access controls, not broad CRM or support notes.
  </Accordion>

  <Accordion title="When should Slack alert finance?">
    Alert finance for VIP payment blockers, duplicate charges, chargebacks, urgent renewal failures, or exceptions needing approval.
  </Accordion>

  <Accordion title="How should collections calls be logged?">
    Keep tone factual, note promises made, avoid sensitive payment details, and link the call to the account balance or invoice.
  </Accordion>
</AccordionGroup>