Service level agreement

What should a dealership software SLA include?

An SLA is only useful when it defines severity, response, resolution and consequence. Most dealership software agreements define availability and stop. Ask for severity levels tied to business impact, a response commitment per severity, an escalation path with names or roles, and a remedy that means something when the commitment is missed.

Direct answerSeptember 1, 2026 reviewedNeutral evaluation
01

Define severity by business impact

Severity should be written in dealership terms: cannot close a deal, cannot open a repair order, cannot post to accounting, cannot dispatch. A vendor-defined severity scale usually rates its own outage lower than you would.

02

Response is not resolution

A four-hour response commitment with no resolution target means someone acknowledges the ticket and nothing more. Ask what the provider commits to for resolution or workaround, and what happens when that is missed.

03

Availability needs a measurement method

Ask what counts as downtime, whether planned maintenance is excluded, what the measurement window is, and who reports the number. An availability figure the vendor calculates and never publishes is not a commitment.

04

Make the remedy proportionate

Service credits that refund a fraction of a monthly fee do not cover a lost Saturday. Where the system is genuinely operationally critical, negotiate escalation rights and termination rights for repeated failure rather than relying on credits.

Decision checklist

What to verify

Open procurement templates →

Define severity in dealership terms, not vendor terms

Separate response commitment from resolution commitment

Ask how availability is measured and who reports it

Negotiate escalation and termination rights for repeated failure

Related market maps

Continue the research

People also research

Related dealership technology questions