An AI assistant can help staff find the right event, retrieve its registrations or update its description without moving through each dashboard screen. With Gomry MCP, compatible assistants can perform the account operations exposed by Gomry, using the signed-in staff member's permissions. The useful question is which task the connection can complete and what record it leaves behind.
For example, an organizer can ask for registrations for a named workshop and date, then ask the assistant to update that event's description using supplied text. Finding the registrations is a read operation; saving a description changes the event. A door volunteer and an administrator may have different access to those actions.
What staff can do through Gomry MCP
Gomry's documented tools include finding and creating Events, updating selected event fields, working with ticket classes and attendees, and reading payment records. Contact and reporting tools support other account tasks, such as finding a customer or reviewing sales for a specified period. The tools advertised to the connected assistant depend on the user's dashboard privileges.
This gives the team another way to work with its existing records. A request for Friday's workshop can return the event record; a request for its registrations can retrieve attendee details. Form answers use the application tools, so a basic attendee list should not be presented as a complete preparation list if the instructor also needs registration answers.
| Staff task | Available result | Detail that matters |
|---|---|---|
| Find an Event | Its event record | Organization, date and event identity |
| Retrieve registrations | Attendee and ticket details | Status and all required result pages |
| Prepare another Event | A newly created event record | Supplied date, location, price and capacity |
| Update a description | The saved text on the selected event | Correct target and intended text |
| Inspect a payment | Payment record and receipt information when available | Correct payment and status |
| Review sales | A supported report for the requested period | Dates, currency and the metric being counted |
The assistant needs a precise target before changing a record. “Move Friday's workshop to seven” is incomplete if there are two Friday workshops or if seven could mean morning or evening. Clarifying that request is part of completing the task correctly.
Keep the result tied to the right record
Tickets issued, registrations, checked-in guests and successful payments answer different questions. A registration total describes people expected to attend; it is not proof they arrived. If the team asks for attendance, the answer needs the relevant check-in state.
A list can also span several pages. Before using a total to prepare materials or contact customers, compare the retrieved records with the dashboard and include the relevant ticket statuses. For a participant's form answers, keep the answer connected to the person who submitted it rather than treating the buyer as every guest in a group purchase.
A useful completion message identifies the record and the saved change. “Description updated” should refer to the intended event and summarize what changed. If the tool fails, the assistant should distinguish a failed step from earlier work that succeeded.
Aven, external assistants and customer purchases have different roles
Aven is Gomry's assistant inside the product. Claude, ChatGPT and other compatible external assistants connect through Gomry MCP. Use the operations documented for that connection rather than assuming every Aven capability is exposed to an external client.
For a financial refund, use the dashboard or a supported Aven refund workflow with the required confirmation. The external MCP payment tools provide payment lookup, rather than a standalone payment-refund command. Ticket-status changes are separate operations and can affect capacity or refund handling, so staff should inspect the applicable ticket and payment outcome when changing a registration.
That distinction also matters when an event is canceled. Gomry's documented delete-event action hides the event and its public page; it does not refund tickets or notify attendees. Removing the listing therefore leaves customer communication and any refunds to be handled separately.
Customer ticket purchases through connected consumer applications follow another route. The AgentCard ticket-booking example explains one purchase integration. That route does not expand an organizer assistant's account permissions.
Match access to the person doing the work
Connect the staff role that will actually use the assistant. An administrator's demonstration does not show what a door-team account can do. The account's permissions should cover the records and changes that person needs for their job.
The confirmation experience can vary with the client, its settings and the action. Keep consequential changes tied to a clear request and inspect the saved result; do not rely on a universal promise that every write produces a new approval prompt.
Updating an event time and sending attendees a message are distinct outcomes unless a documented workflow connects them. If the request needs both, the completion should make clear which happened and what remains.
Recover from an incomplete action
If a request times out, inspect the record before retrying a write that could create a duplicate. A missing response does not establish that the server made no change.
For a request such as “refund Maria's Friday ticket and offer Saturday instead,” identify the correct booking and payment first. Then separate the refund, new offer and customer message according to the supported tools. A drafted message about a refund is not a completed refund.
The API and webhooks guide explains recovery and reconciliation when these account operations connect to another system.
Use the customer information the task needs
A headcount question usually needs totals, not every answer on a participant form. A sales summary may need currency-separated figures rather than a list of customer details. Use the staff role and information appropriate to the task.
Retention and model-training commitments depend on the Gomry and AI-provider products, settings and applicable agreements. Aven and an external assistant are different products. Review the terms for the setup the team chooses rather than extending one product's policy across every client.
Start with one workflow the team can verify
Begin with finding a named event and retrieving its registrations. Have the person who normally prepares that session compare the result with the dashboard. Include an ambiguous event name and a permission failure so the team can recognize when the assistant needs more information or cannot complete a step.
Then try a specific change on a suitable test event, such as saving a description from supplied text. Compare the saved field with the request and check that the assistant identifies the event it changed. Record corrections alongside any time saved before expanding the workflow.
The ChatGPT connection guide and Claude connection guide cover setup.
What is a useful first task?
Ask for registrations for one named event and date. Check the returned statuses and total against the dashboard before relying on the list for preparation.
Does connecting an assistant give it every account permission?
No. Gomry advertises tools according to the connected user's dashboard privileges. The client and its configuration also affect how staff experience confirmation and tool use.
Does deleting an Event finish a cancellation?
No. The documented delete action hides the event, but does not refund tickets or notify attendees. Those customer outcomes still need to be handled.