IBM Software / SaaS United States

MacStadium

Customer Service Automation

MacStadium's support technicians were fielding high volumes of repetitive product questions, leading to inconsistent response quality and slower resolution for customers using the Orka platform.

25% reduction in customer support queries
30% increase in staff efficiency
90% accuracy rate
three-week pilot

Reported impact

Business outcome

MacStadium improved support efficiency, reduced inbound support demand and demonstrated expert-like, high-accuracy responses that can expand from Orka support into broader cloud-configuration assistance.

  • Customer Experience
  • Productivity Improvement
  • Scalability

Solution

MacStadium partnered with Innovative Solutions to pilot a generative-AI support assistant that combines IBM watsonx Assistant with Amazon Bedrock. The design centers on a chat interface delivered through watsonx Assistant, while Amazon Bedrock queries the knowledge sources selected by MacStadium and summarizes the findings for each user request. The assistant was built to support developers using Orka, MacStadium's Kubernetes-native virtualization platform for Apple-device build infrastructure, and to remove low-complexity questions from the queue that previously reached on-call technicians. During the three-week pilot, the team evaluated how quickly the assistant could blend information from documentation and return expert-like responses without relying on whichever technician happened to be on duty. The resulting architecture gave MacStadium an always-available front line for developer support and a path toward broader configuration and cloud-assistance scenarios.

Data flow

Developer questions enter through watsonx Assistant, Amazon Bedrock queries the documentation and other MacStadium knowledge sources, generates a summarized answer, and the response is returned through the support chat interface.

Solution architecture

2 components · 2 layers
  1. Compute
    • Amazon Bedrock Queries MacStadium's selected data sources and summarizes the results that power the assistant's answers.
  2. Serving
    • IBM watsonx Assistant Provides the chat interface developers use to ask support questions and receive guided answers.

Architecture clues

  • The assistant often resolved questions in minutes that previously took hours.
  • The implementation combined IBM and AWS technologies rather than using a single-vendor stack.
  • The pilot focused first on Orka support and is intended to expand to other offerings.

Evidence from the source

25% reduction in customer support queries
30% increase in staff efficiency
Amazon Bedrock technology will query the various data sources determined by MacStadium and summarize its findings
The new assistant's chat interface is enabled by IBM watsonx Assistant
Transparency Evidence & methodology 95/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 value95/100
  • Problem clarity20/20
    Measures whether the customer's operational problem is specific enough to compare.
  • Implementation depth25/25
    Rewards named components, data flow, integrations, and architecture detail.
  • Outcome specificity20/20
    Measures whether the reported benefit is concrete rather than a generic claim.
  • Quantified impact25/25
    3 metrics describe measurable impact.
  • Deployment scale5/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
    4 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. IBM

    MacStadium customer story

    First-party
    https://www.ibm.com/case-studies/macstadium
    Source type
    Vendor-published customer story
    Published
    May 14, 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

Not separately sourced Industry, Region, Company size. Treat these normalized attributes as lower-confidence until a dedicated source is added.