Accenture Public Sector Singapore

Singapore Ministry of Manpower

Customer Service Automation

Singapore's Ministry of Manpower needed to handle a growing volume of employment disputes faster and with less manual effort while keeping the process accessible, multilingual, and compliant for workers, employers, and mediators.

28% of cases not requiring in-person mediation
35k user hours saved annually
41% increase in e-file cases
available in five languages, covering 95% of Singapore's claimants

Reported impact

Business outcome

MOM and TADM reduced friction for claimants, shortened case turnaround, increased self-service adoption, and created a repeatable digital process that improves public-service accessibility while saving staff and user time.

  • Customer Experience
  • Productivity Improvement

Solution

Accenture helped Singapore's Ministry of Manpower and the Tripartite Alliance for Dispute Management build EmPOWER, a cloud-native dispute-resolution platform that digitizes the end-to-end claims journey. The solution combines AWS cloud-native services, a Google Dialogflow CX chatbot, PEGA case management, SingPass authentication, and self-help tools such as e-calculators and eligibility checks. Claimants start in the chatbot, which answers questions, pre-populates claim details, and passes structured inputs into the portal and workflow engine. PEGA then orchestrates case handling, routing, and officer actions, while data is stored locally in Singapore to satisfy sovereignty and public-sector security requirements. The result is a multilingual, guided process that reduces form-filling friction, limits manual errors, and gives officers cleaner data and faster case progression from intake through resolution.

Data flow

Claimants authenticate with SingPass, interact with the Dialogflow CX chatbot, and use calculators and eligibility checks before their answers are passed into EmPOWER and PEGA. Case data is then routed through officer workflows on AWS and stored locally in Singapore for secure, compliant dispute processing.

Solution architecture

5 components · 4 layers
  1. Compute
    • AWS cloud-native services Provide the cloud foundation that hosts and scales the dispute-resolution platform.
  2. Serving
    • EmPOWER Serves as the shared digital platform for guided claim intake, dispute handling, and resolution workflows.
    • Google Dialogflow CX chatbot Handles multilingual claimant interactions and captures structured information before a case is submitted.
  3. Orchestration
    • PEGA case management platform Routes, tracks, and manages dispute cases from intake through officer resolution steps.
  4. Governance
    • SingPass Authenticates claimants and connects the chatbot and portal to Singapore's trusted digital identity system.

Architecture clues

  • All data is stored locally in Singapore to meet government security and compliance standards.
  • Chatbot inputs are pre-populated into the claim portal and PEGA workflows.
  • Self-help tools are embedded in the digital journey to improve data quality before submission.

Evidence from the source

"All data is stored locally in Singapore to meet government security and compliance standards."
"Chatbot integration with PEGA pre-populates user inputs, cutting form-filling time by one-third."
"Let's look back at how EmPOWER resolved Fred's case in just 4 weeks (2x faster than manual processing!)."
"The system integrates AWS cloud-native services, Google Dialogflow CX chatbot, and the PEGA case management platform to streamline case handling from start to finish, minimizing human errors."
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
    5 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 traceability19/25
    9 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 transparency10/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. Accenture

    Digital Solutions for Dispute Resolution | Accenture

    First-party
    https://www.accenture.com/en/case-studies/cloud/digital-solutions-dispute-resolution
    Source type
    Vendor-published customer story
    Published
    May 15, 2026
    Supports
    • 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 May 15, 2026 · Accenture · First-party
    Open date source
Not separately sourced Customer, Industry, Region, Company size. Treat these normalized attributes as lower-confidence until a dedicated source is added.