Salesforce Travel and Hospitality United States

Engine

Customer Service Automation

Engine needed a voice-support experience that could answer traveler questions, manage bookings, and handle hotel cancellations at scale without sounding robotic or forcing callers to repeat themselves to human agents.

10% of calls
50% of calls
75% of incoming calls
Within three months

Reported impact

Business outcome

Engine scaled voice support with a more human-sounding agent, rolled the system out to most inbound calls, and simplified rep work by handing off completed voice transcripts and summaries instead of forcing customers to restart the conversation.

  • Customer Experience
  • Productivity Improvement
  • Scalability

Solution

Engine launched a customer-facing voice-support workflow on Salesforce with Agentforce Voice at the front end and Agentforce for Service behind the scenes so high-volume travel calls can be handled conversationally. Because Engine's stack was already described as 'wall-to-wall Salesforce,' the project could use native CRM, customer-record, and service context instead of bolting a separate voice layer onto fragmented systems. NeuraFlash, Engine, and Salesforce iterated rapidly before and after general availability, testing live conversations, refining prompts and voice settings, and rolling traffic out in phases from 10% of calls to 50% and then 75%. When the AI cannot finish the task, the transfer includes a completed transcript and summary inside Agentforce for Service, which shortens handoffs, preserves traveler context, and lets reps focus on exceptions instead of re-collecting information.

Data flow

Incoming traveler calls are answered by Agentforce Voice, which uses CRM and Data 360 context to answer questions or complete tasks; if the workflow needs a human, the call is transferred into Agentforce for Service with a full transcript and AI summary already attached.

Solution architecture

4 components · 2 layers
  1. Storage
    • Salesforce CRM Provides the underlying customer and service context that powers the voice workflow.
    • Data 360 Supplies native customer-record context that makes the voice agent responsive and personalized.
  2. Serving
    • Agentforce Voice Handles natural voice conversations for traveler support, bookings, and cancellations.
    • Agentforce for Service Receives escalations with transcripts and summaries so human reps can continue the case quickly.

Architecture clues

  • Engine described its environment as 'wall-to-wall Salesforce,' which reduced integration friction.
  • The rollout was deliberately phased from 10% to 50% to 75% of calls.
  • Transferred cases arrive with a fully filled out voice transcript and summary in Agentforce for Service.

Evidence from the source

It's natively integrated with Salesforce CRM, Data 360, and customer records.
They were looking for a conversational voice agent that could answer traveler questions, manage bookings, and handle hotel cancellations end to end.
We started by routing about 10% of calls to Agentforce Voice ... Then we increased usage ... Now we're at 75% of incoming calls.
When a case gets transferred, reps see a fully filled out voice transcript and summary in Agentforce for Service.
Transparency Evidence & methodology 96/100 reference value · 94% confidence · 3 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 value96/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 specificity16/20
    Measures whether the reported benefit is concrete rather than a generic claim.
  • Quantified impact25/25
    3 metrics describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence94%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability25/25
    12 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 transparency9/10
    3 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. Salesforce

    Engine customer story

    First-party
    https://www.salesforce.com/customer-stories/neuraflash-tom-hebner-interview/
    Source type
    Vendor-published customer story
    Published
    May 14, 2026
    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
  2. LinkedIn

    Engine

    Independent secondary
    https://www.linkedin.com/company/engine/

    Headquarters Denver, Colorado

    Source type
    Structured company profile
    Supports
    • Region
  3. LinkedIn

    Engine | LinkedIn

    Independent secondary
    https://www.linkedin.com/company/engine/

    The Organization JSON-LD lists addressLocality 'Denver', and addressCountry 'US', and numberOfEmployees value 1194.

    Source type
    Structured company profile
    Supports
    • Company size
    • Region

Date evidence

  • Published on source page May 14, 2026 · Salesforce · First-party
    Open date source
Not separately sourced Industry. Treat these normalized attributes as lower-confidence until a dedicated source is added.