Skip to main content
OCR Web Service provides SOAP and REST APIs for integrating Optical Character Recognition (OCR) technology into software products, mobile devices, or other web services.
Use OCR Web Service with DialNexa when a shopper or guest asks about a transaction, product, delivery, booking, availability, return, or purchase decision.

​
Where OCR Web Service fits in a DialNexa workflow

OCR Web Service should receive DialNexa output when the conversation affects a order, product, customer profile, booking, return, shipment, cart, or reservation. The handoff should explain what the caller asked for, what DialNexa learned, which record or object is affected, and who owns the next step.

Inform operations

Send urgency, location, item details, and promised next step to the team that can fix the issue.

Find the transaction

Match the caller to the order, booking, SKU, pickup, shipment, or reservation before any workflow runs.

Handle exceptions

Capture return reason, refund expectation, address change, delivery deadline, missing item, or booking constraint.

Recover buying intent

Route callers asking about price, availability, fit, stock, delivery time, or package options.

​
What DialNexa should capture for OCR Web Service

  • Customer name, phone, email, order ID, product SKU, booking ID, store, channel, and location
  • Requested action, delivery status, availability question, return reason, refund expectation, and deadline
  • VIP status, order value, loyalty status, repeat complaint, and escalation owner
  • Transcript link, recording link, DialNexa call ID, payment link, support link, and fulfillment link
  • Risk flags for wrong address, damaged item, fraud concern, urgent travel, or no-show risk

​
High-value OCR Web Service workflows

For this workflow, DialNexa should send OCR Web Service a concise, action-ready handoff: matched caller, affected record, reason for the update, urgency, owner, next step, and links to call evidence.
For this workflow, DialNexa should send OCR Web Service a concise, action-ready handoff: matched caller, affected record, reason for the update, urgency, owner, next step, and links to call evidence.
For this workflow, DialNexa should confirm location details, access notes, timing constraints, and the operational owner before updating OCR Web Service. Low-confidence addresses or risky visits should go to review.
DialNexa should write the symptom, expected behavior, actual behavior, affected area, business impact, and evidence links into OCR Web Service. A teammate should be able to triage the issue without replaying the call.
In OCR Web Service, this should become a revenue handoff with the matched account, buying signal, stage or owner suggestion, objection, and next action. DialNexa should separate real intent from noise before creating tasks.
DialNexa should capture the preferred time, timezone, owner, promise made, and contact channel before updating OCR Web Service. The receiving team should see exactly why the follow-up exists and what the caller expects next.
Use get account information 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.
Use get account credentials 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.

​
Workflows that pair OCR Web Service with other integrations

​
Implementation notes

  • Use the DialNexa call ID as the idempotency key before running OCR Web Service actions.
  • Write a short operational summary into OCR Web Service 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

Yes. Route callers who ask about fit, availability, shipping, price, package options, or trust blockers while intent is fresh.
Use order value, loyalty status, subscription status, repeat purchase, account tier, or urgent deadline to route faster.
Update the booking or calendar, send confirmation, log the reason, and notify operations if capacity or timing is tight.
Verify identity and match order ID, phone, email, product, and recent activity before making changes.
Only safe lifecycle signals such as product interest, return outcome, or follow-up need. Do not send sensitive support details.
Only for low-risk changes with clear identity and policy rules. Address changes, refunds, cancellations, and substitutions often need review.
Customer match, order ID, fulfillment status, payment status, delivery promise, prior support notes, and return eligibility.
Capture item, photo need, damage description, customer expectation, replacement or refund preference, and deadline.