Hub · Leasing operations
Leasing operations for dealers and leasing companies — the complete guide
Most lost lease-renewals aren't lost on price or product — they're lost because the dealer and the leasing company don't work in the same system. This is the definitive guide to how the two parties share customer data, own their respective parts of the relationship, and run a 90-day renewal flow that lifts the renewal rate from 15-25% to 35-50%.
Last updated:
Short answer (TL;DR)
Leasing operations covers the entire chain from new contract to renewal: contract management, customer dialogue, ex-lease vehicle handling and 90-day expiry flow. The dealer owns the relationship, the leasing company owns the contract — and a shared platform like CARRUSLiNK coordinates them without either party losing data ownership. Dealers with structured operations reach 35-50% renewal rate; without, the rate sits at 15-25%.
Role allocation between dealer and leasing company
The single most important decision in a leasing partnership is who owns what. Experience from both Nordic and European markets is clear: the dealer must own the relationship, the dialogue and the renewal. The leasing company must own the contract, the financing and the residual value risk. When that line blurs — typically when the leasing company builds its own call centre and contacts customers directly at expiry — the renewal rate drops dramatically.
It comes down to the nature of the relationship. The customer has had physical contact with the dealer: test drive, delivery, first service. When a call centre from the finance partner rings at expiry, it feels like debt collection or cold calling. When the dealer calls from the same relationship as the original sale, it's a natural continuation.
- Dealer owns: customer relationship, dialogue, test drive, delivery, first service, renewal
- Leasing company owns: contract, financing, residual value, credit risk, balance sheet
- Shared: contract expiry, vehicle history, customer data (role-based)
- Conflict zone: leasing company must not contact the customer directly without the dealer
- Result with clear role allocation: renewal rate 35-50% vs. 15-25% without
Data sharing and GDPR between two parties
Dealer and leasing company each have their own lawful basis to process the customer's data — typically the contract itself. Under GDPR each party is data controller for its own part of the processing, while a shared platform like CARRUSLiNK acts as data processor for both. That means neither party has to hand over raw databases, and each party only sees what it needs to perform its role.
Practical setup: contract data is pushed from the leasing company's finance platform to CARRUSLiNK once during onboarding, and automatically for new contracts thereafter. The dealer sees customer cards with contract length and expiry date — not residual value calculations or credit scoring. The leasing company sees portfolio reports and renewal rate per dealer — not individual customer dialogue. Both parties have audit logs of who has seen what.
- Each party is data controller for its own part — shared platform as data processor
- Role-based access: dealer sees customer + vehicle + expiry; leasing company sees portfolio + rate
- No raw CSV exchange — data is live and shared
- Audit log on both sides of the partnership
- Data processing agreement between CARRUSLiNK and each party
90-day renewal flow from T-90 to T+0
The single most important flow in leasing operations is the 90 days before contract expiry. 6 out of 10 leasing customers start looking at a new car 4-5 months before expiry. If you haven't made contact by day T-90, the customer is already booked at a competitor.
Day T-90: SMS to customer + task to responsible salesperson appears automatically in the daily list. The customer is told that the contract is approaching expiry and that the salesperson will be in touch within 14 days. This is the most important single step — this is where the flow either succeeds or fails.
Day T-60: The salesperson has spoken to the customer and knows the preference. A concrete offer is sent — either re-leasing the same car at a new price, or 2-3 wishlist matches from the dealer's own inventory. The offer is signable digitally with MitID or equivalent.
Day T-30: Salesperson call to close. If the customer wants a new car, a test drive is booked. If the customer wants to re-lease, a new contract is sent for signature. If the customer is leaving, the reason is recorded so the leasing company can spot patterns in churn.
Day T-7 to T+0: Return arrangement, residual value assessment, hand-in/hand-out, possibly contract overlap if the new car isn't ready. The car comes in, runs through reconditioning, and is ready for the next cycle.
- T-90: SMS + salesperson task starts automatically
- T-60: concrete offer (re-lease or wishlist matches)
- T-30: salesperson call, possibly test drive
- T-7 to T+0: return, residual value assessment, reconditioning
- Triggers based on contract date — not on the salesperson's memory
Ex-lease vehicle handling: same flow as used cars
The classic mistake is that ex-lease vehicles end up in a separate 'lease inventory' in Excel, disconnected from the used car flow. That means double work, double advertising, and that vehicle-to-customer matching never happens because the two inventories are separate.
The right setup: the car comes in, runs through the same intake as a trade-in — photos, reconditioning, pricing, portal advertising — and is simultaneously matched automatically against all active customer wishlists (both new buyers and leasing customers whose contracts are about to expire). A residual value report is sent automatically back to the leasing company.
The clever part is that the car is often sold before it's ready: if an existing leasing customer's wishlist matches the returned car, the salesperson can offer continuation on the same car at a lower monthly payment. No advertising, no reconditioning time wasted.
Vehicle ↔ customer match (wishlist) as an operations tool
Wishlist is a simple idea with big operational impact: each customer has a structured preference (make, model, year, price range, transmission, fuel). When a matching car comes in — whether it's a lease return or a regular used car — the responsible salesperson gets an instant notification, and the customer is automatically informed.
For leasing operations, that means the renewal flow doesn't depend on the salesperson manually searching the inventory. When a contract approaches expiry, the system automatically shows which cars in stock match the customer's wishlist. The salesperson picks the track — the system runs the rest.
- Structured wishlist per customer — not an old email
- Auto-match against new cars in inventory
- Works for both re-lease and new car
- Salesperson gets notification — no manual inventory search
- Wishlist stays on the customer card — survives salesperson turnover
Frequently asked questions about leasing operations
Cluster guides · Leasing operations
- System for leasing customers
- Following up on leasing customers
- Alternative to Excel for leasing
- CRM for leasing companies
- Dealer ↔ leasing company collaboration
- Leasing segment
- Who owns the customer — dealer or leasing company?
- How do dealer and leasing company share customer data?
- Lease contract expires — what should the dealer do?
- How to handle ex-lease vehicles as a dealer
- Lease vehicle return flow
- Residual value reporting in a leasing system
- Lease contract renewal-rate benchmark
- White-label leasing for car dealers
See the leasing-operations stack with your own contract numbers
30-minute demo. We show how dealer and leasing company work in the same system with clear role allocation, 90-day renewal flow and vehicle↔customer matching — without either party losing data ownership.