Matches chat visitors to their Plain record, checks tier before answering, opens and replies to threads, and updates group membership.
22actions available
Every action runs live through MCP. Nothing to build, nothing to maintain.
Ayro creates a new support thread in Plain. Agents open tickets without switching to a separate system.
Ayro sends a message within a thread to respond to customers. Agents reply directly within Plain's unified inbox.
Ayro retrieves customer details by email address. Agents look up accounts instantly without database searches.
Each card is one request a support team gets, and the Plain actions Ayro runs to close it.
Ayro looks the customer up by the email they typed, reads the tier attached to them, and pulls the company profile with its contract value and account owner before answering an entitlement question.
When a conversation needs a record, Ayro ensures the customer exists, creates the thread in their name, and sends the first message so support picks up a thread that is already complete.
Ayro adds a customer to a beta or premium group, removes them when the plan changes, and lists existing groups first so nobody creates a second version of one that already exists.
Ayro reads the Jira, Linear, or GitHub links attached across that customer's threads and returns the status with the thread each one came from, instead of a promise that engineering is looking at it.
How it works
Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Ayro reads the Plain actions it has and picks the ones a request needs.
Authorize the Plain account your team already uses — one consent screen, no API keys, no mapping tables. Ayro 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. Ayro maps it to the Plain 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 freePlain · Ayro
What can you do in Plain without me setting anything up?
These, right away:
Great, let's start with the first one.
FAQ
Setup, permissions, and the limits of what Ayro can do inside Plain.
Fetch Issues returns the external issue tracker links - Jira, Linear, GitHub - across every thread belonging to that customer, with the thread context for each one. It returns up to 2,500 links by default and truncates beyond that, so large accounts should be queried with a smaller thread limit.
All 22 actions your agent can call on Plain, straight from the live MCP connection.
Add a customer to one or more customer groups.
Creates a new customer group in Plain for organizing and segmenting customers.
Create a new thread.
Delete a customer from the system.
Delete a user from the system.
Fetch company details by ID.
Fetches external issue tracker links (Jira, Linear, GitHub, etc.) associated with a customer's threads.
Fetch a tier by its ID.
Fetch customer details by email address.
Retrieve details of a specific customer by their unique ID.
Fetch a list of customers.
Fetches comprehensive details of a specific thread by ID, including customer info, status, priority, labels, and assignments.
Fetch workspace user/team member by ID.
List all customer groups.
Retrieve a list of tiers with pagination.
Retrieve a paginated list of threads.
Removes a customer from one or more customer groups in Plain.
Execute any GraphQL query or mutation against Plain API.
Send a new message within a thread.
Upserts (creates or updates) a company in Plain.
Update a thread's title.
Upsert (create or update) a customer.
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 a customer's full thread history, posts replies and internal notes, tags and snoozes incoming conversations, and reports on inbox performance.
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.
Lists the chatbots on an account, retrieves the leads they captured, and reads the smart prompts configured on a given bot.
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 22 actions from the first conversation.
