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

# Reply

> Connect DialNexa calls to Reply for lead, contact, company, deal, activity, task, or account-owner alert workflows.

Reply.io is a sales engagement platform that automates multichannel outreach, enabling users to create and manage email campaigns, track replies, and monitor performance directly within their platform.

<Note>
  Use Reply with DialNexa when a buyer, customer, partner, or account contact gives information that should change pipeline, ownership, qualification, or follow-up.
</Note>

## Where Reply fits in a DialNexa workflow

Reply should receive DialNexa output when the conversation affects a lead, contact, company, deal, activity, task, or account-owner alert. 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="Move deals with evidence" icon="check-circle">
    Update stage or activity only when the caller confirms intent, decision process, urgency, or blocker.
  </Card>

  <Card title="Route hot accounts" icon="check-circle">
    Notify the owner when an existing account calls with expansion intent, churn risk, procurement questions, or renewal blockers.
  </Card>

  <Card title="Keep CRM hygiene clean" icon="check-circle">
    Search by phone, email, company, and open opportunity before creating new records.
  </Card>

  <Card title="Record the promise" icon="check-circle">
    If DialNexa promises a callback, quote, demo, or email, create a task with owner and deadline.
  </Card>
</CardGroup>

## What DialNexa should capture for Reply

* Caller name, company, email, phone, source, owner, lifecycle stage, and CRM match confidence
* Qualification answers, pain point, objection, urgency, budget signal, and buying timeline
* Deal stage suggestion, callback window, meeting request, task owner, and due date
* Opt-out, wrong-number, duplicate, student, vendor, competitor, or low-fit flags
* Recording link, transcript link, DialNexa call ID, CRM URL, calendar URL, and email thread URL

## High-value Reply workflows

<AccordionGroup>
  <Accordion title="Renewal-risk account calls with a complaint">
    For this scenario, DialNexa should treat Reply 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="Partner or referral lead needs routing">
    In Reply, 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.
  </Accordion>

  <Accordion title="Inbound demo request from a qualified buyer">
    DialNexa should capture the preferred time, timezone, owner, promise made, and contact channel before updating Reply. The receiving team should see exactly why the follow-up exists and what the caller expects next.
  </Accordion>

  <Accordion title="Outbound call changes deal stage or urgency">
    In Reply, 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.
  </Accordion>

  <Accordion title="Existing customer asks about expansion">
    In Reply, 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.
  </Accordion>

  <Accordion title="Procurement or legal blocker appears on a call">
    For this scenario, DialNexa should treat Reply 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 asks for a callback from the account owner">
    DialNexa should capture the preferred time, timezone, owner, promise made, and contact channel before updating Reply. The receiving team should see exactly why the follow-up exists and what the caller expects next.
  </Accordion>

  <Accordion title="Use search contacts by email">
    Use search contacts by email 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 create personal list">
    Use create personal list only when DialNexa has a matched caller, a clear destination object, and enough call context to justify opening a new CRM record. If the caller is unclear, route to review instead of creating noise.
  </Accordion>
</AccordionGroup>

## Workflows that pair Reply with other integrations

* [Reply](/integrations/reply) + [Google Calendar](/integrations/googlecalendar): Google Calendar for demos and follow-up meetings.
* [Reply](/integrations/reply) + [Slack](/integrations/slack): Slack for hot-account owner alerts.
* [Reply](/integrations/reply) + [Google Sheets](/integrations/googlesheets): Google Sheets for auditing call outcomes before automation is widened.
* [Reply](/integrations/reply) + [Stripe](/integrations/stripe): Stripe for billing context before sales calls back.
* [Reply](/integrations/reply) + [Intercom](/integrations/intercom): Intercom for support history on existing customers.
* [Reply](/integrations/reply) + [Zendesk](/integrations/zendesk): Zendesk for support escalation tied to account value.
* [Reply](/integrations/reply) + [Notion](/integrations/notion): Notion for call playbooks and objection tracking.
* [Reply](/integrations/reply) + [Google BigQuery](/integrations/googlebigquery): Google BigQuery for pipeline attribution reporting.

## Implementation notes

* Use the DialNexa call ID as the idempotency key before running Reply actions.
* Write a short operational summary into Reply 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 should the CRM note sound like?">
    Short and factual: who called, why they called, what DialNexa learned, what was promised, who owns the next step, and when it is due.
  </Accordion>

  <Accordion title="Can DialNexa move deal stages automatically?">
    Yes for clear rules such as booked demo, confirmed no interest, or requested quote. Use review for high-value deals, legal blockers, procurement issues, and unclear intent.
  </Accordion>

  <Accordion title="How should low-fit leads be handled?">
    Tag the low-fit reason, suppress from sequences when appropriate, and avoid creating sales tasks that reps will ignore.
  </Accordion>

  <Accordion title="How do we prevent duplicate contacts?">
    Match by phone, email, domain, company name, and open deal before creating or updating records. Store the DialNexa call ID on the activity.
  </Accordion>

  <Accordion title="What fields matter most for sales follow-up?">
    Caller identity, company, pain, urgency, buying role, objection, requested next step, owner, and transcript link.
  </Accordion>

  <Accordion title="How should missed calls be logged?">
    Log missed-call status, voicemail summary if available, retry window, owner, and whether a human callback is required.
  </Accordion>

  <Accordion title="When should Slack be notified?">
    Notify Slack for hot accounts, enterprise prospects, renewal risk, buying intent, escalation requests, or missed VIP callbacks.
  </Accordion>
</AccordionGroup>