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
| Field | Detail |
|---|---|
| Client | Bluefin Insurance, 620 employees |
| Industry | Specialty insurance |
| Client and delivery locations | Glasgow, UK / Lisbon |
| Product | Microsoft Dynamics 365 Customer Service |
| Roles | 1 CS consultant (support), 1 CRM/Dataverse developer (support) |
| Engagement dates | 15 Jan – 28 Jun 2024 |
| Overlap | 7 hours GMT |
| Reporting line | Client 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
| Decision | Owner |
|---|---|
| Ticket priority | Client Head of Service Delivery |
| Fix acceptance | Client Service Manager |
| Code and configuration review | Client IT lead |
| Release authorisation | Head 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.
| Role | Assignment | Accepted output | Reviewer | Approver |
|---|---|---|---|---|
| CS consultant | Root-cause diagnosis and routing fixes | 38 routing and SLA defects closed; root-cause records for 12 recurring failures | Client IT lead | Service Manager |
| CRM/Dataverse developer | Customisation remediation | 33 customisation defects closed; environment documentation pack | Client IT lead | Head 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.
| Measure | Baseline | Result | Window | Source |
|---|---|---|---|---|
| Critical incidents per month | 14 | 2 | May–Jun 2024 | Client Jira service board |
| Recurring failures with documented root cause | 0 | 12 | Jun 2024 | Client runbook |
| Environment documentation | None | 1 pack, 34 pages | Jun 2024 | Client wiki |
| Handover acceptance | — | Signed 21 Jun 2024 | — | Handover record |
| First accepted fix | — | 5 business days | Jan 2024 | Client Jira ticket |
Client perspective
“They documented what our last partner never did. Our own team now runs the environment.”
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.