Customer case study

Microsoft Dynamics 365 Customer Service Support at Bluefin Insurance

Engagement summary

Bluefin Insurance embedded one Microsoft Dynamics 365 Customer Service consultant and one CRM and Dataverse developer from MS Dynamics Guys in its live support team from January to June 2024. The specialists closed 71 defects across case routing, service levels and customisations, with handover accepted on 21 June. Bluefin’s Jira service board recorded critical incidents falling from 14 per month to two.

Engagement Facts

Bluefin Insurance: engagement facts
FieldDetail
ClientBluefin Insurance, 620 employees
IndustrySpecialty insurance
Client and delivery locationsGlasgow, UK / Lisbon
ProductMicrosoft Dynamics 365 Customer Service
Roles1 CS consultant (support), 1 CRM/Dataverse developer (support)
Engagement dates15 Jan – 28 Jun 2024
Overlap7 hours GMT
Reporting lineClient Head of Service Delivery

Why the Client Added Capacity

Bluefin’s previous implementation partner had exited, leaving a Microsoft Dynamics 365 Customer Service environment without documentation and recurring case-routing and SLA failures. Bluefin’s two-person team needed extra capacity to diagnose those failures while it continued running daily support.

Decision Rights

Bluefin Insurance: decision rights
DecisionOwner
Ticket priorityClient Head of Service Delivery
Fix acceptanceClient Service Manager
Code and configuration reviewClient IT lead
Release authorisationHead of Service Delivery

Work Delivered

The consultant closed 38 routing and SLA defects and recorded the root causes of 12 recurring failures. The developer closed 33 customisation defects and assembled the environment documentation. Bluefin’s Head of Service Delivery prioritised tickets and authorised releases, and its IT lead reviewed the changes before acceptance.

Bluefin Insurance: work delivered
RoleAssignmentAccepted outputReviewerApprover
CS consultantRoot-cause diagnosis and routing fixes38 routing and SLA defects closed; root-cause records for 12 recurring failuresClient IT leadService Manager
CRM/Dataverse developerCustomisation remediation33 customisation defects closed; environment documentation packClient IT leadHead of Service Delivery

Outcomes

Bluefin’s Jira ticket history records the first accepted fix within five business days. Its runbook, wiki and signed handover record document the fixes and the material transferred to the internal team.

Bluefin Insurance: outcomes
MeasureBaselineResultWindowSource
Critical incidents per month142May–Jun 2024Client Jira service board
Recurring failures with documented root cause012Jun 2024Client runbook
Environment documentationNone1 pack, 34 pagesJun 2024Client wiki
Handover acceptance—Signed 21 Jun 2024—Handover record
First accepted fix—5 business daysJan 2024Client Jira ticket

Client perspective

“They documented what our last partner never did. Our own team now runs the environment.”

Sandra McPherson, Head of Service Delivery

Your next step

Discuss the capacity your team needs

Share the application, workstream and specialist allocation you need. Your team can define its own backlog, acceptance and release responsibilities.