Car Dealership AI Stack — Reference Design and Costs
Car dealerships can miss opportunities when a lead arrives during Sunday lunch, a call rings out while every salesperson is busy or a trade-in inquiry waits overnight. A response process can help the team track those gaps; whether it leads to more appointments must be measured.
This page maps a reference architecture for a multi-brand used-car dealership in Brazil. It is a design to configure and validate, not a claim of measured production results.
What the design could automate
- Lead capture and WhatsApp reply. A permitted website, marketplace or ad lead can trigger a template-send request. Delivery depends on the integration, provider, approved template and recipient eligibility.
- Missed-call follow-up. A phone-system no-answer event can enter a follow-up process. Confirm permission to use WhatsApp and map the phone event before sending a message.
- Inventory marketing — separate implementation. An inventory integration could prepare listing drafts for human review. Inventory posting, image generation and cross-platform listing updates are not included in the downloadable pack.
- Follow-up cadence. The paid reference workflow schedules day-1, day-3 and day-7 checks. Validate reply detection and recipient suppression before enabling any follow-up; it is not continuous inbox monitoring.
The stack and its real monthly cost
| Job | Tool | Monthly cost |
|---|---|---|
| WhatsApp API + team inbox | AiSensy for budget-first tests; Wati or respond.io for broader inbox needs | ~$16–79 |
| Workflow engine | n8n — self-hosted on a small VPS | ~$6 (VPS) or $23 cloud |
| AI copy and image handling | LLM API usage inside n8n | $5–20 |
| Voice answering (optional) | Retell AI when calls overflow | ~$0.11/min used |
Estimated total: roughly $22–122/month for the core, before Meta message charges. Validate with your country, volume and provider. Use the lead recovery ROI calculator without treating its estimate as guaranteed revenue.
Budget-first WhatsApp test: try AiSensy. Start with one approved template and one lead source.
Controls the implementation needs
- Require approval for publishing. If you add inventory marketing, review factual details and images before publishing. That publishing integration is separate from the pack.
- Disclose automation and arrange a real handoff. The copy should describe what the system and sales team actually do.
- Separate send acceptance from delivery. Record provider status, replies, opt-outs and booked appointments, not just webhook runs.
- Use a permitted channel. Confirm that the recipient expects WhatsApp contact; a phone number or missed call is not sufficient evidence on its own.
Build it yourself
The lead follow-up and missed-call workflows are available as n8n reference templates on our templates page. The paid dealership pack contains a JSON workflow and guide with scoring, vehicle-interest capture and reply checks before day-1/3/7 follow-ups. It does not include inventory posting. Configure and test the provider integration before production. The general-purpose version of the architecture is documented in the lead follow-up stack.
Affiliate note: some links are affiliate links. This page labels the design and assumptions; commission does not prove a tool is suitable for your dealership.