MS Dynamics and Autonomy.
For dealer groups on Microsoft Dynamics, Autonomy publishes an authenticated feed of enquiries, reservations and service bookings that Storm Technology, a Microsoft solutions partner, collects into Dynamics. Each record carries the customer, vehicle, dealership and campaign tracking, mapped to Dynamics fields.
What it does.
Unlike Autonomy's other CRM integrations, this one is pull based. Nothing is pushed when a form is submitted; instead Storm polls an authenticated JSON feed of the site's enquiries, reservations and service bookings, by date range and page, and imports them into the dealer's Dynamics. Each dealership on the site carries a Dynamics hash so Storm can file records against the right location.
Form questions are mapped to Dynamics fields in the dashboard, including name, contact details, address, preferred date, contact methods, the customer's own vehicle, and a set of finance and know-your-customer fields for enquiries. Submission date, marketing preferences, UTM values, the enquired vehicle and any part-exchange valuation are added automatically. Reservations carry the amount paid and bookings carry the booking date and vehicle.
What flows where.
| Data | Direction | How often |
|---|---|---|
| Enquiries with mapped fields, vehicle, valuation, UTM values and marketing preferences | Autonomy to Dynamics (collected by Storm) | Storm polls the feed; interval set by Storm |
| Vehicle reservations, with the amount | Autonomy to Dynamics (collected by Storm) | Storm polls the feed; interval set by Storm |
| Service bookings, with the booking date and vehicle | Autonomy to Dynamics (collected by Storm) | Storm polls the feed; interval set by Storm |
Because Storm pulls the data, the enquiry shows as actioned on the platform as soon as it is submitted; if Storm stops polling, nothing on the platform side notices. Monitoring is agreed with Storm, and the API user's usage metrics show whether the feed is being read.
What the dealer sees.
Nothing changes for the customer. Records appear in the dealer's Dynamics against the right location; in the Autonomy dashboard the API usage log shows Storm's reads of the feed.
Who runs it.
Setup and ownership.
mtc. enables the Storm connector in the Autonomy dashboard, creates an API user for Storm with access to the feed routes, sets each dealership's Dynamics hash and maps the form questions. Storm holds the Dynamics-side mapping and starts polling, then both sides confirm records appear in Dynamics.
What the dealer provides
- A Storm Technology engagement for the dealer's Dynamics
- Dynamics location hashes for each dealership, supplied by Storm or the dealer's Dynamics team
- The list of Dynamics fields the dealer wants populated, including any finance or KYC fields
