Skip to content
Workspacebeamcore

Client notes

What desks said after the pack landed

These are comments from named roles, not scores. Each one refers to a piece of work on this site. We keep surnames to an initial because the extracts themselves are confidential.

“The first draft put Sunday password resets into Monday’s first-response line. We caught it on the review call, they redrew it, and the pack we took to the operations group finally matched the hours we actually advertise. I still wish the covering note were shorter — two pages is a lot before a 9 a.m. meeting — but the charts were the ones people argued about, which is the point.”

Claire M., Service desk manager, university IT — Quarterly SLA pack

“Thursday’s page showed the 12:00–13:00 abandoned-call spike we keep talking about in the huddle. Having it on the same hour grid as ticket creates stopped the usual row about whether the phones were ‘really’ busy.”

Darren H., Contact centre supervisor, local authority — Weekly workload snapshot

“We had been sure late Tuesday was our problem. Thirteen weeks of volume said the quiet waste was Wednesday after 15:30. That did not give us a new rota on its own, and they were clear they would not write one, but it stopped us moving people to the wrong evening.”

Amelia R., IT operations lead, regional housing association — Shift-pattern review

“They refused to talk about named agents in the room, which annoyed one of our team leads for the first ten minutes and then saved the session. We spent the rest of the time on the VIP queue that had been hiding inside ‘general staff’.”

Neil P., Support manager, in-house desk for a manufacturer — On-site pack briefing

“Audit wanted a story about a bad fortnight. The note they got listed three clock-pause codes with no reason text and a batch of tickets reopened by another team after we had closed them. Not comfortable reading, and not something a dashboard screenshot would have shown.”

Sian L., Head of customer support, shared-service desk — Breach and backlog investigation

A university desk and a Sunday clock

The operations group had been shown a first-response chart that treated every weekend password reset as late on arrival. Helen sat with the advertised hours, redrew the clock to the next opening minute, and the breach column dropped without anyone closing a ticket. The manager’s reservation — that the covering note ran long for a 9 a.m. slot — is fair; we now offer a one-page board strip as an extra sheet, still drawn from the same extract.

A housing-association evening that was not the problem

A shift-pattern review for a regional housing desk used thirteen weeks of volume. The late Tuesday overlay everyone expected to look overloaded was ordinary. Wednesday after 15:30 was quiet enough to trial a shorter evening. We did not write the rota. We left a heat map and a conversation. The operations lead later moved two hours of cover, then asked for a quarterly pack on the same field list.