Looks up ticket history, opens and replies to tickets, and keeps the queue tagged and deduplicated without an agent stepping in.
452actions available
Every action runs live through MCP. Nothing to build, nothing to maintain.
Lyro opens a Zendesk ticket via the voice API endpoint to log support requests. Support channels feed directly into Zendesk without manual entry.
Lyro posts a comment reply to a Zendesk ticket to move conversations forward. Agents respond to customers without leaving their primary tool.
Lyro marks a public comment as private to hide internal notes from customers. Teams redact sensitive info on the fly without editing in Zendesk.
Each card is one request a support team gets, and the Zendesk actions Lyro runs to close it.
Lyro searches the requester's ticket history and reads the latest comments, so a customer asking where their request stands gets the current status instead of waiting for an agent to look it up.
When a conversation needs a paper trail, Lyro opens a Zendesk ticket in the customer's own wording, attaches any file they sent, and posts the first reply so the thread starts complete.
Lyro tags incoming tickets by topic, merges the duplicate a customer filed twice, and applies status changes across a batch, so the queue an agent picks up is already sorted.
Before a handoff, Lyro matches the person in chat to their Zendesk user record, updates it if details changed, and pulls their open requests so the agent sees one history rather than two.
How it works
Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Lyro reads the Zendesk actions it has and picks the ones a request needs.
Authorize the Zendesk 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.
Describe the job the way you would hand it to a teammate. Lyro maps it to the Zendesk actions that close it and chains as many as the request needs.
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 freeFAQ
Setup, permissions, and the limits of what Lyro can do inside Zendesk.
Yes. The toolkit exposes brand-level actions including List Brands, Get Zendesk Brand, and List Brand Agent Memberships, so Lyro can scope a lookup or a new ticket to the right brand rather than treating the account as a single queue. Which brands it reaches follows the permissions on the Zendesk account you connect.
All 452 actions your agent can call on Zendesk, straight from the live MCP connection.
Preview how a Zendesk macro would affect a ticket without actually applying it.
Autocomplete problems in Zendesk.
Search for Zendesk users by name prefix using the POST /api/v2/users/autocomplete endpoint.
Check the host mapping validity for an existing brand in Zendesk.
Count deleted users in Zendesk.
Count tickets where the specified user is CCD (carbon copy distribution).
Count the number of records in a specific Zendesk custom object.
Count the number of organizations in Zendesk.
Create an access rule for a custom object in Zendesk.
Install a Zendesk app in the account.
Send a notification to currently open instances of a Zendesk app.
Search for Zendesk tags using autocomplete via POST request body.
Create a new automation in Zendesk.
Create a bookmark for a ticket in Zendesk.
Redact sensitive content from a ticket comment in Zendesk using the Agent Workspace method.
Create a bulk job to perform batch operations (create, update, delete, upsert) on custom object records in Zendesk.
Create a new record for a custom object in Zendesk.
Create an attachment for a custom object record in Zendesk.
Create a new custom ticket status in Zendesk.
Create a new deletion schedule in Zendesk that automatically deletes records matching specified conditions on a schedule.
Create a new dynamic content item with locale variants in Zendesk.
Create a new locale variant for an existing dynamic content item in Zendesk.
Add an identity (email or phone) to an end user's profile in Zendesk.
Create a group membership in Zendesk, assigning an agent to a group.
Bulk import tickets into Zendesk by posting up to 100 ticket objects at a time.
Create many locale variants for an existing dynamic content item in Zendesk.
Create many tickets in Zendesk in a single request.
Create many users in Zendesk in a single request.
Create a new trigger for a custom object in Zendesk.
Create a custom organization field in Zendesk.
Same connection, same setup. Pick the next one your team already uses.
Searches an indexed documentation base for grounded answers, keeps its sources re-indexed, and escalates the questions it cannot close.
Reads the ticket queue and saved views, reports agents, teams, and roles, and explains email routing, automation rules, and plan setup.
Messages known customers, filters who has interacted by channel or opt-in, and keeps agent availability and brand data current.
Reads approved response templates and report tags so replies use your team's own wording and categories, not a separate script.
Pull a customer's past responses and sentiment, upsert the customer and team member records behind them, and read the questions a score came from.
Registers WhatsApp contacts, replies inside the active session window, updates contact attributes, and moves chats to the right inbox status.

Authorize the account and your agent has all 452 actions from the first conversation.
