Integrations · MIA and CarTake
Integrations with the systems your dealership already uses
MIA and CarTake don't ask you to change CRM, phone system, or multipublisher. They connect to the existing stack: MIA reads stock and CRM and writes conversations, notes, and appointments where the team works; CarTake delivers processed photos to the multipublishers that push them to website and portals. This page lists available integrations and the method we use to verify new ones.
CRM, stock, channels, and lead sources
To qualify a request well, MIA needs to know what's in stock, who is already in the CRM, and which process should start next. Integrations exist for this: real data in, orderly actions out.
CRM and lead management
MIA integrates with the automotive CRMs most used in Italy to record the conversation in the customer's context: record, summary, vehicle of interest, stage, team notes, activity or appointment according to the agreed integration.
- Lead creation or update with source and channel
- Conversation summary and collected information
- Vehicle of interest linked to stock
- Stage, notes, activities, and appointment where integration allows
Phone system and telephony
The available telephony integration is 3CX. MIA handles inbound and outbound voice conversations; 3CX continues to govern numbers, queues, and routing. Transfers to BDC, sales, or Service use the phone system's rules. For other providers, the connection method is verified per project; compatibility is not assumed.
Learn more: AI phone agent for dealerships
Conversation channels
Each channel has a dedicated page explaining flows, human control, and limits. Here is the technical connection scope.
WhatsApp Business (API and Coexistence)
MIA runs on the WhatsApp Business API. With Coexistence, the WhatsApp Business app on the phone and the API connected to MIA share the same number: the team keeps using the app, MIA adds shared inbox and automations.
Website chat
Widget installed on the dealer website, with page and vehicle context: the conversation starts from the listing the visitor is viewing.
Voice and 3CX phone system
MIA handles the conversational layer of inbound and outbound calls. With 3CX the integration is already available; number and other phone systems are verified per project.
Stock, portals, lists, and tracking
The sources feeding conversation context and the systems receiving its events.
Stock: XML, JSON feed or API
Availability and location, prices, promotions, trims, photos, and vehicle details. MIA answers on real data, not generic descriptions.
AutoScout24 listings → vehicle in stock
With MIA's WhatsApp number in listings, every conversation starts from the right vehicle: MIA recognizes the source listing and links it to the dealer's stock.
Learn moreLists for outbound campaigns
Import from CSV, XML, CRM, DMS, or API to segment and start one-to-one WhatsApp conversations within collected consents.
Learn moreGA4, ad pixels, and ASC events
MIA tracks exchanged messages and lead generation and can send events to GA4 and the pixels configured by the dealership.
Learn moreCalendar and DMS
Slot lookup, appointment recording, and job status for sales and Service depend on the integration available in the dealer's environment and are defined per project.
Learn moreFrom the lot to portals, no manual uploads
Photos processed by CarTake Photo, cut out and placed in the Digital Room, don't need to be downloaded and re-uploaded: they are delivered automatically to integrated multipublishers, which distribute them to website and listing portals.
Integrated multipublishers
Three active integrations cover the multipublishers most used by Italian dealerships. From there, images reach the dealer website and portals such as AutoScout24 and Subito.it.
- 01
Guided capture with the CarTake Photo app
- 02
AI processing: cut-out, Digital Room, logo
- 03
Automatic delivery to SmilePhotoWeb, Infinity Publisher, or WEICOLA
- 04
Distribution to website and portals through the multipublisher
CarTake Photo ↔ CarTake Studio
The most direct integration is inside the platform: every photo processed by CarTake Photo appears in the CarTake Studio asset library, the visual editor for social, ads, and website creatives. No file handoff between the two tools.
Discover CarTake StudioMethod
How we verify an integration before activating it
An 'available' integration isn't the same in every dealership: versions, permissions, and configurations differ. Every project follows the same four steps.
- 01
Stack map
CRM, DMS, stock, calendar, PBX, multipublisher, and active channels: what exists, who manages it, which accesses are available.
- 02
Available reads and actions
For each system we define what MIA or CarTake can read and write, separating what is verified from what needs setup.
- 03
Test on the real environment
Trial with the dealer's data and accounts: a test lead in the CRM, a photo delivered to the multipublisher, a routed call.
- 04
Activation and monitoring
Scope declared in writing, activation on agreed channels, and flow monitoring in the first weeks.
MIA and CarTake integrations: frequently asked questions
CRM not listed, phone system, synced data, portals, and timing: the most common questions before a project.
Listed integrations are those already available. For other systems we assess feasibility on the specific environment: it depends on the vendor's API or data exchange options and the dealership's accesses. Scope is defined before activation, not promised upfront.
According to the agreed integration: lead creation or update with source and channel, conversation summary, vehicle of interest, stage, team notes, activity or appointment. Only actions actually available in the dealer's CRM are declared.
If the dealership uses 3CX, MIA connects to that phone system without replacing it. Number, provider, and other PBXs are verified before the architecture is defined: MIA can join the existing flow or require a dedicated configuration.
Yes. 3CX is the available telephony integration: MIA handles the conversation, 3CX continues to govern numbers, queues, and routing. Transfers and schedules are configured on the dealer's environment.
Yes. With WhatsApp Coexistence, the WhatsApp Business app and the API connected to MIA share the same number: the team uses the app for daily conversations, MIA adds shared inbox and automations on the API channel.
Yes, through integrated multipublishers: CarTake delivers images to SmilePhotoWeb, Infinity Publisher, or WEICOLA, which distribute them to website and portals like any other listing photo, with no manual uploads.
It depends on the integration available in the dealer's environment. When calendar and DMS expose the needed operations, MIA can look up slots, record appointments, or read statuses; otherwise it collects the complete request and passes it to the team.
Related pages
Dealership CRM AI
How MIA works inside the sales process and the existing CRM.
WhatsApp for dealerships
Coexistence, outbound campaigns, and team control.
AI phone agent for dealerships
Voice, routing, and connection with existing telephony.
AI for Service and workshop
Workshop calendar, DMS, and after-sales requests.
Dealership car photo app
The guided capture that feeds the multipublishers.
CarTake Studio
The visual editor connected to stock photos.
Want to know what connects in your case?
In the demo we map your dealership's CRM, stock, channels, calendar, and multipublisher and tell you what's available now and what needs setup.
Check your stack in a demo