FixTrip: voice-first trip repair on WhatsApp, powered by Vocal Bridge

Forward a broken itinerary into WhatsApp, talk it through once, and the agent rebooks the flight through Sabre and phones the restaurant itself, built on Vocal Bridge's Voice for your app surface.

The problem: support disappears exactly when a trip breaks

A canceled flight rarely breaks one thing. It breaks the whole chain. Miss the flight home and the dinner reservation, the hotel checkout, and the ride all fall out of alignment at once. The traveler is usually in an airport, on a phone, with a weak connection and no patience for a support queue.

Henry Gardner spent nine months traveling Southeast Asia and came back with the insight behind FixTrip. WhatsApp is the one app almost every traveler already has open. Travelers want to keep control of the booking decisions, not hand their trip to a black box. And the moment something goes wrong is the exact moment human support goes quiet.

What FixTrip built

FixTrip turns trip repair into a single conversation. A traveler forwards a multi-page itinerary into a WhatsApp chat, and the agent parses it into a live view of every flight, hotel, and reservation. From there the traveler just talks. FixTrip searches and rebooks the flight through Sabre, handles the fare difference through a PayPal portal it drops into the chat, and, for the pieces of a trip that live behind a phone number rather than an API, it calls the business directly and negotiates on the traveler's behalf. Every step is confirmed back into the same thread.

Voice is what lets the agent both take the request in plain speech and act on the world by speaking to another human.

How they use Vocal Bridge

FixTrip is built on Vocal Bridge's Voice for your app surface, carrying two live audio channels for the same task: the traveler talking to the agent, and the agent talking to a restaurant. The team owns the trip model, the Sabre integration, the payment flow, and the WhatsApp bridge. Vocal Bridge owns the real-time voice: streaming speech both ways, placing the outbound call, sub-second turn-taking, barge-in, and the conversational fillers that keep both sides grounded while a booking runs.

from vocalbridge import Agent, tool

agent = Agent(name="fixtrip")

@tool
async def rebook_flight(origin, dest, date, carrier):
    await agent.say("Pulling up those flights now.")  # fills dead air
    options = await sabre.search(origin, dest, date, carrier)
    await ui.push("flight_options", options)           # live UI update
    return options

@tool
async def call_business(phone, request):
    return await agent.dial(phone, objective=request)  # second live session

Illustrative. The production agent handles richer itinerary state and payment reconciliation.

What's hard about voice here

• Dead air while a booking runs. A Sabre search, a payment, or dialing a restaurant takes real seconds, and silence reads as a dropped call. FixTrip leans on streaming speech and conversational fillers to keep the traveler grounded while the tool completes.
• Negotiating live with another human. The outbound call is the risky part. The restaurant offers 8:15 instead of 8:00, and the agent has to hear it, accept it, and confirm the changed detail without talking over the employee. That depends on sub-second turn detection and barge-in.
• Keeping speech and the chat in sync. Every booking has to land back in the thread and the options view, or the traveler loses trust. FixTrip drives those updates off the agent's actions on the Vocal Bridge data channel.

FixTrip already demonstrates the complete recovery loop, from a broken itinerary to a rebooked flight, a negotiated reservation, and a payment handoff. The production path is to harden the visible seams: keep the voice responsive, recover cleanly when a person interrupts or a call drops, and make every confirmation unmistakable in the thread. Those are concrete UX and reliability levers the team can test one by one.

The quote

"One call and your trip is back together." Henry Gardner, FixTrip