CRM Connections
Connect Microsoft Dynamics so new clients and conversation notes flow into your CRM automatically. Choose the table, map fields and watch sync logs.
CRM Connections sends your clients and conversation notes to the CRM your team already uses, so nobody has to copy and paste. Today the supported business CRM is Microsoft Dynamics (Dynamics 365 / Dataverse). You can also link AutoChat CRM if your plan includes it.
Find it in the left menu under CRM > CRM Connection.
HubSpot and Salesforce connections are not available yet. Please don't plan around them. If the CRM Connection menu item is missing, or the page says connections are disabled, CRM connections aren't switched on for your account. Contact support.
What gets synced
- Contacts. Name, email, phone and company for each client.
- Notes. Conversation summaries and key insights (qualification status, buying stage and similar) are added to the CRM record.
- Anything you map yourself. For Dynamics you can choose exactly which Autoch.at details land in which Dynamics field (see below).
Connect Microsoft Dynamics
You'll need your Dynamics address (for example https://yourorg.crm.dynamics.com) and, depending on the method, your Microsoft Entra (Azure) Directory ID. Ask your IT person or Microsoft partner if you're unsure. For a checklist to get ready, see Dynamics CRM Setup.
Start
On the Microsoft Dynamics card, click Connect with Microsoft.
Enter your environment
Fill in Instance URL and Directory ID (Azure AD), then click Continue to Microsoft.
Approve
Sign in with Microsoft and approve access. You return to Autoch.at and see "Microsoft Dynamics connected successfully!". The card shows Active and "Hosted OAuth".
If the button reads Connect with OAuth, your account uses your own Microsoft app. Click it, enter Client ID, Client Secret, Instance URL and Directory ID (Azure AD), click Save OAuth Configuration, then approve access on the Microsoft page.
For a server-to-server link that doesn't depend on one person's login: click Use Service Principal, enter Client ID, Client Secret, Instance URL and Directory ID (Azure AD), then click Connect. Best for IT-managed setups.
Switching between connection methods later asks you to confirm, because it changes how Autoch.at signs in to Dynamics.
Check that it works
After connecting, use the buttons on the card:
- Test Connection checks that Autoch.at can reach Dynamics.
- Validate Setup runs a deeper check and lists each requirement as ready or needing attention. "Needs attention" usually means a sign-in or permission problem. "Sync needs attention" means sign-in is fine but the table you chose needs permission changes; the connection stays active.
- Sync Now pushes everything waiting in the queue right away. It's greyed out if Enable Sync is off.
Sync settings
| Setting | What it does |
|---|---|
| Enable Sync | Turns automatic syncing on. Conversations are queued by priority and sent in the background. |
| Qualified Leads Only | Only sends conversations that were marked qualified (see Qualification Settings). With this off, everything except spam is sent. |
| Enable Bi-directional Sync | Dynamics only. Also lets changes made in Dynamics flow back. An Inbound webhook status box shows whether it's Registered and when the last event arrived. |
| Sync Contacts | Sends contact details (name, email, phone, company). |
| Sync Notes | Adds conversation summaries and insights as notes. |
| Update Interval (minutes) | How often Autoch.at checks for new conversations to sync, from 5 to 1440. Shorter is faster but uses more of your CRM's allowance. 15 to 60 is a good range. |
Choose the Dynamics table and map fields
Once the connection shows Active, a panel called Dynamics table & field mapping appears.
Pick the table
Under Target Dataverse table, choose where clients should land. The default is contact. Use Search tables (then Refresh) to find others such as lead or account. Click Save table.
Map a field
In the row at the bottom, choose a Platform field (what Autoch.at knows), then the Dynamics field it should fill, then a Write mode, and click Add.
Remove a mapping
Click the bin icon at the end of a mapping row.
Changing the target table removes the field mappings you set up for the old table. You'll be asked to confirm first.
Platform fields you can map: Email, First name, Last name, Company, Street Address, City, State / Province, Postal Code, Country, Autochat Summary, Autochat Full Text, Autochat Notes and Workspace Identifier.
Write mode:
- Replace overwrites whatever is in the Dynamics field.
- Append adds to what's already there. Use it to put Autochat Notes into the same memo field as Autochat Summary without overwriting the summary.
With no mappings, name, email and phone use safe defaults when the table has matching fields.
Dynamics memo fields hold about 10,000 characters. If a full conversation is longer, Autoch.at keeps the newest messages and drops the oldest, starting the text with "[Earlier messages omitted to fit CRM field limit.]".
Watch the sync
The Sync Logs table at the bottom lists each sync: Time, CRM, Type, Client and Status.
- Success: your CRM is up to date.
- Pending: queued and waiting its turn.
- Failed: hover or read the short error. Autoch.at retries automatically. If it keeps failing, check the connection with Test Connection or Validate Setup.
Reconnect or disconnect
If a card shows Error or Disconnected, use the reconnect button that matches how you connected: Reconnect with Microsoft, Reconnect with OAuth or Reconnect Service Principal. For Service Principal connections, Reconnect with saved credentials restores access without retyping your environment details.
Disconnect stops syncing. Records already in your CRM stay there.