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

# Elasticsearch

> Connect DialNexa calls to Elasticsearch for address, route, appointment, booking, shipment, service job, phone validation, or site record workflows.

Elasticsearch is a distributed, RESTful search and analytics engine capable of addressing a growing number of use cases. It provides real-time search and analytics for all types of data.

<Note>
  Use Elasticsearch with DialNexa when where, when, route, address, delivery, dispatch, phone validity, or appointment constraints affect the next step.
</Note>

## Where Elasticsearch fits in a DialNexa workflow

Elasticsearch should receive DialNexa output when the conversation affects a address, route, appointment, booking, shipment, service job, phone validation, or site record. 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="Reduce failed visits" icon="check-circle">
    Flag invalid addresses, no-access risk, wrong region, unreachable number, or outside-service-area cases.
  </Card>

  <Card title="Validate location details" icon="check-circle">
    Confirm address, unit, landmark, timezone, territory, service area, and phone while the caller can correct errors.
  </Card>

  <Card title="Schedule with constraints" icon="check-circle">
    Capture preferred window, access notes, weather risk, delivery deadline, attendee count, or cancellation reason.
  </Card>

  <Card title="Prepare field teams" icon="check-circle">
    Send site context, equipment, safety notes, parts, parking, route, and customer expectations to the owner.
  </Card>
</CardGroup>

## What DialNexa should capture for Elasticsearch

* Customer, phone, email, address, coordinates, region, timezone, booking ID, job ID, or shipment ID
* Requested time, access note, delivery status, service issue, cancellation reason, weather or route risk
* Territory, branch, technician, host, owner, SLA, and next window
* Transcript link, recording link, DialNexa call ID, calendar link, order link, map link, and ticket link
* Risk flags such as invalid address, no access, unsafe condition, VIP, or outside service area

## High-value Elasticsearch workflows

<AccordionGroup>
  <Accordion title="Delivery is at risk">
    For this scenario, DialNexa should treat Elasticsearch 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="Caller is outside service area">
    For this workflow, DialNexa should send Elasticsearch 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="Weather or travel affects timing">
    For this workflow, DialNexa should send Elasticsearch 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="Phone number needs validation">
    For this workflow, DialNexa should send Elasticsearch 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="Route or branch owner must be selected">
    For this workflow, DialNexa should confirm location details, access notes, timing constraints, and the operational owner before updating Elasticsearch. Low-confidence addresses or risky visits should go to review.
  </Accordion>

  <Accordion title="Caller provides a new address">
    For this workflow, DialNexa should confirm location details, access notes, timing constraints, and the operational owner before updating Elasticsearch. Low-confidence addresses or risky visits should go to review.
  </Accordion>

  <Accordion title="Use get index schema">
    Use get index schema 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 list indices">
    Use list indices 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 Elasticsearch with other integrations

* [Elasticsearch](/integrations/elasticsearch) + [Gmail](/integrations/gmail): Gmail for confirmations after the call.
* [Elasticsearch](/integrations/elasticsearch) + [HubSpot](/integrations/hubspot): HubSpot for account territory context.
* [Elasticsearch](/integrations/elasticsearch) + [Shopify](/integrations/shopify): Shopify for delivery or order calls.
* [Elasticsearch](/integrations/elasticsearch) + [Google Sheets](/integrations/googlesheets): Google Sheets for low-confidence address review.
* [Elasticsearch](/integrations/elasticsearch) + [Zendesk](/integrations/zendesk): Zendesk for field-service support tickets.
* [Elasticsearch](/integrations/elasticsearch) + [Google Maps](/integrations/google_maps): Google Maps for address and route context.

## Implementation notes

* Use the DialNexa call ID as the idempotency key before running Elasticsearch actions.
* Write a short operational summary into Elasticsearch 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 order data should be checked first?">
    Customer match, order ID, fulfillment status, payment status, delivery promise, prior support notes, and return eligibility.
  </Accordion>

  <Accordion title="How should damaged-item calls be handled?">
    Capture item, photo need, damage description, customer expectation, replacement or refund preference, and deadline.
  </Accordion>

  <Accordion title="Can DialNexa recover buying intent?">
    Yes. Route callers who ask about fit, availability, shipping, price, package options, or trust blockers while intent is fresh.
  </Accordion>

  <Accordion title="How should VIP buyers be prioritized?">
    Use order value, loyalty status, subscription status, repeat purchase, account tier, or urgent deadline to route faster.
  </Accordion>

  <Accordion title="What happens after a booking change?">
    Update the booking or calendar, send confirmation, log the reason, and notify operations if capacity or timing is tight.
  </Accordion>

  <Accordion title="How do you avoid acting on the wrong order?">
    Verify identity and match order ID, phone, email, product, and recent activity before making changes.
  </Accordion>

  <Accordion title="What should be sent to marketing afterward?">
    Only safe lifecycle signals such as product interest, return outcome, or follow-up need. Do not send sensitive support details.
  </Accordion>
</AccordionGroup>