Service requests overview
Log what you've promised a client, give it an owner and a target date, and work it from open to closed, with follow-up flags for anything overdue.
A service request is a dated commitment to a client: a repair, a change, a question someone owes an answer to. Each one has a requester, an owner and a target date, so nothing gets dropped.
Open Service → Service Requests (route /service/requests). Service
Requests is part of Full mode.
The Service Requests list

- Status filters show only Open, In progress, Resolved, Closed or Cancelled requests, with a count on each.
- Follow-up narrows the list to requests that are Overdue or Due soon. A request is overdue once its target date has passed and it isn't closed or cancelled, and due soon within two days of the target. Requests without a target date have no flag.
- Search requests looks through titles, descriptions, statuses and priorities.
- Group by groups the list by status or priority. Export CSV downloads what you're looking at.
- Change a request's Status or Priority right in the list, or select it to open it.
The list shows the newest requests first. Select the Priority column heading to sort by urgency.
Log a request
-
Select New Request.
-
Enter a Title and, if you like, a Description (you can dictate it with the microphone).
-
Choose the Contact the request is for. It's required; if the person isn't in the CRM yet, you can create them from the list. Add their Account too.
-
Choose an Owner, the person accountable for it, and a Priority: Low, Normal, High or Urgent. Normal is the default.
-
Set the Target Resolution date you've committed to, and a Related Asset if the request is about one of your client's assets.

Contact is required. The owner is who's accountable for the request. -
Select Create Request.
Work a request through to closed
Open a request to work it. The buttons at the top move it along its lifecycle:

| Status | Buttons |
|---|---|
| Open | Start work, Cancel request |
| In progress | Mark resolved, Cancel request |
| Resolved | Close request once the client confirms, or Reopen |
| Closed or Cancelled | None. These are final. |
Each change is recorded on the request's history. On the request you can also reply to the customer and keep internal notes; see Reply to a customer on a ticket.
Edit changes the title, description, priority, target date, account and owner. To hand a request to someone else, change its Owner.
Where requests come from
- Logged by your team with New Request.
- From a conversion page with Service tickets turned on: see Turn a form into a help-desk intake.
- From a connected chat channel, if your workspace has one set up.
Tips
- Always set a target date. It's what makes a request show up as overdue before the client has to chase you.
- Cancel requests you won't do, with a note on why, rather than leaving them open.