Why can a brand new visitor come back empty?

LeadBoxer needs a moment to populate a record after the first pageview; the documented pattern is roughly a three-second delay after lead creation before reading it. A Get Lead Detail call fired the instant someone lands can therefore return less than the same call a few seconds later.

Our account has more than one dataset. Does Lyro know which to use?

It has to be told, because several actions are dataset-scoped: Get Lead Score Formula, Get Custom Tracking Domains, and Delete Custom Tracking Domain all take a datasetId. Point Lyro at the dataset for the site in question and lookups stay inside it.

Can Lyro create a new lead in LeadBoxer?

No. The toolkit exposes no create-lead action, because leads come from LeadBoxer's own visitor tracking. What Lyro can do is feed that tracking with Log Server-Side Event or Post Event Data, then read and tag the record LeadBoxer builds from it.

Could Lyro wipe the tags a sales team already set?

Add or Update Lead Tags supports adding tags, removing specific tags, and overwriting all existing tags for a user, so the overwrite mode is the one to gate. Restrict Lyro to adding and removing named tags and the tags your team maintains by hand stay intact.

LeadBoxer MCP integration

Pulls a lead's sessions and event history, retags records as qualification changes, and logs conversions back from the conversation.

Connect LeadBoxer See all integrations

9actions available

Three actions you can hand over today

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

Get lead detail
Lyro looks up comprehensive lead information including profile and scoring data. You qualify prospects or understand their engagement history instantly.
Add or update lead tags
Lyro tags leads with custom labels to organize and segment your prospect list. Your sales team immediately sees how to prioritize and route follow-ups.
Get sessions
Lyro retrieves all browsing sessions for a lead showing what pages they visited. You understand engagement patterns to tailor your response and timing.

See all 9 actions

How businesses use LeadBoxer + Lyro

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

See what a lead actually did before they wrote in
Lyro pulls the detailed lead record, the sessions behind it, and the individual pageviews, clicks, and form submissions in each one, so a reply can reference the page the visitor was stuck on.
Get Lead DetailGet SessionsGet Events
Tag a lead the way the scoring model expects
Lyro reads the dataset's lead score formula to see which ranges, matches, and event boosts actually move a score, then adds or updates tags on the record so qualification is logged consistently.
Get Lead Score FormulaAdd Or Update Lead Tags
Log conversions that happen outside the browser
When a customer completes something in chat or on the backend, Lyro sends the event to LeadBoxer server-side so it counts toward that visitor's behaviour instead of disappearing.
Log Server-Side EventPost Event Data
Audit the custom tracking domains on a dataset
Lyro lists the custom tracking domains created or still in progress for a dataset and removes an entry pointing somewhere the team no longer controls.
Get Custom Tracking DomainsDelete Custom Tracking Domain

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

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

LeadBoxer · Lyro

Everything else about LeadBoxer

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

LeadBoxer needs a moment to populate a record after the first pageview; the documented pattern is roughly a three-second delay after lead creation before reading it. A Get Lead Detail call fired the instant someone lands can therefore return less than the same call a few seconds later.

Every action available in LeadBoxer

All 9 actions your agent can call on LeadBoxer, straight from the live MCP connection.

Add or update lead tags
Add or update lead tags in LeadBoxer.
Delete custom tracking domain
Delete a custom tracking domain entry for a dataset.
Get events
Fetch events for specified sessions from LeadBoxer.
Get lead score formula
Fetch the lead score formula for a specific dataset.
Get sessions
Fetch sessions for a specified lead ID from LeadBoxer.
Log server-side event
Track server-side events in LeadBoxer.
Get custom tracking domains
Fetch custom tracking domain entries for a dataset.
Post event data
Send event data for tracking user activities via POST request.
Get lead detail
Fetch detailed information about a lead based on filters.