Microsoft Dynamics 365 Sales call tracking integration

It puts your calls in Dynamics 365 Sales. After each call, Nimbata looks the caller up in Dynamics by phone number across contacts, accounts and leads. A new caller becomes a lead with a phone call activity regarding it, and a known caller gets a phone call and a repeat caller task on their record, with the call data you choose mapped to Dynamics fields.

Open Integrations in Nimbata, choose Dynamics 365 Sales and sign in with your Microsoft account. Pick your Dynamics environment from the list Nimbata finds; it stays set until you disconnect. Then add Dynamics as a step in a call workflow and choose its conditions and field mapping. There's no code to write, and a project can keep several configurations.

Yes, for new callers. When no record matches the caller's number, Nimbata creates a lead with the caller's number as its business phone, and an incoming phone call, named new phone call, regarding it. Map the caller's name to the lead's name fields; otherwise the lead is named Nimbata Lead.

Nimbata searches contacts, accounts and leads for the caller's number, on their business phone, mobile phone and address phone fields, both as given and as the national number, and logs the call on the record it finds instead of creating a new one. You choose which comes first, contacts, leads or accounts, or all of them (the default). When a number matches more than one record, you choose whether to handle the first match, all of them, or none.

By default, a phone call activity with the caller's number, and for a repeat caller a task named repeat caller, both regarding the caller's record. Beyond that, you map any of Nimbata's call fields to the fields of contacts, accounts, leads, phone calls and tasks, custom fields and picklists included, and you can update the fields of a record Nimbata matched. Durations go in minutes.

Yes. The source, campaign, landing page, call page, UTM fields and Google, Meta and Microsoft click IDs (gclid, fbclid, msclkid) can all be mapped to fields on the lead, contact, account or phone call, so your Dynamics views and reports can show calls by campaign.

Yes. Map the transcription, the AI summary and the fields Nimbata AI fills to Dynamics fields, and write text fields with your own words mixed with call variables. Recordings go as a link to the call in Nimbata, so your team can listen from the record; the audio file stays in Nimbata.

No. Nimbata creates leads, phone calls and tasks, and updates the contacts, accounts and leads it matches. It doesn't create or update opportunities.

Yes. Dynamics is a step in a Nimbata workflow, so you set its conditions, such as the call's outcome or duration, first-time callers, source or campaign, tags, value, rating, or an answer Nimbata AI found on the call. Only the calls that meet them reach Dynamics.

Outbound calls, yes. Dynamics can be a step in workflows for both inbound and outbound calls, run when a call starts, when it ends or by hand. Form submissions and text messages don't go to Dynamics directly; send them on with Zapier or a webhook instead.

Yes. A workflow can read a value from the caller's Dynamics contact, account or lead into a Nimbata property, so your call reports can use what your CRM already knows.

If Dynamics refuses Nimbata's sign-in, Nimbata refreshes it once; if that fails, it disconnects the integration and emails you to reconnect Microsoft Dynamics. If Dynamics can't be reached while Nimbata looks the caller up, the call isn't sent, so no duplicate is created, and the attempt is logged. On the Agency plan, the Integration Events log shows every attempt.

The Marketing and Agency plans, and the 14-day free trial. See pricing for everything else each plan includes.