Take your live chat to the next level by harnessing the power of Microsoft Dynamics. Provide your agents the ability to search and create Microsoft Dynamics records from within with the Velaro console. 

Velaro can also capture and save conversation transcripts to Dynamics CRM, providing your team with a complete view of all your customer interactions. 

Install Dynamics 

To start the setup, log into Velaro as an administrative user and navigate to the Account Setup > Account > Integrations tab. Find the Microsoft Dynamics card and select Install.

First, input your Dynamics Resource URL. This should be the primary URL you see when logged into your Dynamics account; e.g.: https://[company].crm.dynamics.com/. 

Next we'll need your Discovery Source URL. Log into your Dynamics account with user who can access the Settings > Customization > Developer Resources section. Copy the Discovery Resource URL and set it on appropriate field in Velaro. 

**If your Dynamics account utilizes multi-tenant setup, you will need to also include your account's Unique Name which can also be found in the Developer Resources section.**

Now enter your Dynamics username and password and select Connect. Now that you are connected you should see your Dynamics account number and a few global options:

• Require users to select a CRM record per engagement – If enabled this will require that a CRM record is selected for every chat that occurs. This means your agents will always need to open an existing record or create a new record in order to archive the chat transcript to that record.
• Require users to save their transcripts to the CRM record per engagement – If enabled this will require the chat transcript to be posted to Dynamics. Agents will not be able disable this.

Mapping record types

Velaro lets you select what record types should be used in the integration, and even what fields you want to be accessible. To map the data fields in a record type, select the + Record Type button.

Velaro supports Dynamics' record types for Leads, Contacts, Accounts, and Tickets. To specify the type of record you need defined just select it from the first drop down. The record name is displayed to agents when they are selecting what record type to create.

The next step in creating a record in Velaro is to define the fields that go along with it. Simply select the empty Field drop down in your table, this will open up a list of all fields that belong to that record type.

The rest of the columns in the table pertain to how Velaro handles the field. 

• Linked to – This allows you to link a field value to data within Velaro. Select this and you'll be prompted to choose from Velaro's visitor monitoring data or from the pre-chat survey. Linking data to fields helps your agents by cutting out some what they need to enter while creating records.
• Create – Enabling this means this field is needed to create the record, it will be displayed to the Agent when they create a new record.
• Used for searching – This enables you to search Dynamics based on certain fields. We recommend selecting fields that have unique values such as E-Mail or Company name so that your agents get accurate results.
• Show when selected – This enables you to choose what is shown to Agents when they have a record selected either by searching or creating.
• Control – Select what type of input should be used when creating or editing this field. Dynamics supports some custom types such as the Company lookup, which are listed as their own Control type. If you select a list you will also see a pencil icon which allows you to define the contents of the list.
• Default value – If using a list, you can define the default value here.

Once you have your fields set you can change the order with the drag and drop icon on the left of each row. When you're all set select Save.

Using the Dynamics Integration

Your agents now have access to the Dynamics integration while in a chat. To access Dynamics, select Microsoft Dynamics from the drop down at the top of your right engagement panel. 

Upon first login, your agents will be prompted to log into Dynamics. If you have Active Directory Single Sign On (SSO) setup in Velaro, you agents will not need to login separately to Dynamics. Agents can search Dynamics directly in the main section.

Once your agent is signed into Dynamics through Velaro, when a new chat comes in, Velaro will automatically search for the chat visitor in Dynamics based on the data fields you have mapped for that record type. 

Or the agent can select the New button on the bottom right and create a new record in Dynamics.

Data fields that have been mapped to create a record in the integration will automatically be populated from the chat.  Once you create a record, or select one by searching, the chat transcript and any mapped data fields will be displayed.

Connecting With Microsoft OAuth 2.0 (Optional)

By default, Velaro connects to Dynamics using a single Service Account — one Dynamics username and password shared by every agent. If you'd rather not maintain a shared password, you can optionally connect using Microsoft OAuth 2.0 instead. This is completely optional: connecting it never removes or disables your existing Service Account, and your current setup keeps working exactly as it does today unless you take the extra steps below.

There are two separate things you can do here, and they don't affect each other:

1. Individual agents can connect their own Microsoft account

Under Microsoft OAuth 2.0 connection, any agent can click Let agents connect their own Microsoft accounts and sign in with their own Microsoft login. Once an agent does this, their own actions are always attributed to their own account — every record they search for, create, or update in Dynamics shows them as the author, permanently, for as long as that connection stays in place. This can't be turned off or overridden by anything else on this page; it's entirely up to each individual agent whether they connect.

2. The site can set a different shared default for everyone else

Agents who haven't personally connected their own account (per #1) use a single shared identity for their Dynamics actions — today, that's your Service Account. If you'd rather that shared identity also be a modern Microsoft OAuth 2.0 connection instead of a username and password, an administrator can click Connect with Microsoft (as me) to sign in once, then check Default connection for agents without their own login further down the page. On its own, clicking Connect only sets up background record creation for missed chats and bot conversations — checking that setting is what switches your agents' live, in-chat actions over to it too. Turning it off at any time switches back to your Service Account, with no data lost either way.

Do agents need to individually log in to use Velaro's Dynamics integration at all? No. By default, every agent shares one connection (your Service Account, or the site-level OAuth connection if you've switched to it) and nobody has to sign in individually. Connecting an individual Microsoft account (#1 above) is entirely optional, for customers who specifically want each agent's own Dynamics activity attributed to them by name.