AWS Telecommunications Estonia

Wildix

Customer Service Automation

Based in Estonia, Wildix has offered unified communications solutions since 2005 and provides services to 2 million users worldwide. The company focuses on enhancing its customers' sales processes through its communications solutions.

"Using AWS was crucial for our company to be able to move forward quickly and not miss this window of opportunity." Wildix accelerated innovation by 80 percent and achieved a 70...
Based in Estonia, Wildix has offered unified communications solutions since 2005 and provides services to 2 million users worldwide.
Results acceleration in innovation for x-hoppers 80% faster time to market for x-hoppers 70% decrease in employee training time for x-hoppers' customers 50% increase in sales for...
The x-hoppers solution also uses Amazon Redshift —which powers data-driven decisions with the best price performance cloud data warehouse—and AWS Lambda —which runs code in...

Reported impact

Business outcome

Wildix continues to add more features to x-hoppers. In some cases, Wildix has been able to implement new features directly requested by active customers, such as adding a voice imprint functionality to the headsets to authenticate which employee used which headset during a shift.

  • Customer Experience
  • Productivity Improvement
  • Revenue Growth

Solution

With more customers shopping online, and with the rise of remote work, in-store foot traffic isn't what it used to be. Wildix, a provider of unified communications solutions, saw an opportunity to offer innovative support to brick-and-mortar retailers to help them meet these modern challenges. Wildix recognized that to compete with online competitors, in-person stores must be able to offer efficient and personalized customer service with lean staff teams. The company sought to build a solution that could offer near real-time communication through the cloud and integrate with existing and future in-store systems. To modernize quickly, the company chose to build its complete retail headset solution, x-hoppers, on Amazon Web Services (AWS).

Data flow

Push-to-talk communication for in-store associates, broadcasts across multiple departments, and external phone calls can all be handled through the headset and associated application. If a customer asks a question that a store employee doesn't know the answer to, the employee can ask AI in natural language, as if they were asking a knowledgeable colleague. "Using AWS significantly accelerated our innovation process," says Hölzl.

Solution architecture

4 components · 4 layers
  1. Ingest
    • Amazon Transcribe Converts voice interactions into text for the customer and agent support workflows.
  2. Compute
    • AWS Lambda Executes serverless processing and workflow glue for the customer and agent support workflows.
  3. Storage
    • Amazon Redshift Serves as the analytics warehouse for the customer and agent support workflows.
  4. Serving
    • Amazon Polly Generates speech output used by the customer and agent support workflows.

Architecture clues

  • The company sought to build a solution that could offer near real-time communication through the cloud and integrate with existing and future in-store systems.
  • The x-hoppers solution also uses Amazon Redshift —which powers data-driven decisions with the best price performance cloud data warehouse—and AWS Lambda —which runs code in response to events and...

Evidence from the source

Based in Estonia, Wildix has offered unified communications solutions since 2005 and provides services to 2 million users worldwide.
To modernize quickly, the company chose to build its complete retail headset solution, x-hoppers, on Amazon Web Services (AWS).
Using AWS, Wildix accelerated the innovation process and improved verticalization to better support the needs of its brick-and-mortar retail clients.
When Wildix first began discussing the x-hoppers solution in 2020, it decided to use AWS for the project because it was confident that doing so would mean it could build a reliable solution quickly.
Wildix had been using AWS since 2013 for security and in its private branch exchange (PBX) infrastructure for telecommunications, taking advantage of the internationally reliable service that AWS offers as the company expanded across...
Wildix recognized that to compete with online competitors, in-person stores must be able to offer efficient and personalized customer service with lean staff teams.
Transparency Evidence & methodology 91/100 reference value · 87% 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 confidence87%
  • 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 provenance8/10
    The publication date comes from publisher-controlled metadata.
  • 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. AWS

    Wildix customer story

    First-party
    https://aws.amazon.com/solutions/case-studies/wildix
    Source type
    Vendor-published customer story
    Published
    Jul 7, 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.