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

# Livesession

> Connect DialNexa calls to Livesession for row, dataset, lookup result, enrichment record, dashboard event, warehouse record, or review queue workflows.

LiveSession is a session replay and user behavior analytics tool that helps you understand how users interact with your website.

<Note>
  Use Livesession with DialNexa when spoken context should become structured data that teams can query, enrich, report on, or review.
</Note>

## Where Livesession fits in a DialNexa workflow

Livesession should receive DialNexa output when the conversation affects a row, dataset, lookup result, enrichment record, dashboard event, warehouse record, or review queue. 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">
    Route low-confidence matches, missing data, suspicious lookups, and edge cases for review.
  </Card>

  <Card title="Power reporting" icon="check-circle">
    Track call reasons, qualified outcomes, missed-call impact, churn risk, and conversion quality.
  </Card>

  <Card title="Normalize call outcomes" icon="check-circle">
    Store intent, category, urgency, product, owner, and next action in fields reporting can trust.
  </Card>

  <Card title="Join call context" icon="check-circle">
    Match phone or email to CRM, product, billing, support, account, or external IDs before syncing.
  </Card>
</CardGroup>

## What DialNexa should capture for Livesession

* Caller ID, contact ID, account ID, source system, external ID, and match confidence
* Structured outcome, intent, category, sentiment, urgency, product, region, and owner
* Lookup result, enrichment value, qualification fields, revenue signal, support reason, and next action
* Timestamp, duration, transcript URL, recording URL, DialNexa call ID, and raw payload reference
* Data quality fields such as duplicate status, missing fields, confidence, and review needed

## High-value Livesession workflows

<AccordionGroup>
  <Accordion title="Warehouse needs transcript-linked rows">
    For this scenario, DialNexa should send structured fields into Livesession: matched identity, lookup result, confidence, timestamp, and the decision that depends on it. Keep full transcripts linked, not copied.
  </Accordion>

  <Accordion title="Duplicate data should be cleaned">
    For this scenario, DialNexa should send structured fields into Livesession: matched identity, lookup result, confidence, timestamp, and the decision that depends on it. Keep full transcripts linked, not copied.
  </Accordion>

  <Accordion title="Call outcome should enter reporting">
    For this scenario, DialNexa should send structured fields into Livesession: matched identity, lookup result, confidence, timestamp, and the decision that depends on it. Keep full transcripts linked, not copied.
  </Accordion>

  <Accordion title="Caller needs enrichment before routing">
    For this scenario, DialNexa should send structured fields into Livesession: matched identity, lookup result, confidence, timestamp, and the decision that depends on it. Keep full transcripts linked, not copied.
  </Accordion>

  <Accordion title="Low-confidence record needs review">
    For this workflow, DialNexa should send Livesession 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="Campaign quality should be measured">
    DialNexa should send Livesession the source, consent state, call outcome, audience impact, and suppression or enrollment decision. The goal is better targeting, not another generic campaign touch.
  </Accordion>

  <Accordion title="Support reasons need trend analysis">
    For this workflow, DialNexa should send Livesession 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 list live sessions">
    Use list live sessions 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 Livesession with other integrations

* [Livesession](/integrations/livesession) + [Intercom](/integrations/intercom): Intercom for conversation context.
* [Livesession](/integrations/livesession) + [Notion](/integrations/notion): Notion for reporting notes.
* [Livesession](/integrations/livesession) + [BigQuery](/integrations/googlebigquery): BigQuery for central reporting.
* [Livesession](/integrations/livesession) + [HubSpot](/integrations/hubspot): HubSpot for customer and deal context.
* [Livesession](/integrations/livesession) + [Google Sheets](/integrations/googlesheets): Google Sheets for manual review queues.
* [Livesession](/integrations/livesession) + [Slack](/integrations/slack): Slack for alerts on urgent records.
* [Livesession](/integrations/livesession) + [Zendesk](/integrations/zendesk): Zendesk for support category analysis.
* [Livesession](/integrations/livesession) + [Google Analytics](/integrations/google_analytics): Google Analytics for source attribution.

## Implementation notes

* Use the DialNexa call ID as the idempotency key before running Livesession actions.
* Write a short operational summary into Livesession 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 should schema changes be managed?">
    Version fields, document meanings, and test downstream dashboards before changing production payloads.
  </Accordion>

  <Accordion title="Should full transcripts go into data tools?">
    Usually no. Store structured fields, summaries, and links to restricted transcripts.
  </Accordion>

  <Accordion title="What fields make reporting useful?">
    Intent, category, source, owner, outcome, urgency, customer ID, timestamp, and DialNexa call ID.
  </Accordion>

  <Accordion title="How should low-confidence matches be handled?">
    Send them to a review queue with match reason, confidence, candidate records, and transcript link.
  </Accordion>

  <Accordion title="Can DialNexa enrich callers before routing?">
    Yes, if the lookup is fast and confidence is visible. Use fallback routing when enrichment fails.
  </Accordion>

  <Accordion title="How do we avoid stale data decisions?">
    Include lookup timestamp, source, confidence, and expiration rules.
  </Accordion>

  <Accordion title="What should analysts audit first?">
    Conversion labels, spam suppression, duplicate matching, missing owners, and high-impact categories.
  </Accordion>

  <Accordion title="When should a record be rejected?">
    Reject or review records with missing identity, conflicting external IDs, impossible values, or sensitive data in the wrong destination.
  </Accordion>
</AccordionGroup>