Inside Pam's AI agents, a quarter of a million recall checks a month
Pam builds the AI agents that answer and place calls for more than 800 dealership locations. Every vehicle those agents touch gets checked against open safety recalls, outbound and inbound, on CarsXE data.
Jump to the form. Takes about a minute.
- Company
- Pam
- Services
- AI agents for car dealerships
- Products Used
- Vehicle Recalls API
16×
Growth in recall lookups between May and July 2026
Both directions
The list Pam calls, and the call that comes in
800+ rooftops
Dealership locations running Pam's agents
01
The call ends, and the recall is still open
Someone calls their dealership to ask about a tire rotation. The AI receptionist answers, finds a slot, books it, and the call ends.
Sitting on that same vehicle was a second appointment nobody booked. An open safety recall, already funded by the manufacturer, free to the customer, and billable work for the service department. Nobody on the call knew it was there.
The gap runs the other way too. A service department needs a reason to call a customer that is not "it has been a while." A recall is the best reason in the industry: manufacturer funded, safety framed, legally significant, and genuinely worth the customer's time. But working out which owners have an open one, across an entire DMS, this week, is a data problem. Not an AI problem.
02
One VIN, both directions
Pam wired CarsXE's recall endpoints into both halves of its platform.
The Outbound Marketing Agent runs on continuous monitoring. Pam checks dealers' vehicle lists against open recall campaigns on a schedule, so the list the agent works is built from vehicles that have an open recall right now, not a snapshot someone pulled last quarter.
The Receptionist Agent runs the other direction. A call comes in, and Pam looks up that caller's vehicle during the conversation. If there is an open recall, the agent raises it while the customer is still on the phone and books the recall service alongside whatever they originally called about.
Same data, two jobs. One finds the customer worth calling. The other makes the call the customer makes worth more.
03
What it changed
Recall lookups went up 16× in two months. Pam went from thousands of vehicle lookups a month to more than a quarter of a million, without changing what the agents do, only how many vehicles they could check.
Checking became monitoring. Instead of looking up a recall when someone asked, Pam moved to scanning dealers' vehicle bases continuously, so an open recall surfaces when it is published rather than when someone thinks to look.
Recalls stopped being a feature and became the workflow. Almost every call Pam makes to CarsXE is recall data.
Jump to the form. Takes about a minute.
04
In their words
“Our agents book the recall alongside whatever the customer originally called about, and the dealer captures service work that used to walk out the door unnoticed.”
“When a customer calls a dealership, we know they have an open recall instantly. That changes what the call is worth. Our agents book the recall alongside whatever the customer originally called about, and the dealer captures service work that used to walk out the door unnoticed. CarsXE's recall data is what makes that possible on every call, at every rooftop we run.”
Samee Khan
Founder & CEO, Pam
05
About Pam
Pam builds AI agents for car dealerships. Its Receptionist Agent answers inbound calls and texts around the clock, books service and captures sales intent. Its Outbound Marketing Agent works customer lists for retention, recalls and declined-service follow-up. Pam runs at more than 800 dealership locations across 40+ US states and three Canadian provinces. It is a preferred partner with GM and Ford, and is backed by Autotech Ventures.
Product used: Vehicle Recalls API
06
Would this work for our platform?
- Can't we get recall data free from NHTSA?
You can get a lookup. You cannot get a pipeline.
NHTSA gives you a per-VIN query. It does not give you a bulk interface, an SLA, normalized completion status, or anything that survives a quarter of a million calls a month. The question worth asking is not what it costs today. It is what happens to your outreach the week that endpoint changes shape and your agent starts failing calls.
- How long does this take to integrate?
Minutes to your first call, not weeks. There is a free sandbox with no credit card, published docs, and SDKs, and you can go from sandbox to production without talking to anyone. The recall endpoints take a VIN and return open campaigns, so there is no schema to model and no file exchange to build.
Putting it inside your product the way Pam has is a real integration, and that is a developer's job. Getting a trustworthy answer back on your own VINs is an afternoon.
- What does it cost?
Plans are published, not quoted. A free sandbox gives you 100 lookups with no credit card. Past that, pricing is per plan with per-lookup overage, and you are only charged for lookups that return data.
- Will it tell us whether the recall has already been fixed?
Not consistently, and this is worth knowing before you build on it. Some manufacturers, Toyota in particular, restrict remedy-completion status. For those makes you will know an open campaign exists without knowing whether that specific vehicle has already had the work done. Coverage varies by OEM and we are working on it.
For outreach this is usually survivable, because the agent's job is to start a conversation the dealer can confirm against their own service records. For hard compliance gating, test it against your own makes first.
- Can we test it on our own vehicles?
Get a sandbox key and run your VINs. No card, no call. Test it on the makes and model years you actually see rather than taking our word for the coverage. That is what the sandbox is for.
07
Get pricing for your volume
Tell us roughly how many vehicles you are checking and which data you need, and we will come back with pricing for your volume.
Rather test it first? Start with 100 free lookups, no credit card required.