DMS
Swifty reads and updates customer and vehicle records in Keyloop and Pinewood, and books workshop visits on the call.
Dealership system integrations
Connect conversations to the systems that make them useful.
Swifty works with the DMS, workshop, CRM, phone, call recording and stock systems that UK car dealers already use, including Keyloop, Pinewood, EnquiryMax, Dealerweb, Mitel and Avaya.
Customer says
“Can I book a service on Tuesday?”
Swifty connects to your systems
- Read
- Check diary availability
- Confirm
- Agree a time with the customer
- Write
- Create the appointment
The booking stays in your diary
Your existing system remains the source of truth.
An example of a configured booking connection. Supported systems, access and permitted updates are agreed for each implementation.
Compatible with
Systems Swifty works with
What Swifty does with each type of system.
Workshop management
Swifty checks the workshop diary in Rapid RTC, Drive, Autoline and Kerridge, offers free times, and books, moves or cancels visits on the call.
CRM
Swifty reads and updates enquiries in EnquiryMax, Dealerweb and eMaster, and writes new ones from calls with a note and the next contact. It gives new leads an owner, finds duplicates and creates call tasks for your team.
Phone systems
You keep your phone system, such as Mitel, 8x8 or Avaya. It sends calls to Swifty, and Swifty transfers callers to your departments. Swifty is SIP based, so other phone systems work the same way.
Call recording
Swifty pulls your team's recorded calls from Akixi, Xima or Red Box, or from your phone system, and analyses the sales calls.
Stock and websites
Swifty webchat searches your live stock from NetDirector or Cooper Solutions, and checks if a car is still available.
What to ask about any integration
A useful integration needs to answer practical questions. Can it read availability, create an appointment, update a customer record, save an opt out and recover safely when a system is unavailable? Swifty maps those actions against the dealership journey.
What Swifty needs from the dealership
- The customer journey and the dealership person who owns it.
- The approved source system, access method and minimum required data.
- The booking, update or follow up authority Swifty is permitted to use.
- The backup, exception and human handover rules.
- Representative test cases and an agreed acceptance process.
Safe behaviour when a system cannot complete the action
Swifty should not invent availability or say that an appointment is confirmed when the connected system has not accepted it. The agreed backup action may capture a request, record what failed, offer another route or assign the work to a person.
For the wider evaluation process, review security and governance or use the Automotive AI buyer's guide.
Frequently asked
Integration questions.
Which dealership systems is Swifty compatible with?＋
Swifty works with Keyloop and Pinewood, the workshop systems Rapid RTC, Drive, Autoline and Kerridge, and the CRMs EnquiryMax, Dealerweb and eMaster. It also works with phone systems such as Mitel, 8x8 and Avaya, call recording from Akixi, Xima and Red Box, and stock from NetDirector and Cooper Solutions. If you use another system, ask us.
Does Swifty replace the dealership's existing systems?＋
No. Swifty is designed to connect customer conversations to the dealership systems and workflows that remain the approved source of truth.
Can Swifty update appointments and outcomes?＋
Where approved access and a suitable interface exist, Swifty can support appointment, request, outcome or follow up updates. The exact authority and backup action are agreed for each journey.
Bring your system landscape
Map one valuable dealership journey from call to result.
Show us the conversation, systems, booking rules, information needs, exceptions and team owner. We will map what the integration needs to do.
Discuss an integration