Skip to content
DCS
PR

Riccall Solicitors LLP

RIC387ActiveTime and materials

riccallsolicitors.co.uk · Legal · Account manager Dan Okafor

Microsoft 365Healthy2 days agoSupport & assets (SQL)Healthy11 hr ago

01 Jan 202625 Aug 2026 · month buckets · applies to every section

SLA figures cover contract calls only, measured against a flat 8-hour response target from logged to responded. 3 records in this selection sit outside that — quotes, projects and planned installs, plus 2 calls billed time and materials. They stay visible for volume context.

Service performance

25 eligible records in this year
Average first response
4.8 hr
Target 8 hours from logged to responded
Average resolution
1.4 days
Open records excluded from the average
SLA achievement
88.0%
3 call(s) over the 8-hour target
First-time fix
60.0%
Where the source records the field

Volume

Contract calls
25
28 calls logged in the period
Off contract
2
£218.25 chargeable
Open / closed
0 / 28
Across the selected period
Data-quality gaps
0
Contract calls with no response time recorded

Support volume trend

Event measure summed per month

Records are counted in the bucket containing their logged date.

Category breakdown

Eligible records only

25
records
  • Network6
  • Printing4
  • Backup4
  • Microsoft 3653
  • Hardware2
  • Telephony2

Support performance by year

Contract calls against the 8-hour response target

Contract support calls by year
YearCallsAvg responseSLA metMissesExcluded
2026254.80 hr88.0%33

Response performance by call logger

Grouped by the person who raised the call, not the engineer

Response performance by the person logging calls
Call loggerCallsAvg responseSLA metMisses
Daniel Blacker41.77 hr100%0
(Not recorded)46.88 hr75%1
Stacey Thomas314.32 hr67%1
Julie Herbert32.72 hr100%0
Rachael Parkin32.27 hr100%0
Kelly Gregory32.36 hr100%0
Aiden Higgins20.92 hr100%0
Damian Armstrong14.63 hr100%0
Karen Taylor18.47 hr0%1
Chloe Dempsey15.39 hr100%0

3 contract calls missed the 8-hour target

Worst first — the calls a service review will be asked about

Longest 32.9 hr over
Contract calls that missed the response target
Job numberCall loggerMachine or systemLoggedResponseOver targetEngineerIssue
302207Stacey ThomasDell Latitude 74202026-01-02 11:0440.92 hr+32.9SEWi-Fi dropouts in warehouse
302227(Not recorded)HPE ProLiant DL380 Gen102026-07-02 11:0920.80 hr+12.8SEVoicemail not delivering
302219Karen TaylorKyocera ECOSYS M55262026-04-13 08:418.47 hr+0.5SESite offline

Recurring issues by call logger

Repeat patterns worth fixing at source

No repeat pattern in this period.

Recurring issues by machine

Equipment generating repeat calls

No device is generating repeat calls.

SLA achievement trend

Percentage of eligible records responded to within target

Records

28 records match the current filters · showing the 150 most recent

Read-only from source
ReferenceLoggedTypeSummaryPriorityStatusResponseResolutionSLA
RIC387-10007824 Aug 2026IncidentCall quality issue
Telephony · TAG · Head Office
P1Closed1.18 hr6.0 hrMet
RIC387-10007708 Aug 2026Service RequestNew printer driver rollout
Printing · SE · Site 2
P3Closed5.72 hr1.8 daysMet
RIC387-10007630 Jul 2026IncidentWi-Fi dropouts in warehouse
Network · KB · Site 2
P3Closed1.17 hr1.3 daysMet
RIC387-10007515 Jul 2026Service RequestTeams sign-in loop
Microsoft 365 · KB · Head Office
P3Closed0.20 hr2.5 daysMet
RIC387-10007414 Jul 2026IncidentBackup job failed
Backup · BK · Head Office
P4Resolved1.23 hr2.2 daysMet
RIC387-10007309 Jul 2026Service Request · excludedHandset registration
Telephony · TAG · Remote
P3Resolvedn/a
RIC387-10007206 Jul 2026Service RequestBackup capacity review
Backup · SE · Head Office
P2Closed4.60 hr2.3 daysMet
RIC387-10007102 Jul 2026IncidentVoicemail not delivering
Telephony · SE · Remote
P3Resolved20.80 hr16.6 hrMissed
RIC387-10007024 Jun 2026IncidentName change request
User admin · TAG · Branch
P4Closed1.04 hr1.2 daysMet
RIC387-10006923 Jun 2026IncidentSharePoint permission request
Microsoft 365 · ML · Remote
P2Resolved5.39 hr1.7 daysMet
RIC387-10006805 Jun 2026IncidentSpoofed email reported
Email · SE · Head Office
P1Resolved1.38 hr7.8 hrMet
RIC387-10006721 May 2026IncidentRestore request
Backup · TAG · Head Office
P3Closed0.46 hr1.7 daysMet
RIC387-10006620 May 2026Planned Install · excludedDatabase timeout
Line of business app · BK · Site 2
P3Resolvedn/a
RIC387-10006529 Apr 2026ChangeReplacement keyboard
Hardware · AB · Head Office
P4Closed1.06 hr1.5 daysMet
RIC387-10006415 Apr 2026IncidentRetention change
Backup · SE · Head Office
P3Resolved1.42 hr1.8 daysMet
RIC387-10006313 Apr 2026IncidentSite offline
Network · SE · Head Office
P3Closed8.47 hr1.2 daysMissed
RIC387-10006231 Mar 2026Service RequestScan to email failing
Printing · BK · Head Office
P3Closed0.11 hr19.3 hrMet
RIC387-10006124 Mar 2026IncidentPrinter offline
Printing · SE · Head Office
P4Closed0.99 hr1.8 daysMet
RIC387-10006022 Mar 2026IncidentSite offline
Network · AB · Branch
P3Resolved4.49 hr11.2 hrMet
RIC387-10005902 Mar 2026IncidentReplacement keyboard
Hardware · BK · Remote
P3Resolved0.88 hr1.9 daysMet
RIC387-10005812 Feb 2026IncidentPrinter offline
Printing · AB · Branch
P3Resolved5.37 hr2.1 daysMet
RIC387-10005704 Feb 2026Service RequestDatabase timeout
Line of business app · AB · Branch
P3Closed1.47 hr1.6 daysMet
RIC387-10005602 Feb 2026Service RequestOneDrive sync conflict
Microsoft 365 · AB · Head Office
P4Resolved0.59 hr17.1 hrMet
RIC387-10005521 Jan 2026IncidentMFA reset
Security · ML · Head Office
P3Closed5.52 hr7.1 hrMet
RIC387-10005416 Jan 2026Incident · excludedMessage quarantined
Email · BK · Head Office
P3Resolvedn/a
RIC387-10005314 Jan 2026Service RequestSlow VPN
Network · AB · Branch
P2Resolved0.84 hr13.0 hrMet
RIC387-10005211 Jan 2026IncidentSlow VPN
Network · ML · Head Office
P3Closed4.63 hr2.0 daysMet
RIC387-10005102 Jan 2026ChangeWi-Fi dropouts in warehouse
Network · SE · Remote
P3Closed40.92 hr1.1 daysMissed
iHow these figures are calculatedShow
Eligibility uses the structured record type from the source system, never free-text title matching. Excluded types: Quote, Project, Planned Install (rule version sla-rules v2.0). Records with no captured response time are left out of averages and reported as a data-quality count. Worked example: if nine eligible records respond within one hour and one quote stays open for fourteen days, the quote contributes nothing to the response-time denominator and does not move the average.