Overview
Service Requests are used to record customer service work that needs attention, follow-up, and resolution. They are useful when the business wants a structured service workflow separate from ordinary sales transactions.
Main purposeManage customer service work from request to completion.
Important areasService request list, request details, linked customer or item, status, assignment, and follow-up.
Business valueBetter service visibility, clearer ownership, and stronger service history.
Where To Find It
Common Path: Service Request > Service Requests
Users typically open the Service Request list to create a new request or update an existing one.
Note: Some requests may link to items or invoice details depending on the service process your company follows.
How It Works
A service request usually begins with a customer problem or need. The business records the details, assigns responsibility, updates the request through its statuses, and closes it when the service outcome is complete.
- Use clear issue descriptions so follow-up is easier.
- Link the correct customer, item, or prior document where relevant.
- Keep assignment and status current so open service work stays visible.
Main Areas
| Area | What It Is Used For |
|---|---|
| Request List | Shows service requests and their current control status. |
| Request Details | Stores the customer issue, request background, and supporting information. |
| Linked Item / Invoice | Supports reference to the product or source document where relevant. |
| Assignment And Status | Shows who is working on the request and how far it has progressed. |
Important Fields And Controls
| Field Or Control | What It Means | When To Use It |
|---|---|---|
| Request Subject | The short title of the service matter. | Use a name that identifies the issue clearly. |
| Customer | The business partner requesting service. | Use it to keep service history connected. |
| Item / Product | The related product when the request concerns a specific item. | Use it where product-based service is important. |
| Status | The current progress of the request. | Update it during the service lifecycle. |
| Assigned To | The user or employee responsible for the next action. | Set this so ownership stays clear. |
| Description / Notes | The detailed explanation of the issue and outcome. | Use it for accurate service follow-up. |
Recommended Workflow
- Create the service request and record the customer issue clearly.
- Link the correct customer and related item or document if needed.
- Set the current status and assign the request to the correct person.
- Update notes and progress as service work continues.
- Close the request when the issue is resolved and the result is documented.
Best Practice
- Use clear, business-focused request descriptions.
- Do not leave service requests unassigned.
- Update status regularly so service backlogs remain visible.
- Close resolved requests properly so active-service reporting stays meaningful.