Enterprise DNA

Instead of Salesforce Automotive Cloud

Stop renting Salesforce Automotive Cloud. Own your vehicle recall desk.

We build your version around how your recall coordinators work, bring your agreed Salesforce history across and run it for you. Keep the approved campaign scope, dealer handoffs and evidence in a database you own.

Salesforce lists Core at US$300 per user/month, billed annually. That is US$3,600 per user/year before add-ons. This free version covers the recall desk, with your wider requirements scoped separately.

Get your version built See it working
  • check_circleYour data in a database you own
  • check_circleOpen source, no lock-in
  • check_circleBuilt and run by Enterprise DNA

What the subscription covers

A broad automotive suite priced by the user

Compare the parts your recall team uses with the wider suite you license. Start with affected vehicles, contact history, dealer coordination and evidence.

paid

Core seats

Core is listed at US$300 per user/month, billed annually. Each licensed coordinator adds another seat.

layers

Advanced editions

Advanced is US$500 per user/month and Service Max is US$700, billed annually. Check which edition your operation actually needs.

extension

Service lifecycle add-ons

Salesforce lists Asset Service Lifecycle Management at US$75 per user/month, billed annually. Confirm availability and inclusion against your agreement.

directions_car

Work beyond the recall desk

Automotive Cloud covers vehicle relationships, warranties and service activity. This alternative concentrates on recall coordination and evidence.

assignment

A prescribed recall process

Salesforce Recall Inquiry links an open recall to a preferred partner and creates a service case. Your owned version follows your approved handoff process.

history

The work of bringing history across

A configured report can export the affected-vehicle records. Evidence files, existing messages and permissions need a migration plan of their own.

What your version does

Every affected vehicle has a next step

Triage

See which vehicles need attention

Review unresolved work across campaigns, coordinators and regions without rebuilding the same meeting pack each week.

  • check Affected vehicles linked to their official campaign
  • check Overdue follow-ups alongside missing dealer assignments
  • check Imported history kept separate until reconciled
  • check Ask which regions have unresolved vehicles with no dealer

Contact

Follow the owner contact through

Record a contact that happened, keep its reference and set the next follow-up. The record tells the next coordinator where to begin.

  • check Attempted, reached, returned and wrong-contact outcomes
  • check The last contact date for each vehicle
  • check Follow-up dates and named coordinators
  • check Ask which vehicles have repeated unsuccessful attempts

Evidence

Verify the remedy before completing the case

A workshop evidence reference and a separate reviewer decision sit beside the affected vehicle. A copied status never completes a case.

  • check Assigned dealer and dated remedy evidence
  • check A verifier label separate from the recorder
  • check Rejected evidence returns the case to open work
  • check Ask where evidence is waiting across several dealers

Reporting

Bring the campaign review together

Generate internal progress and handoff documents from the same records. Your responsible team reviews and submits through its approved process.

  • check Campaign totals with active and imported work separated
  • check Agreed next reporting dates
  • check Branded progress, dealer handoff and evidence worksheets
  • check Ask which reports are due while affected vehicles remain unresolved

Make it yours

Design your own Salesforce Automotive Cloud replacement

Everything starts from the open-source base. Then it gets your name, the parts you run, your rules and your data from Salesforce Automotive Cloud. Try it here, and we build the real one.

2. What it runs

3. Make it fit

4. Your colour

Your business · your Salesforce Automotive Cloud replacement Your version
YB Your business

auto_awesome

Answered from your own database

Build my version

We build it from the open-source base, bring your Salesforce Automotive Cloud data across and run it for you.

What it looks like

Ask it like you would ask a colleague

Real answers from the demo data that ships with Vehicle Recalls for Claude Code. It runs in Claude Code inside the Claude app, so it feels like any chat you already use.

forum

Vehicle Recalls for Claude Code

Connected to your own database

Which vehicles need someone to act?

DEMO-AU-01

Vin
TST00000000000001
Coordinator
Mia Chen
Dealer
Demo Harbour West
Due on
2026-10-17
Reason
appointment missed

DEMO-AU-01

Vin
TST00000000000001
Coordinator
Mia Chen
Dealer
Demo Harbour West
Due on
2026-10-17
Reason
overdue follow-up

DEMO-AU-01

Vin
TST00000000000002
Coordinator
Mia Chen
Due on
2026-10-18
Reason
dealer not assigned

DEMO-AU-01

Vin
TST00000000000002
Coordinator
Mia Chen
Due on
2026-10-18
Reason
no contact recorded

DEMO-AU-01

Vin
TST00000000000002
Coordinator
Mia Chen
Due on
2026-10-18
Reason
overdue follow-up

DEMO-AU-02

Vin
TST00000000000003
Coordinator
Noah Reed
Dealer
Demo Southern Service
Due on
2026-10-24
Reason
remedy evidence awaits verification

DEMO-NZ-01

Vin
TST00000000000006
Coordinator
Noah Reed
Dealer
Demo Harbour Service
Due on
2026-10-24
Reason
no contact recorded

DEMO-AU-02

Vin
TST00000000000004
Coordinator
Noah Reed
Due on
2026-10-26
Reason
unreconciled import

Ask it anything

Ten questions your recall desk answers today

These reports are included in the free version. Your own questions and rules shape the version we build for you.

chat_bubble Which coordinators have overdue affected vehicles?
chat_bubble Which campaigns combine missing notification evidence with unresolved vehicles?
chat_bubble Which dealers have missed appointments?
chat_bubble Which vehicle owners have had no recorded contact?
chat_bubble Which campaigns have imported completed claims that remain unverified?
chat_bubble Where is remedy evidence waiting on a separate reviewer?
chat_bubble Which regions have unresolved vehicles without a dealer?
chat_bubble Which progress reports are due with unresolved vehicles?
chat_bubble Which vehicles have repeated contact failures?
chat_bubble Which vehicles appear in more than one unresolved campaign?

Switching

How to switch from Salesforce Automotive Cloud

A move involves exporting campaign records, mapping the fields and history you want to keep, then checking the imported records before you make the new database your source of truth.

  1. 1

    Export each campaign

    Ask an authorised Salesforce administrator to prepare a Details Only CSV report for each campaign. Use the reports to export the campaign and affected-vehicle records you want to bring across. Check with Salesforce Automotive Cloud if you need help with the report or export. Decide separately which evidence files, messages and other history you need, since they require separate migration work.

  2. 2

    Load a test report

    Start with a dry run of a configured campaign report before loading records into the new recall database. Review the result, then have the operator run the import for real when the report is ready. The import validates the affected vehicles, rolls back errors and skips identical source rows. Keep the original Salesforce export available for comparison.

  3. 3

    Review import findings

    Check the validation results and any records that need reconciliation. Compare affected vehicle identification numbers and counts with the Salesforce export. An imported Completed status stays as history until you reconcile the record, so do not treat it as active work automatically. Your authorised people still make safety decisions and campaign closure decisions.

  4. 4

    Run both side by side

    Keep Salesforce Automotive Cloud available for a short period while your team checks the new records and review process against the source. Compare vehicle counts and the campaign, dealer handoff, contact history and remedy evidence you chose to bring across. Note differences, resolve them and confirm the new database is ready before relying on it for active work.

  5. 5

    Switch off Salesforce

    Before switching off Salesforce Automotive Cloud, confirm that the records and evidence you need are accounted for. Attachments, permissions, existing communications and other suite functions need separate migration work. Address those items or make a clear plan to retain them elsewhere. Once your team approves the move, stop using Salesforce Automotive Cloud for the work you have switched.

construction

Where the real effort goes

The real work is usually mapping your own fields and review rules, then deciding how much history to bring across. Evidence files, messages and permissions need separate scoping. If you have Enterprise DNA install and run the system, Enterprise DNA handles the history mapping and scopes the additional migration work with you.

Not ready for a call?

Get your Salesforce Automotive Cloud switch plan by email

We will send you the step-by-step plan for moving your business off Salesforce Automotive Cloud, what the move really involves, and how we would do it for you.

One email with your plan. No spam, and you can unsubscribe any time.

Three ways to own it

Do it yourself, customise it, or have it run for you

Open source

Do it yourself

Free, MIT licence

  1. 1 Clone the repo and install its dependencies
  2. 2 Run npm test and npm run demo, then use Claude Code, Codex, OpenCode or Cursor
  3. 3 Configure your Salesforce Details Only report and test the import
  4. 4 Reconcile the affected vehicles and evidence before switching the covered work
Get it on GitHub

Built around your business

We customise it

One setup fee, then a retainer

  • check Your campaign fields, review rules and reporting documents
  • check Your agreed Salesforce history brought across and reconciled
  • check A web front end for your team if you want one
  • check A different stack and connected systems scoped around your operation
Get your version built

Omni by Enterprise DNA

We run it for you

One setup fee, then a retainer

  • check Installed, connected and operated through Omni by Enterprise DNA
  • check Your team access, backup and retention requirements built into the setup
  • check Your authorised people retain recall decisions and evidence review
  • check Ongoing operation and changes as your process develops
Book a call with Sam

Questions

Instead of Salesforce Automotive Cloud, answered

Does this replace all of Salesforce Automotive Cloud? expand_more

The free version replaces the coordinator records and evidence workflow described here. We map your wider use before agreeing a switch. Enterprise DNA builds the screens, connections and additional workflows your version needs.

Will our existing recall records come across? expand_more

An authorised administrator prepares a report for each campaign. The import validates the affected vehicles and keeps the original status as history. Your team reconciles the result before active use. Enterprise DNA handles that mapping and scopes evidence files, messages and permissions separately.

Can it decide whether a vehicle is safe or close a recall for us? expand_more

Your authorised people make those decisions. The system records the official source, remedy evidence and reviewer decision. It flags missing notification evidence and overdue reporting dates. It does not assess defects, give repair instructions or file a regulatory report.

Can our dealers use their own screens? expand_more

Enterprise DNA can build dealer screens and the access controls around them as part of your custom version. We agree who can see each campaign, what evidence they supply and who reviews it.

What does Enterprise DNA charge? expand_more

One setup fee, then a retainer. Sam scopes the history to bring across, your review process, team access and the connections you need. The free version remains yours to install and change.

Own the recall desk your team actually needs

Spend 30 minutes with Sam. Bring your Salesforce bill and one recall workflow. We will map the records, evidence and handoffs your version needs, then scope what Enterprise DNA builds and runs for you.

Book a call with Sam Get the free version

Vehicle Recalls for Claude Code is free and open source, published by Enterprise DNA.

Done paying for Salesforce Automotive Cloud?

Get your version built