---
title: "Bluefin Customer Service Support | MS Dynamics Guys"
canonical_url: https://msdynamicsguys.com/case-studies/dynamics-365-customer-service-support-bluefin/
description: "MS Dynamics Guys supplied Bluefin Insurance’s support specialists. Critical incidents fell from 14 to 2 per month in May–June 2024."
publisher: "MS Dynamics Guys"
published: 2026-11-17
last_modified: 2026-11-17
---

# 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.

_Updated November 17, 2026_

[Discuss staffing](https://msdynamicsguys.com/contact/#intent=hiring&service=X12&role=team&app=customer_service) · [All customer cases](https://msdynamicsguys.com/case-studies/)

## Engagement Facts

**Bluefin Insurance: 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




**Bluefin Insurance: 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.

**Bluefin Insurance: work delivered**

| 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.

**Bluefin Insurance: outcomes**

| 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.”
>
> Sandra McPherson, Head of Service Delivery

## Related roles and services

- [Staff augmentation](https://msdynamicsguys.com/services/dynamics-365-staff-augmentation/): Add Dynamics 365 developers, consultants or architects to your team. You direct the backlog; agree skills, allocation, working hours and terms before starting.
- [CRM support](https://msdynamicsguys.com/solutions/dynamics-365-crm/support/): Dynamics 365 CRM support for Sales and Customer Service. MS Dynamics Guys investigates plug-ins, flows, permissions and integrations in existing systems.
- [Microsoft Dynamics 365 support](https://msdynamicsguys.com/services/dynamics-365-support/): Support for Dynamics 365 CRM and Business Central: custom code, integrations and recurring issues, with handover planned by MS Dynamics Guys.
- [Customer Service consultants](https://msdynamicsguys.com/hire/dynamics-365-customer-service-consultants/): Hire Dynamics 365 Customer Service consultants for cases, queues, routing and knowledge. Review the scope and discuss a specialist for your delivery team.
- [Microsoft Dynamics 365 CRM developers](https://msdynamicsguys.com/hire/dynamics-365-crm-developers/): Hire Dynamics 365 CRM developers for Dataverse, C# plug-ins, APIs and PCF controls. Review role-specific assessments and request profiles for your backlog.
- [Support transfer checklist](https://msdynamicsguys.com/resources/change-dynamics-365-support-partner/): Plan a Dynamics 365 or Business Central support transfer. Scope source code, access, open incidents, licensing and acceptance before handover.
- [Case studies](https://msdynamicsguys.com/case-studies/): Approved Microsoft Dynamics 365 projects delivered by MS Dynamics Guys, with the starting point, role, architecture, measured result and period for each.

## 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.

[Discuss staffing](https://msdynamicsguys.com/contact/#intent=hiring&service=X12&role=team&app=customer_service)
