Skip to main content
All CollectionsGetting Started
Determining the Priority Level of a Request
Determining the Priority Level of a Request
Updated over a week ago

When submitting a service request, determining the priority of the request becomes crucial to minimize disruptions and keep your business running efficiently.

Here's a guide to help you understand and establish the priority levels for service requests in your restaurant.

Emergency Priority

Criteria:

  • Situation: Location is closed or at risk of closing.

  • Asset: Critical for business operations.

  • Resolution Time: Needed ASAP.

  • Service Needed: First available technician; overtime (OT) approval required.

Whether it's a kitchen shutdown or any critical asset that jeopardizes the success of your restaurant, immediate resolution is imperative. Emergencies are for the first available service, OT approved.

High Priority

Criteria:

  • Asset: Important and causes business disruptions when down.

  • Resolution Time: Needed ASAP.

  • Service Needed: First available technician; regular rates apply.

Assets classified as high priority are essential for your business but might not pose an immediate threat of closure. However, their malfunction could disrupt operations and impact customer satisfaction. High priority indicates needing first available service at regular rates.

Medium Priority

Criteria:

  • Asset: Not critical for business operations.

  • Resolution Time: Needed within 48-72 hours.

  • Service Request: Regular rates apply.

Assets falling under medium priority are necessary but don't have an immediate impact on daily operations. Work arounds are available. These requests need to be addressed within a timeframe of 48-72 hours.

Low Priority

Criteria:

  • Asset: Not critical; can be bundled with other requests.

  • Resolution Time: Not needed within 72 hours.

  • Service Request: No urgency; service not required right away.

Assets with low priority are non-critical and can afford a delayed resolution. These requests can be bundled with others to optimize service efficiency.

Did this answer your question?