Google Cloud Software / SaaS Australia

Trillet

Customer Service Automation

Trillet needed to automate complex enterprise calls in sensitive industries, but earlier model choices produced unreliable answers and its fragmented infrastructure made it hard to scale voice workflows predictably and cost-effectively.

Achieves <1% error rate
Cuts infrastructure costs by ~80%
Reduces call escalations to <15%
Scales instantly to 3x traffic spikes

Reported impact

Business outcome

Trillet cut infrastructure cost, reduced escalations and error rates, and turned Google Cloud into a production voice layer that can automate most complex enterprise calls while maintaining the reliability demanded by sensitive industries.

  • Cost Reduction
  • Customer Experience
  • Scalability

Solution

Trillet moved its voice application layer to Google Cloud so conversational automation could be both predictable and scalable. Gemini in Vertex AI became the core reasoning engine, allowing the team to run with near-zero model freedom for high-stakes healthcare and enterprise interactions while still maintaining large context and fast responses. The models cross-reference live clinic databases and scheduling rules to formulate answers, which sharply reduced erroneous appointment responses compared with earlier LLM attempts. Google Kubernetes Engine and Cloud Load Balancing provide the elastic runtime needed to absorb large call spikes, while the unified Google Cloud stack removes the operational overhead of a fragmented black-box setup. This architecture lets Trillet orchestrate thousands of calls simultaneously, keep error rates below one percent, and combine real-time data access with strict AI control in a way that is suitable for regulated customer interactions.

Data flow

Caller requests enter through Cloud Load Balancing into services on GKE, where Gemini models on Vertex AI validate the request against live clinic data and scheduling rules. The resulting response is returned to the caller or escalated if needed, while the platform elastically scales for spikes in call volume.

Solution architecture

4 components · 3 layers
  1. Compute
    • Vertex AI Hosts Trillet's conversational AI workflows and enforces the controlled, low-variance reasoning needed for sensitive call handling.
    • Gemini Cross-references user requests against live databases and scheduling rules to produce accurate call responses.
  2. Serving
    • Cloud Load Balancing Distributes incoming call workload across the runtime environment.
  3. Orchestration
    • Google Kubernetes Engine Scales the voice application layer to handle thousands of calls and traffic spikes without manual intervention.

Architecture clues

  • Gemini in Vertex AI cross-references requests against a clinic's live database and scheduling rules
  • Google Kubernetes Engine and Vertex AI work together to handle thousands of calls simultaneously
  • The team set model temperature to zero to maximize determinism

Evidence from the source

Achieves <1% error rate using Gemini in Vertex AI
Cuts infrastructure costs by ~80% with Vertex AI
Gemini in Vertex AI cross-references the request against the clinic's live database and scheduling rules to formulate a response.
Moving to Google Cloud gave us the unified infrastructure we needed.
With Gemini in Vertex AI we gained the strictness, large context window, and predictability we needed for sensitive industries such as healthcare.
Transparency Evidence & methodology 95/100 reference value · 82% confidence · 2 sources

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 depth20/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 scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence82%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability23/25
    11 of 12 key fields link to a named source.
  • Direct evidence20/20
    5 direct source quotes retained.
  • Date provenance0/10
    The publication date has no documented provenance.
  • Source transparency9/10
    2 source references 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. Google Cloud

    Trillet customer story

    First-party
    https://cloud.google.com/customers/trilletai
    Source type
    Vendor-published customer story
    Supports
    • Customer
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Metrics
    • Architecture
    • evidence quotes
  2. LinkedIn

    Trillet AI | LinkedIn

    Platform-hosted self-reported
    https://www.linkedin.com/company/trillet-ai/

    The public company page shows 'Discover all 16 employees.'

    Source type
    Structured company profile
    Supports
    • Company size

Date evidence

  • First archived Apr 13, 2026 · Internet Archive · Independent First Wayback Machine capture; confirms the page existed by this date, not when it was published.
    Open date source
  • Sitemap last modified Mar 25, 2026 · Google Cloud · Publisher metadata Publisher-reported modification timestamp; not a publication date.
    Open date source
Not separately sourced Industry, Region. Treat these normalized attributes as lower-confidence until a dedicated source is added.