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

# Rev AI

> Connect DialNexa calls to Rev AI for record, request, case, lookup, approval, workflow run, or operational task workflows.

Rev AI provides advanced machine learning and speech recognition services for converting audio and video to text.

<Note>
  Use Rev AI with DialNexa when the call creates a specialized follow-up that needs owner, urgency, and clear operational context.
</Note>

## Where Rev AI fits in a DialNexa workflow

Rev AI should receive DialNexa output when the conversation affects a record, request, case, lookup, approval, workflow run, or operational task. 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="Create structured handoffs" icon="check-circle">
    Capture caller identity, request, affected object, owner, urgency, and decision needed.
  </Card>

  <Card title="Route niche requests" icon="check-circle">
    Send specialized calls to the person who knows the system, product, policy, or customer context.
  </Card>

  <Card title="Build review queues" icon="check-circle">
    Hold unclear, sensitive, high-value, or low-confidence cases for human review.
  </Card>

  <Card title="Measure recurring issues" icon="check-circle">
    Tag repeated call reasons so operations can see where customers keep getting stuck.
  </Card>
</CardGroup>

## What DialNexa should capture for Rev AI

* Caller identity, account, source, owner, category, urgency, and related object ID
* Call summary, requested outcome, missing information, blocker, and promised next step
* Status, priority, deadline, approval requirement, duplicate key, and review reason
* Transcript link, recording link, DialNexa call ID, CRM link, ticket link, and file links
* Sensitive-data flag and routing note for human review

## High-value Rev AI workflows

<AccordionGroup>
  <Accordion title="Recurring issue should be categorized">
    DialNexa should write the symptom, expected behavior, actual behavior, affected area, business impact, and evidence links into Rev AI. A teammate should be able to triage the issue without replaying the call.
  </Accordion>

  <Accordion title="Customer promise needs tracking">
    For this workflow, DialNexa should send Rev AI 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="Low-confidence match needs review">
    For this workflow, DialNexa should send Rev AI 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="Owner should be alerted quickly">
    For this workflow, DialNexa should send Rev AI 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="Caller creates an operational request">
    For this workflow, DialNexa should send Rev AI 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="Use delete custom vocabulary">
    Treat delete custom vocabulary 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 Rev AI.
  </Accordion>

  <Accordion title="Use get account">
    Use get account 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 Rev AI with other integrations

* [Rev AI](/integrations/rev_ai) + [Zendesk](/integrations/zendesk): Zendesk for support follow-up.
* [Rev AI](/integrations/rev_ai) + [Google Docs](/integrations/googledocs): Google Docs for operational briefs.
* [Rev AI](/integrations/rev_ai) + [Gmail](/integrations/gmail): Gmail for approved customer follow-up.
* [Rev AI](/integrations/rev_ai) + [Google Calendar](/integrations/googlecalendar): Google Calendar for scheduled callbacks.
* [Rev AI](/integrations/rev_ai) + [HubSpot](/integrations/hubspot): HubSpot for customer context.
* [Rev AI](/integrations/rev_ai) + [Slack](/integrations/slack): Slack for owner alerts.

## Implementation notes

* Use the DialNexa call ID as the idempotency key before running Rev AI actions.
* Write a short operational summary into Rev AI 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="How do we reduce hallucinations?">
    Use approved knowledge sources, cite source records, set fallback behavior, and route low-confidence answers to humans.
  </Accordion>

  <Accordion title="Can DialNexa write follow-up messages with AI?">
    Yes, but drafts should use the actual call outcome, approved tone, and customer context. Sensitive messages should be reviewed.
  </Accordion>

  <Accordion title="What data should not be sent to AI tools?">
    Secrets, payment data, private HR or health details, and anything your policy forbids unless the tool and workflow are approved.
  </Accordion>

  <Accordion title="How should extraction errors be handled?">
    Store confidence and route missing or conflicting fields to review rather than silently updating downstream systems.
  </Accordion>

  <Accordion title="When should an AI answer fall back to a human?">
    When source context is missing, confidence is low, the caller disputes the answer, or the next step changes money, access, or legal commitments.
  </Accordion>

  <Accordion title="What should be measured over time?">
    Intent accuracy, extraction accuracy, fallback rate, review overrides, bad answers, and customer outcomes after AI-generated follow-up.
  </Accordion>

  <Accordion title="Should AI outputs act without review?">
    Only for low-risk workflows with clear confidence thresholds. Account changes, money, access, legal, and sensitive support cases need review.
  </Accordion>

  <Accordion title="What should be logged for AI decisions?">
    Prompt version, source context, model or workflow ID, confidence, output, call ID, and reviewer when applicable.
  </Accordion>
</AccordionGroup>