Microsoft Real Estate and Construction United Kingdom

VIVID

Application Refactoring · Customer Service Automation · Risk Management

Alex Nagle, Customer Services Director, VIVID Coming out of the pandemic, VIVID knew it needed to upgrade its legacy systems to modern cloud-based solutions.

Average speed to answer has been cut from six minutes to 50 seconds.
VIVID created a comprehensive knowledge base of articles in SharePoint which can be interrogated using a customised chatbot built with Microsoft Copilot Studio Since its launch, knowledge articles have been viewed more than 500,000 times, supporting digital self-service and contributing to reduced voice traffic volumes.

Reported impact

Business outcome

They enhanced their contact centre with the Microsoft Digital Contact Centre platform, integrating skill-based routing, IVR, chatbots, and Copilot.

  • Customer Experience
  • Productivity Improvement
  • Risk Reduction
  • Speed to Market

Solution

VIVID built its Microsoft solution to improve customer-service and conversational-support workflows. Alex Nagle, Customer Services Director, VIVID Coming out of the pandemic, VIVID knew it needed to upgrade its legacy systems to modern cloud-based solutions. Key components included Microsoft Copilot Studio coordinated workflows, prompts, or deployment, and Dynamics 365 Customer Service delivered dashboards, apps, or copilots to users. Requests and business records enter Dynamics 365 Customer Service, where Microsoft Copilot Studio assists routing, summaries, or responses before the updated information is surfaced back to employees and customers through the Microsoft application layer. The stack stayed governed and extensible on Microsoft. They enhanced their contact centre with the Microsoft Digital Contact Centre platform, integrating skill-based routing, IVR, chatbots, and Copilot.

Data flow

Requests and business records enter Dynamics 365 Customer Service, where Microsoft Copilot Studio assists routing, summaries, or responses before the updated information is surfaced back to employees and customers through the Microsoft application layer.

Solution architecture

4 components · 3 layers
  1. Compute
    • Azure Provides the core cloud infrastructure and managed services underlying the deployment.
  2. Serving
    • Dynamics 365 Customer Service Provides the case-management and service workspace for customer-support teams.
  3. Orchestration
    • Microsoft Copilot Studio Provides the managed environment to design, test, and operate custom copilots.
    • Microsoft Power Platform Supports low-code automation and app development around Microsoft business data.

Architecture clues

  • Key Microsoft components include Microsoft Copilot Studio, Dynamics 365 Customer Service, Microsoft Power Platform, Azure.

Evidence from the source

Alex Nagle, Customer Services Director, VIVID Coming out of the pandemic, VIVID knew it needed to upgrade its legacy systems to modern cloud-based solutions.
Average speed to answer has been cut from six minutes to 50 seconds.
Taking a "Microsoft first" approach "We knew we wanted to implement Dynamics 365 Customer Service ," states Fiona Harris.
The foundation of the new solution is Microsoft Dynamics 365, including Dynamics 365 Customer Service, Dynamics 365 Contact Centre, and Dynamics 365 Field Service.
They enhanced their contact centre with the Microsoft Digital Contact Centre platform, integrating skill-based routing, IVR, chatbots, and Copilot.
VIVID created a comprehensive knowledge base of articles in SharePoint which can be interrogated using a customised chatbot built with Microsoft Copilot Studio Since its launch, knowledge articles have been viewed more than 500,000 times, supporting digital self-service and contributing to reduced voice traffic volumes.
Transparency Evidence & methodology 91/100 reference value · 89% confidence · 1 source

Review how this reference was scored and trace each normalized claim back to its documented source.

01

Scoring methodology

How scores are calculated

Customer Reference Value measures usefulness as a customer reference. Evidence Confidence measures the quality and traceability of available evidence, not independent verification.

Customer reference value91/100
  • Problem clarity20/20
    Measures whether the customer's operational problem is specific enough to compare.
  • Implementation depth20/25
    Rewards named components, data flow, integrations, and architecture detail.
  • Outcome specificity16/20
    Measures whether the reported benefit is concrete rather than a generic claim.
  • Quantified impact25/25
    2 metrics describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence89%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability21/25
    10 of 12 key fields link to a named source.
  • Direct evidence20/20
    6 direct source quotes retained.
  • Date provenance10/10
    The publication date comes from the source page or publisher.
  • Source transparency8/10
    1 source reference document publisher, URL, authority, retrieval, and supported fields.
  • Implementation specificity10/10
    Rewards source-backed components, data flow, quantified impact, and a specific outcome.
02

Traceability

Sources & provenance

Field coverage shows which facts each source supports. Dates are shown only when documented by the source.

  1. Microsoft

    VIVID customer story

    First-party
    https://www.microsoft.com/en/customers/story/19820-vivid-azure
    Source type
    Vendor-published customer story
    Published
    Dec 3, 2024
    Supports
    • Customer
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Metrics
    • Architecture
    • evidence quotes
    • Publication date

Date evidence

  • Published on source page Dec 3, 2024 · Microsoft · First-party
    Open date source
Not separately sourced Industry, Region, Company size. Treat these normalized attributes as lower-confidence until a dedicated source is added.