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

# Plate Recognizer

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

Plate Recognizer offers Automatic License Plate Recognition (ALPR) solutions for processing images and videos to detect and decode vehicle license plates.

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

## Where Plate Recognizer fits in a DialNexa workflow

Plate Recognizer 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="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>

  <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>
</CardGroup>

## What DialNexa should capture for Plate Recognizer

* 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 Plate Recognizer workflows

<AccordionGroup>
  <Accordion title="Low-confidence match needs review">
    For this workflow, DialNexa should send Plate Recognizer 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 Plate Recognizer 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 Plate Recognizer 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="Specialist review is required">
    For this workflow, DialNexa should send Plate Recognizer 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="Missing information blocks progress">
    DialNexa should attach the relevant file or visual evidence, summarize what the caller says it proves, and mark the review owner in Plate Recognizer. Sensitive files should stay behind restricted links.
  </Accordion>

  <Accordion title="Approval is needed before action">
    For this workflow, DialNexa should send Plate Recognizer 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="Recurring issue should be categorized">
    DialNexa should write the symptom, expected behavior, actual behavior, affected area, business impact, and evidence links into Plate Recognizer. A teammate should be able to triage the issue without replaying the call.
  </Accordion>

  <Accordion title="Use read license plate">
    Use read license plate when the call outcome maps clearly to that operation and the required fields, owner, review state, and evidence links are known.
  </Accordion>

  <Accordion title="Use snapshot get statistics">
    Use snapshot get statistics 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 Plate Recognizer with other integrations

* [Plate Recognizer](/integrations/platerecognizer) + [Google Calendar](/integrations/googlecalendar): Google Calendar for scheduled callbacks.
* [Plate Recognizer](/integrations/platerecognizer) + [HubSpot](/integrations/hubspot): HubSpot for customer context.
* [Plate Recognizer](/integrations/platerecognizer) + [Slack](/integrations/slack): Slack for owner alerts.
* [Plate Recognizer](/integrations/platerecognizer) + [Google Sheets](/integrations/googlesheets): Google Sheets for review queues.
* [Plate Recognizer](/integrations/platerecognizer) + [Zendesk](/integrations/zendesk): Zendesk for support follow-up.
* [Plate Recognizer](/integrations/platerecognizer) + [Google Docs](/integrations/googledocs): Google Docs for operational briefs.

## Implementation notes

* Use the DialNexa call ID as the idempotency key before running Plate Recognizer actions.
* Write a short operational summary into Plate Recognizer 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 should a call become a project brief?">
    When the conversation includes background, constraints, files, decisions, and multiple follow-up steps.
  </Accordion>

  <Accordion title="How do teams avoid task spam?">
    Create tasks only for actionable work. Tag informational calls and resolved questions without opening work items.
  </Accordion>

  <Accordion title="What should be linked?">
    Transcript, recording, CRM account, support ticket, files, calendar event, and downstream task URL.
  </Accordion>

  <Accordion title="When should managers be notified?">
    Notify managers for blocked work, VIP customers, missed commitments, urgent deadlines, or repeated operational issues.
  </Accordion>

  <Accordion title="How should completed work close the loop?">
    Update the task, notify the owner, and trigger the customer-facing follow-up that was promised on the call.
  </Accordion>

  <Accordion title="Should DialNexa create tasks automatically?">
    Yes when owner, outcome, and due date are clear. Use review for vague, sensitive, or high-value commitments.
  </Accordion>

  <Accordion title="What makes a task actionable?">
    A clear title, customer context, acceptance criteria, owner, deadline, evidence links, and next step.
  </Accordion>

  <Accordion title="How should promises be tracked?">
    Capture who promised what, to whom, by when, and where the customer should get the update.
  </Accordion>
</AccordionGroup>