Can Lyro cancel a subscription or issue a refund in MoonClerk?

No. Every action here is a list - customers, payments, subscriptions, payment forms and discounts - so Lyro reads the billing record but does not change it. Cancellations and refunds stay with a human agent working in MoonClerk.

How does Lyro isolate one customer's charge out of the whole payment history?

List Payments filters by form, customer, date range and status, so Lyro narrows to the specific charge a customer is asking about instead of returning a page of unrelated transactions and guessing which one they meant.

Why does MoonClerk return customers and plans as the same thing?

That is MoonClerk's own model - its customer list is a list of plans, because a customer record exists in relation to the plan they signed up on through a payment form. Lyro reports it the way MoonClerk stores it rather than inventing a separate customer object.

What happens when a billing question needs a refund decision?

Lyro confirms the facts first - the charge from List Payments, the current subscription from List Subscriptions - then hands the conversation to a human agent with the full history attached, so the person deciding is not starting by asking the customer to repeat themselves.

Moonclerk MCP integration

Answers a billing question from live MoonClerk records - the payment, the subscription, the customer and the discount that applied.

Connect Moonclerk See all integrations

5actions available

What your agent can do with Moonclerk

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

List payments
Lyro displays all payment records in MoonClerk to answer customer billing questions instantly. Support teams check payment status immediately instead of asking customers for transaction IDs and dates.

See all 5 actions

How businesses use Moonclerk + Lyro

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

Answer a charge or renewal question from the record
Lyro finds the customer, filters their payments by date or status to identify the charge in question, and reads the subscription behind it to confirm what renews and when.
List CustomersList PaymentsList Subscriptions
Confirm which form and discount a customer signed up on
When a price does not match what the customer expected, Lyro checks the payment form they used and the discounts applied to customer records to explain the amount.
List Payment FormsList Discounts

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

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

Moonclerk · Lyro

Everything else about Moonclerk

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

No. Every action here is a list - customers, payments, subscriptions, payment forms and discounts - so Lyro reads the billing record but does not change it. Cancellations and refunds stay with a human agent working in MoonClerk.