Priority Service Rules

The customer and operating outcome

Define what priority handling means so dispatch can apply it fairly during normal and peak demand. The plan must be understandable to the customer and deliverable by scheduling, dispatch, field, billing, and customer-service teams.

Plan controls

• Use the same scope, benefit, term, and pricing language across the website, agreement, office scripts, dispatch notes, field forms, and invoices.
• Avoid benefits that depend on unlimited capacity or undefined exceptions.
• Keep active-customer terms separate from future pricing or product changes.

Key checkpoints

• State whether priority changes queue position, response target, arrival window, or after-hours eligibility.
• Define exclusions during emergencies, weather events, and capacity limits.
• Train office teams to explain priority without guaranteeing impossible response times.
• Audit whether the promised benefit is actually delivered.

Implementation sequence

• Define the rule and the business owner.
• Document how the rule appears in customer communication and system records.
• Train office and field teams using realistic examples and exceptions.
• Test the workflow with a small account group before broad use.
• Measure completion, customer questions, cost, and retention impact.

Review evidence

• Agreement version and effective date.
• Customer authorization, covered assets, due visits, completed service, and open obligations.
• Revenue, delivery cost, discounts, cancellations, renewal outcomes, and service exceptions.