Can Lyro reply to or assign a Re:amaze conversation?

No. The actions available here are Get Report Tags and Get Response Templates, both reads. Lyro uses Re:amaze content to shape its own answers and handoffs, while sending, assigning, and closing conversations stay in Re:amaze.

Are the response templates account-wide or scoped to a brand?

Get Response Templates retrieves the templates for the brand behind the connected credentials, so a company running several Re:amaze brands gets that brand's canned responses rather than one merged list.

What use are report tags if Lyro cannot tag a conversation?

They tell Lyro which categories your team actually measures. Get Report Tags returns the tags used in reporting, so when Lyro summarises or routes a conversation it describes it in the same terms your reports already use.

How does Lyro decide which response template fits a question?

It matches the request against the templates Get Response Templates returns and follows the closest one, rather than working from a copy pasted into a separate knowledge base. When nothing fits, it hands the conversation to a human agent with the full history instead of forcing a template.

Re amaze MCP integration

Reads approved response templates and report tags so replies use your team's own wording and categories, not a separate script.

Connect Re amaze See all integrations

2actions available

What your agent can do with Re amaze

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

Get report tags
Lyro retrieves the list of tags used in Re:amaze reports to organize feedback. Your team understands how customer issues are categorized.
Get response templates
Lyro fetches response templates for your brand to speed up replies. Your team reuses vetted answers without retyping every time.

See all 2 actions

How businesses use Re amaze + Lyro

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

Answer in wording your team already approved
Lyro retrieves the brand's Re:amaze response templates and follows the one that fits, so a customer gets phrasing your support leads signed off rather than an improvised answer.
Get Response TemplatesGet Report Tags
Describe a conversation in your reporting vocabulary
Lyro reads the tags already used across Re:amaze reports, so the category it assigns a conversation lines up with what your dashboards measure instead of starting a parallel taxonomy.
Get Report TagsGet Response Templates
Hand off with the right template already surfaced
When a conversation needs a person, Lyro passes along the Re:amaze template that matches the request, so the agent picks up from approved wording instead of writing from scratch.
Get Response TemplatesGet Report Tags

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

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

Re amaze · Lyro

Everything else about Re amaze

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

No. The actions available here are Get Report Tags and Get Response Templates, both reads. Lyro uses Re:amaze content to shape its own answers and handoffs, while sending, assigning, and closing conversations stay in Re:amaze.