# Contracts and SLAs

A **contract** records what you have promised a client. Tickets linked to a contract inherit its service levels, so deadlines are worked out for you instead of by hand.

## Contracts

Each client can have contracts, found under **Contracts** in the agent portal. A contract carries:

- **Response and resolution times for each priority**, such as 1 hour to respond and 8 hours to resolve a High priority ticket.
- An **included support hours** allowance.
- A **billing frequency**: Monthly, Quarterly, Annual or Other.
- Contract documents, built from templates you maintain in the admin area.

## How a ticket gets its deadline

When a ticket is linked to a contract, RivetMSP computes its **response due** and **resolution due** times from the contract's targets for that ticket's priority. When you pick a contract while creating a ticket, a **live hint** shows the response and resolution time you can expect before you save.

## Business hours and holidays

Targets are counted in business time, not wall-clock time. Define your working hours under **Administration > SLA Business Hours Calendars**. Each calendar has a **timezone**, the periods you work on each day of the week, and its **holidays**.

## Watching for breaches

SLA status is available to automation rules, so you can act on it automatically: a rule condition can test whether the **SLA response** or **SLA resolution** has been breached. For example, add an internal note and notify the assigned technician when a response is missed. See [Ticket automation rules](/docs/msp/ticket-automation).

## Billing

Contracts record a billing frequency, and billable time and charges can be added to tickets (the **Ticket charges** feature). Turn on **Accounting** if you want to go on and create invoices in RivetMSP, or push them to QuickBooks Online. See [Integrations](/docs/msp/integrations) and [Turning features on and off](/docs/msp/modules).
