Integrations · MIA and CarTake

Integrations with the systems your dealership already uses

Check your stack in a demoDiscover MIADiscover CarTake

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.

MIA · AI agent for leads, WhatsApp, and voice

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 sends the lead to the CRM with the conversation context. Salesforce via Web-to-Lead or REST API; Walcu also with live salesperson availability to route callbacks; Action and TCar/Trock via direct push. For other CRMs there is a webhook with field mapping.

  • Lead with source, channel, source page, UTM, and gclid
  • Conversation summary and transcript link
  • Vehicle of interest and trade-in details collected in the conversation
  • Automatic retry on errors and CRM ID saved back in MIA
Learn more: dealership CRM AI

Phone system and telephony

MIA doesn't replace your phone system. With 3CX, MIA connects through Twilio: numbers, queues, and extensions stay yours. With other phone systems, calls reach MIA by forwarding. MIA's voice runs on Twilio; when needed, MIA forwards the call to the team by rules and hours. Forwarding and transfers are verified in a demo on your phone system.

Learn more: AI phone agent for dealershipsAI outbound calls
  • 3CX connected through Twilio; other phone systems by forwarding
  • Numbers stay the dealership's
  • Inbound calls and AI outbound calls, with recordings and transcripts
  • Forward to the team by request type, brand, hours, or salesperson availability

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)

Meta WhatsApp Cloud API with Embedded Signup: the dealer connects the number on their own. Alternatively, Spoki. With Coexistence, where the account allows it, the team keeps using the app on the same number: messages sent from the app appear in MIA and the AI pauses on that conversation. Several numbers per site or department.

Website chat

Widget installed on the dealer website, with page and vehicle context: the conversation starts from the listing the visitor is viewing.

Voice (Twilio)

Answering inbound calls and placing AI outbound calls. 3CX connects through Twilio, other phone systems by forwarding; numbers stay yours. Recordings and transcripts land in the inbox.

Email (Resend)

Outbound email, with customer replies coming back into the same conversation. Block-based newsletters with unsubscribe handling.

Stock, lead sources, APIs, and tracking

The sources feeding conversation context and the systems receiving its events.

Guide: 7 WhatsApp workflows in the dealership

Account, number, templates, CRM and Human Control; opt-in, 24-hour window and the seven operational flows (vehicle, after hours, qualification, test drive, Service, follow-up).

Learn more

Stock: JSON feed and Eurotax

Sync from any JSON API feed (hourly, daily, or weekly) and the Eurotax trim catalogue. MIA answers on real prices, offers, and availability.

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 more

Facebook and Instagram Lead Ads

Leads from Meta forms are imported automatically every few minutes, and MIA can contact them right away on WhatsApp or by phone.

Learn more

Click-to-WhatsApp ads

MIA records the ad a WhatsApp conversation started from and also links website-to-WhatsApp journeys to the lead.

Learn more

Webhooks, data API, and public API

Webhook with field mapping for any CRM, a read-only data API, and a public API to send WhatsApp templates or start flows, including an AI call, from external systems.

Campaign audiences

Segments and RFM segmentation built on MIA's CRM, or a start from an external system via API. WhatsApp campaigns and AI calls within collected consents.

Learn more

Website tracking, GA4, and ASC events

First-party website tracking (visits, sources, UTM, forms, chats opened) and ASC v1.1 chat events pushed to the site's GA4 dataLayer.

Learn more

Calendar

MIA has its own calendar for sales and workshop (services, locations, resources, shifts) where it books and sends reminders. It does not sync with Google Calendar or Outlook.

Learn more
CarTake · Stock photos and visual marketing

From 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.

  1. 01

    Guided capture with the CarTake Photo app

  2. 02

    AI processing: cut-out, Digital Room, logo

  3. 03

    Automatic delivery to SmilePhotoWeb, Infinity Publisher, or WEICOLA

  4. 04

    Distribution to website and portals through the multipublisher

How the CarTake Photo capture app works

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 Studio
Let's look at your multipublisher

Method

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.

  1. 01

    Stack map

    CRM, DMS, stock, calendar, PBX, multipublisher, and active channels: what exists, who manages it, which accesses are available.

  2. 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.

  3. 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.

  4. 04

    Activation and monitoring

    Scope declared in writing, activation on agreed channels, and flow monitoring in the first weeks.

Integrations FAQ

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.

No. Calls reach MIA by forwarding from the phone system you already use, and numbers stay the dealership's. Forwarding rules and transfers to the team are verified in a demo on your system.

Yes. MIA connects to 3CX through Twilio: 3CX keeps managing numbers, queues, and extensions, MIA answers when configured and hands the call to the team. The setup is verified in a demo.

Yes. With the public API an external system can send a WhatsApp template or start a flow, including an AI call. Webhooks report events and a read-only API exposes the data.

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.

MIA has its own calendar for sales and workshop, where it checks slots, books, and sends reminders; it does not sync with Google Calendar or Outlook. From the DMS it reads stock through a JSON feed; other DMS integrations are not available today.

Related pages

WhatsApp automation in dealerships

7 operational workflows: account, number, templates, CRM, Human Control and handoff.

Dealership CRM AI

How MIA works inside the sales process and the existing CRM.

Dealership lead management

From first contact and qualification to the BDC and CRM.

WhatsApp for dealerships

Coexistence, outbound campaigns, and team control.

AI phone agent for dealerships

Voice, routing, and connection with existing telephony.

AI outbound calls

Callbacks and voice campaigns with a script, retries, and recorded outcomes.

WhatsApp marketing

Meta-approved templates, with replies handled by the AI.

AI for Service and workshop

Workshop calendar, DMS, and after-sales requests.

Dealership car photo app

The guided capture that feeds the multipublishers.

Digital Room

The virtual showroom applied to stock photos.

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