What does Lyro need to know about a prospect before Autobound is useful?

Enough to resolve them. Generate Insights is designed to run after identifiers are resolved, and Generate Personalized Content after contact and user details are confirmed, so Lyro collects the email or company domain in conversation first - without one, neither action has anything to personalize against.

How does Lyro decide which insight to lead the message with?

It does not rank them itself. Generate Insights returns prospect and company insights already ordered by relevance, so Lyro takes the top of that list and feeds it into Generate Personalized Content rather than applying a scoring model of its own.

Can Lyro tell us whether a prospect opened or replied to the outreach?

No. The connected toolkit exposes two actions, Generate Insights and Generate Personalized Content, and neither returns engagement data. Autobound produces the research and the draft; sending, tracking, and reply handling stay with your sequencer or inbox.

How is this different from running Autobound through Zapier or Make?

A Zap fires a fixed sequence whenever its trigger matches. Lyro judges mid-conversation whether it has enough identifying detail to call Generate Insights at all, asks for what is missing, and only generates content once the research came back - so a thin lead does not quietly produce a generic draft.

Autobound MCP integration

Pulls ranked insights on a prospect or company, then drafts outreach built on those specific findings rather than a generic template.

Connect Autobound See all integrations

2actions available

What your agent can do with Autobound

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

Generate insights
Lyro generates ranked prospect and company insights for sales conversations. Reps discover conversation angles and decision drivers without manual research.
Generate personalized content
Lyro generates hyper-personalized sales content tailored to a prospect. Emails and pitches feel custom-built instead of templated.

See all 2 actions

How businesses use Autobound + Lyro

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

Brief a rep on an account before the call
Lyro resolves the prospect's identifiers from the conversation, pulls ranked person and company insights, and reports the top ones back, so the rep walks in with current context rather than a name and a job title.
Generate InsightsGenerate Personalized Content
Draft outreach around what the prospect actually cares about
Once contact and user details are confirmed, Lyro generates personalized content built on the ranked insights it just pulled, so the message references something real about the account instead of a merge field.
Generate Personalized ContentGenerate Insights
Qualify an inbound lead and hand over a ready first touch
When someone new arrives in chat, Lyro gathers enough detail to resolve them, checks what the insights say about their company, and passes the rep both the research and a drafted opener.
Generate InsightsGenerate Personalized Content

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 Autobound actions it has and picks the ones a request needs.

01
Connect Autobound
Authorize the Autobound 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 Autobound 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

Autobound · Lyro

Everything else about Autobound

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

Enough to resolve them. Generate Insights is designed to run after identifiers are resolved, and Generate Personalized Content after contact and user details are confirmed, so Lyro collects the email or company domain in conversation first - without one, neither action has anything to personalize against.