What Headout information can Lyro access?

Only what the connected Headout account authorizes. Lyro uses that connection strictly to look up current booking data and trigger updates - nothing beyond what the account access covers.

What happens if a Headout booking can't be found?

If Lyro's lookup doesn't return a matching Headout record, it says so rather than guessing, and can hand the conversation to a teammate if that's what solves the customer's question.

Can a Headout lookup happen alongside other tools Lyro is connected to?

Yes - each integration works independently, so checking a Headout booking can be one step in a conversation that also touches other connected tools.

How is asking Lyro about a Headout booking different from checking Headout directly?

It's the same booking data, surfaced inside the conversation instead of a separate login. Lyro's Headout connection only covers looking up data and triggering updates - it doesn't add capabilities Headout itself doesn't have.

Headout MCP integration

Looks up Headout booking data and triggers updates from inside the conversation.

Connect Headout See all integrations

3actions available

What your agent can do with Headout

Every action runs live through MCP. Nothing to build, nothing to maintain.

Look up Headout data
Lyro fetches current booking and event data from Headout relevant to the customer's inquiry. Support teams answer questions about availability and pricing instantly.
Trigger a Headout update
Lyro updates bookings or customer records in Headout as part of a support workflow. Agents make changes without leaving the conversation to access the Headout platform.

How businesses use Headout + Lyro

Each card is one request a support team gets, and the Headout actions Lyro runs to close it.

Answer a booking status question
When a customer asks about an upcoming Headout booking, Lyro looks up the current record and answers directly instead of sending them to check themselves.
Connect Headout AccountLook Up Headout Data
Trigger a change agreed in chat
Once a change to a booking is confirmed in the conversation, Lyro triggers the matching Headout update instead of leaving it for someone to enter later.
Look Up Headout DataTrigger Headout Update
Confirm details before changing a booking
Lyro looks up the current Headout booking first and only triggers an update once the details match what the customer confirmed.
Connect Headout AccountLook Up Headout DataTrigger Headout Update
Handle a booking question as part of a bigger request
When a conversation covers more than one topic, Lyro can look up the Headout booking as a single step and keep handling the rest itself.
Look Up Headout DataTrigger Headout Update

How it works

Get started in 3 steps

Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Lyro reads the Headout actions it has and picks the ones a request needs.

01
Connect Headout
Authorize the Headout account your team already uses — one consent screen, no API keys, no mapping tables. Lyro can only do what you granted that account, and you can disconnect it at any time.
02
Tell your agent what you need
Describe the job the way you would hand it to a teammate. Lyro maps it to the Headout actions that close it and chains as many as the request needs.
03
Watch it work
The agent runs the actions inside the conversation the customer is already in, so nobody copies data between tabs and your team can take over at any point.
Get started free

Headout · Lyro

Everything else about Headout

Setup, permissions, and the limits of what Lyro can do inside Headout.

Only what the connected Headout account authorizes. Lyro uses that connection strictly to look up current booking data and trigger updates - nothing beyond what the account access covers.