Check tickets and attendee numbers for an event

Someone asks how the event is selling and the honest answer is that you would have to go and look. The numbers live across a few screens: ticket types in one place, attendee records in another, capacity buried in each ticket’s own settings.

This prompt gathers them and reports the shape of it. It cannot do anything else, and that is the interesting part. Event Tickets is exposed read only in this plugin, so there is no purchase, issuance, or refund path for an agent to reach for even if you asked it to.

I want to know how [the spring workshop] is selling. Read only, change nothing,
and do not list individual attendees.

List every ticket attached to that event, RSVP and paid. For each ticket type,
tell me its capacity and what it costs. If any single ticket needs a closer
look, read it on its own.

Then pull the attendee records for the event and give me counts only: how many
per ticket type, and how many for the event overall. I do not want names or
email addresses in your answer.

Finish with a short summary: total capacity, total taken, how much is left, and
which ticket type is moving fastest. If a ticket type has sold nothing at all,
say so plainly.

Why this is safe to run

Every ability here is a read, and there is no write to reach for. The plugin ships no ability that sells a ticket, issues one, or refunds one. That was a scope decision made and recorded during the integration work: the commerce flows differ per provider and none of them was verified against a real write path, so nothing was shipped rather than something half-checked. Your ticketing stays in your ticketing system.

Access is checked per event, not per site. All three abilities require the bound user to have edit access to that specific event, so a scoped-down agent user cannot browse the ticket sales for events it has nothing to do with.

There is one limit the plugin cannot set for you, so set it yourself. Attendee records describe real people, and an ability that can read them can just as easily read them into a chat window. Keep prompts like this on the operational question, meaning counts and remaining capacity, and do not ask an agent to export names or addresses. If you need the actual list, that is a job for your own admin screens under your own login, where the access is yours and the trail is obvious.

Already connected? Skip the paste. Ask your agent for the “check tickets and attendee numbers for an event” recipe, name the event, and it runs the same counts-only reads on your own site.