About Paddock
Built around the dealership conversation.
Paddock builds AI software for car dealerships: answering on website chat, text, and phone, arranging appointments, and bringing the conversation back to your team.
The next person should know what happened.
A customer can move from a vehicle page to a text thread to a phone call without thinking of those as separate channels. At a dealership, each move can leave a different person trying to reconstruct the story. Paddock brings those conversations and the resulting work into one product, so the next response starts with context.
The goal is concrete: answer the question using the store’s records, complete an appropriate next step, and leave a record staff can read. That is why the product combines chat, phone, text, follow-up campaigns, and a dealership console. A helpful conversation should lead to work the store can see.
The dealership’s facts come first.
Paddock uses dealership inventory and configured store information to support answers. The vehicle page helps identify what a shopper means; it does not make every number on that page authoritative. Inventory-grounding checks and permission checks sit around the assistant’s actions so a generated answer is not the only line of defense.
These controls depend on the information your store provides and the workflows enabled during setup. We encourage dealers to ask about a missing price, an unavailable vehicle, and a changed appointment during a demo. Inspecting the resulting record is a better evaluation than accepting a broad promise about accuracy.
Your people keep ownership.
Dealership staff can review conversations and take over. Bookings, customer context, and appointment sources help the team understand what the assistant has done. Your managers configure greetings and operating details, while staff handle decisions that need a person.
For follow-up, a readable plan matters. Dealers should be able to understand the audience, the reason for contact, and when outreach stops. Customer contact preferences are part of the workflow, and staff need a clear way to inspect the activity. Product controls support that work; they do not remove the dealership’s responsibility for its own practices.
How we write our product guides.
Paddock’s resource guides are published by Paddock. They explain the category, offer practical ways to evaluate a demo, and help teams define a rollout. Where a guide uses an external framework or definition, it links to the source. Recommended procedures are presented as procedures, and fictional examples are labeled as illustrations.
We keep planning estimates separate from measured outcomes. The ROI calculator models an opportunity using selected inputs. Product demonstrations show an example workflow. Neither is a substitute for a customer case study with a stated baseline and reporting period. As the product changes, our public descriptions should continue to match what a dealer can actually see and test.
See it with your store’s questions.
The most useful conversation starts with the work you want covered. Bring your inventory source, current booking process, staffing coverage, and examples of calls or messages that are difficult to handle today. We can walk through the supported workflow and discuss the scope of a first rollout.
Use the demo booking link below to reach the Paddock team. If you are evaluating more than one vendor, bring the same test scenarios to each demo and compare the saved results, staff handoffs, and operating requirements.
Bring your store’s questions.
See an inventory question, an appointment, and a handoff in a Paddock demo.
Book a demo