Engine’s cover photo
Engine

Engine

Software Development

Powering connection through simplified travel

About us

Engine is the modern travel platform for booking and managing work trips. It saves businesses time and money through an intuitive travel network that connects to nearly every hotel, airline, and car rental company in the U.S. It offers single invoice billing, the flexibility to modify trips at any time without sunk costs, and a unified view of all company travel and spend. Customers rely on Engine to not only make travel easier to manage, but to make it enjoyable for everyone involved. The company is backed by Telescope Partners, Blackstone, Elefund and Permira. Learn more at www.engine.com.

Website
engine.com
Industry
Software Development
Company size
1,001-5,000 employees
Type
Privately Held
Founded
2019
Specialties
travel management, business travel, corporate travel, SMB, enterprise, travel tech, software, members only, travel, and software

Employees at Engine

Updates

  • Engine reposted this

    We were the first company to ship Agentforce Voice in production. Not a demo. Not a pilot. A live voice agent handling real customer calls — starting with cancellations, then extending to full parity with our chat agent. The result: cancellation calls handled without a human queue. Customers get answers immediately. Reps got their afternoons back for higher-value work. The thing that let us scale wasn't the AI. It was the governance around it. Here's the pattern running in production right now: Prompt A classifies every call against a fixed taxonomy. The categories live in Custom Metadata — a Salesforce config layer that non-engineers can edit — not in the prompt. So they can govern the taxonomy without touching code. A Salesforce Flow validates that classification deterministically. Wrong category? Reject. Missing field? Reject. Sentiment score doesn't match the sentiment label? Reject. The Flow has zero opinion. It's a gate. Prompt B then audits the classification semantically. Its only job is to try to disprove what Prompt A said. If it can't, the classification stands. The non-obvious win: when something breaks, you know exactly which layer broke. Prompt A wrong? Retrain the classifier. Flow rejecting valid calls? Adjust the rule. Prompt B drifting? Tighten the template. No more "the AI is broken, somewhere, somehow." At production scale, the monitoring system matters more than the generation system. The AI that classifies your calls is important. The system that catches when it's wrong is what lets you sleep at night. What patterns are you using to govern AI outputs in production? Curious what's working beyond the demo stage. #Agentforce #Salesforce #AIAutomation

  • View organization page for Engine

    38,434 followers

    AI is the future for fintech and if you want to win, you better build for it. Our FinTech PD leadership showed up to Stripe Sessions this week. Three days deep in the future of payments, agentic finance, and how AI is changing the way businesses move and manage money. Real-time reconciliation, embedded controls, and agentic AI. Collapsing the stack into fewer but smarter layers.

    • No alternative text description for this image
  • Engine reposted this

    This week at Salesforce TDX, Engine was highlighted in the keynote. Our Agentforce architecture was featured in the three demos. And Salesforce gave me the Golden Hoodie - one of the rarest honors in the ecosystem. But I need to be clear: that hoodie belongs to this team. We didn't get here by building the perfect agent on day one. We got here by taking action, learning from feedback, and scaling what worked. We started small. One agent. One use case. We looked at our own customer data - actual conversation transcripts, actual pain points, not vendor examples or best practices. We found the problem that would deliver real value, built Eva to solve it, and let real customers tell us what worked and what didn't. Action produces feedback. Feedback is how you get better. That foundation let us scale. One agent became many. Chat became voice, email, Slack agents, Employee Agents. We went from automating one use case to building an agentic enterprise. Today: 50% autonomous case resolution. CSAT up from 3.7 to 4.3. Real production impact. Joshua Stern gave me the trust and room to build. Angel Jaime drove product direction. The OpEx team led by Demetri Salvaggio pressure-tested every conversation until the numbers were undeniable. I got to represent Engine on stage, on a live Salesforce+ panel, and in media interviews. But every time I explained what we built, I was sharing their work. If you're thinking about Agentforce: start small, use your own data to find the right problem, take action, learn from feedback, then scale what works. The Golden Hoodie has my name on it, but Engine earned it.  #Agentforce #Salesforce #TDX

    • No alternative text description for this image
    • No alternative text description for this image
    • No alternative text description for this image

Similar pages

Browse jobs

Funding

Engine 3 total rounds

Last Round

Series C

US$ 140.0M

Investors

Permira
See more info on crunchbase