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

# Dynamics 365

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

Dynamics 365 from Microsoft combines CRM, ERP, and productivity apps to streamline sales, marketing, customer service, and operations in one integrated platform.

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

## Where Dynamics 365 fits in a DialNexa workflow

Dynamics 365 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="Record the promise" icon="check-circle">
    If DialNexa promises a callback, quote, demo, or email, create a task with owner and deadline.
  </Card>

  <Card title="Qualify callers" icon="check-circle">
    Capture pain, role, budget signal, timeline, objection, source, and next step before a rep follows up.
  </Card>

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

## What DialNexa should capture for Dynamics 365

* 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 Dynamics 365 workflows

<AccordionGroup>
  <Accordion title="Existing customer asks about expansion">
    In Dynamics 365, 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 Dynamics 365 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 Dynamics 365. The receiving team should see exactly why the follow-up exists and what the caller expects next.
  </Accordion>

  <Accordion title="Wrong-number or low-fit lead should be suppressed">
    When this happens, DialNexa should mark the record as a suppression or cleanup case in Dynamics 365. Include the exact reason, caller identity, source, and whether future outreach should stop so the team does not keep chasing a bad or unwanted contact.
  </Accordion>

  <Accordion title="Renewal-risk account calls with a complaint">
    For this scenario, DialNexa should treat Dynamics 365 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 Dynamics 365, 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 Dynamics 365. The receiving team should see exactly why the follow-up exists and what the caller expects next.
  </Accordion>

  <Accordion title="Use create account">
    Use create account 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>

  <Accordion title="Use update case">
    Use update case when the caller changes a field, status, owner, date, priority, note, consent choice, or next step on an existing Dynamics 365 record. Include the old value, new value, and reason from the call.
  </Accordion>
</AccordionGroup>

## Workflows that pair Dynamics 365 with other integrations

* [Dynamics 365](/integrations/dynamics365) + [Intercom](/integrations/intercom): Intercom for support history on existing customers.
* [Dynamics 365](/integrations/dynamics365) + [Zendesk](/integrations/zendesk): Zendesk for support escalation tied to account value.
* [Dynamics 365](/integrations/dynamics365) + [Notion](/integrations/notion): Notion for call playbooks and objection tracking.
* [Dynamics 365](/integrations/dynamics365) + [Google BigQuery](/integrations/googlebigquery): Google BigQuery for pipeline attribution reporting.
* [Dynamics 365](/integrations/dynamics365) + [Gmail](/integrations/gmail): Gmail for the exact recap promised on the call.
* [Dynamics 365](/integrations/dynamics365) + [Google Calendar](/integrations/googlecalendar): Google Calendar for demos and follow-up meetings.
* [Dynamics 365](/integrations/dynamics365) + [Slack](/integrations/slack): Slack for hot-account owner alerts.
* [Dynamics 365](/integrations/dynamics365) + [Google Sheets](/integrations/googlesheets): Google Sheets for auditing call outcomes before automation is widened.

## Implementation notes

* Use the DialNexa call ID as the idempotency key before running Dynamics 365 actions.
* Write a short operational summary into Dynamics 365 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 Slack be notified?">
    Notify Slack for hot accounts, enterprise prospects, renewal risk, buying intent, escalation requests, or missed VIP callbacks.
  </Accordion>

  <Accordion title="Should every call create a new CRM record?">
    No. Search contacts, companies, deals, and open tasks first. Create a new record only when the caller is new or the call changes pipeline, ownership, qualification, or follow-up.
  </Accordion>

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