LEARN BUSINESS INTELLIGENCE

Preparing a Service Performance Review Customers Can Use

Open a service performance review with what you promised, what happened and what you’ll look into next. Bring the cases behind the numbers so the customer can see how you reached the result.

  
AGREE THE MEASURE

Put the service promise in plain language

Imagine you run a monthly review for a facilities customer. You agreed that engineers would arrive within 60 minutes of an urgent call being logged. Your monthly target is to meet that promise on 95% of eligible calls.

  • Group calls by when they were logged, using the customer’s local time.
  • Exclude calls cancelled before dispatch under the agreement.
  • Show the count as well as the percentage.

June had 53 urgent calls. Three were excluded and 45 of the remaining 50 were on time. That gives 90%.

Show the cut-off

State the reporting period and when you took the data. Flag unresolved calls and missing arrival times.

  
CONNECT THE EVIDENCE

Match each call to the rule that applied

Start with the promise that applied when the call came in. If response times vary by customer or priority, use the rule for that call. Then compare the monthly result with the target you agreed for that month.

Before counting, check for duplicate call references, missing arrival times and calls without a valid rule. If several engineers attended one call, use the first arrival under this agreement.

Label the two targets

60 minutes applies to each call. 95% applies to the month’s eligible calls.

  
READ THE MONTH IN CONTEXT

Show the trend and the cases behind it

Show the 95% target beside the trend. April was above it. May and June were below it.

On-time arrival for urgent callouts
Monthly target 95%
MonthOn timeEligibleRate
April586096.7%
May475094.0%
June455090.0%

Three of June’s five late arrivals were at the east site. Callout FM-2048 was logged at 9:12 a.m., assigned at 9:43 a.m. and the engineer arrived at 10:24 a.m. That is 72 minutes from logging to arrival, or 12 minutes past the deadline. The dispatch log gives the team a place to start its follow-up.

Keep the case traceable

Bring the call reference, the deadline and the timestamps to the review.

  
PREPARE THE DISCUSSION

Bring one question and agree what happens next

Before comparing sites, check how many eligible calls each site handled. Bring one case and agree on one follow-up. Here, the dispatch lead agrees to compare the three east-site timelines and update the customer by July 15.

  • Use a workbook if the team just needs to prepare the figures.
  • Use a dated PDF when the customer needs a fixed copy.
  • Use a shared view when approved readers need to explore case detail between meetings.

If the customer needs to follow up between meetings, put the trend and the cases they can see in one place. IntelliFront BI is ChristianSteven Software’s reporting platform, hosted on infrastructure you manage, and can show both from the data you’ve prepared.

Check the customer’s copy

Open the output as the customer will see it. Check the account, period and level of detail.

  
PUT IT INTO PRACTICE

Try it in your next monthly review

Bring one late case to your next review and agree who’ll look into it and when the customer will hear back. Open the following meeting with that update. If the customer needs the trend and supporting records between reviews, see how to share a customer’s service reporting through a portal.

Contributors:

Christian Ofori-Boateng

Christian Ofori-Boateng

CEO, ChristianSteven Software