Checking ticket sales
Maya Okafor, marketing manager at Acme Ltd, asked how sales were going for the autumn conference. Memtro listed each ticket type with tickets sold against quantity on offer, and named the one that had sold out.
How many tickets have sold for our event, and is this person registered?
Tito connects Memtro to your event ticketing. It reads events, ticket types with price and tickets sold, registrations with who booked and their state, and tickets with attendee name and ticket type. Registrations also sync hourly. When asked, and once an administrator has granted the action by name, it creates and edits registrations and tickets, cancels registrations, voids tickets, reassigns a ticket, manages discount codes and puts ticket types on sale or pauses them. A refund through the payment provider moves money back and cannot be undone. Reassigning a ticket emails the new attendee. Use a live token.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Tito tool, reads what it needs, and answers with the source cited.
These tools change something in Tito. The model is told to use them only when you ask for exactly that, and an administrator grants each one by name to the teams that may use it; a personal connection acts only after its owner allows it.
Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in Tito, choosing the same kinds; the tab shows Tito's own steps. Each event can start a job, with the event as its input, and can be remembered where you choose. Tito signs every delivery, and one whose signature does not check out is refused before it is read.
Events and webhooksOnce Tito is connected, these are the kinds of things people ask. Plain questions, no syntax. If the answer lives partly in another system you have connected, Memtro looks there too.
How many tickets have sold for our next event?
Is Sarah Chen registered for the conference?
Which ticket types have sold out?
Who from BigCo has booked?
Create a 20% discount code SPEAKERS for the autumn conference, limited to 10 uses.
Maya Okafor, marketing manager at Acme Ltd, asked how sales were going for the autumn conference. Memtro listed each ticket type with tickets sold against quantity on offer, and named the one that had sold out.
Tom Reilly, on the Acme Ltd events team, heard that a Northwind delegate could no longer attend and her colleague James Patel would go instead. He asked Memtro to reassign her ticket. Memtro reassigned it to James, and Tito emailed James, the original booker and the organisers.
The teams that lean on Tito most, a question each of them asks, and what they connect beside it.
A record in Tito is rarely the whole story. Connect the systems that hold the rest and Memtro checks them together, then remembers what it learned so the next question starts further along.
Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.
Go to id.tito.io and choose Generate New Token. Set Type to secret, Mode to live and Version to 3.0, then copy it. The token can do anything your Tito user can, so Memtro changes things only through the actions an administrator grants.
Find your account slug in your Tito URLs (ti.to/<account>/<event>). Leave it blank if the token covers only one account.
In Memtro, open Connections → Tito and paste the token into Secret API token, with the Account slug if you need one.
Ask "How many tickets have sold for our next event?"
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Tito tools are the same everywhere.
Only when you ask, and only what it has been granted: create a registration for named ticket types, emailing the registrant only when asked; edit a registration's name, email, company, purchase order or source; cancel a registration and void its tickets; refund a registration through the payment provider, or record a manual refund; mark an invoiced registration paid, or back to unpaid; add a ticket for an attendee, or edit an attendee's name, email, company or tags; reassign a ticket to a new attendee, which emails them; void a ticket so it can no longer check in; create, change or delete a discount code; put a ticket type on sale or pause its sale. Every other tool reads, searches or lists. The Connections page labels the tools that act, an administrator grants each one by name to the teams that may use it, and a personal connection acts only after its owner allows it.
A personal connection serves only your own requests. A shared connection serves the organisation: everyone, or only the teams an admin chooses. Admins can always add shared connections; other members need the permission.
Credentials are encrypted at rest. Tool results are cached briefly so agent loops do not repeat identical calls, and the facts the model extracts are saved to your organisation's memory with provenance (system, record and link) so they can be checked and superseded. An hourly sync anchors recently changed Tito records into memory as entities.
Secret API token and optional account slug. Go to id.tito.io and choose Generate New Token. Set Type to secret, Mode to live and Version to 3.0, then copy it. The token can do anything your Tito user can, so Memtro changes things only through the actions an administrator grants.
Yes. Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in Tito, choosing the same kinds; the tab shows Tito's own steps. A job set to start "When an event arrives" then runs once for each matching event, with the event as its input. The run treats the event as outside data, never as instructions, and anything the run remembers is kept as unverified.
Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.
Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.
7-day free trial · card on file, nothing charged until it ends · cancel any time