Skip to main content

Service Categories

Service Categories

Purpose and when to use this record

Maintain the types of service work used for intake, quoting, assignment, and reporting.

At a glance

  • Identify it by: Name.

  • Why care: Customer, equipment, scope, priority, technician availability, parts, labor, and status must stay aligned from intake through billing.

Before you begin

You need the Brisk storespermission for the action you are taking on service categories. If a Create, Edit, or Delete control is absent, do not work around it with another user’s account; ask an administrator to review your role.

Find and review service categories

as
Brisk Service Categories list screen displayed with fictional documentation-demo data.
The partService ofCategories list screen in the Brisk documentation demo.

Use the Service Categories list to find the correct record before opening or changing it. Compare Name. Compare the full identifier rather than relying on a similar name.

Open the service module.category Thiswhose generatedName referencematch the task. If it is awaitingmissing, workflowclear review.the list filters and recheck the identifying information shown on the screen rather than creating a replacement immediately.

Create a recordservice category

Brisk Service Categories create screen displayed with fictional documentation-demo data.
The Service Categories create screen in the Brisk documentation demo.

TheCreate evidencea packetservice identifiescategory only when the viewexisting choices do not represent the policy or classification you need. Near-duplicate setup values split reporting and make later selection harder.

  1. Select the business context first.

  2. Enter the required identifying and operational values: Name.

  3. Review the identifying information shown on the screen against the source locationdocument or approved setup decision.

  4. Save the service category, then confirm Name on its detail page before continuing.

After saving: Open Service Orders, and Service Quotes and confirm the service category appears with the intended label and availability. Keep the old value for thishistorical action.records Confirmwhen user-facingchanging stepsit beforewould approvingsplit or relabel prior reporting.

Delete a service category

Delete this page.service category only if it is an unused duplicate or setup mistake. Once other records refer to it, preserve that history and make the value inactive when the screen provides that option.

Before confirming, check for related Service Orders, and Service Quotes. Brisk may refuse deletion when another record depends on this one; resolve the duplicate or use the supported correction workflow instead of breaking the trail.

On the confirmation page, verify Name. After confirmation, return to the Service Categories list and make sure only the intended service category was removed.

ViewReview recordservice category details

Brisk Service Categories detail screen displayed with fictional documentation-demo data.
The Service Categories detail screen in the Brisk documentation demo.

The evidence packet identifiesUse the viewdetail page as the shared record of what this service category currently means. Verify Name before relying on it for a decision.

Compare the service category with its source document or approved setup request before deciding that it needs correction.

Next check: Open Service Orders, and sourceService locationQuotes and confirm the service category appears with the intended label and availability. Keep the old value for this action. Confirm user-facing steps before approving this page.

Find and reviewhistorical records

Brisk Service Categories list screen displayed with fictional documentation-demo data.
Thewhen Servicechanging Categoriesit listwould screensplit inor therelabel Briskprior documentation demo.

The evidence packet identifies the view and source location for this action. Confirm user-facing steps before approving this page.reporting.

Edit an existing recordservice category

TheEdit evidencethis packetservice identifiescategory when the viewunderlying policy or classification changed. First determine whether historical transactions should retain the old value; if so, deactivate the old choice and sourcecreate locationa new one.

  1. Open the detail page. Compare Name with the supporting document or approved request.

  2. Recheck the identifying information shown on the screen. These values are most likely to change intake, estimating, dispatch, parts, labor, completion, and billing.

  3. Save the change, return to the list, and confirm that the service category now appears under the expected Name.

After the change: Open Service Orders, and Service Quotes and confirm the service category appears with the intended label and availability. Keep the old value for historical records when changing it would split or relabel prior reporting.

Fields and business rules

Brisk stores 1 user-relevant fields for this action.service Confirmcategory, user-facingincluding steps0 beforelinked-record approvingselections and 0 controlled-choice fields. Create and edit screens may hide calculated or workflow-managed values from this page.full reference.

Deletearecord

The

evidencepacketviewandsourcelocation user-facingstepsbefore
Field Required What identifiesit thecontrols
NameYesHuman-readable name for this action.service Confirmcategory.
approving

What happens next

Open Service Orders, and Service Quotes and confirm the service category appears with the intended label and availability. Keep the old value for historical records when changing it would split or relabel prior reporting.

Common mistakes and troubleshooting

  • The record will not save: Recheck Name and any message beside the field. A required related record may also be inactive or unavailable to your role.

  • The values look right but the result is wrong: Compare this page.service category with the source document or approved setup decision, then check the downstream screen where it is used.

Back to top