Client review prep
Tom Reilly, service manager at BigCo, asked what was open for Northwind before a client review. Memtro listed the open tickets with status, agent and priority, and the invoices with an amount still due.
Which open HaloPSA tickets does a client have with the 1st Line team?
HaloPSA connects Memtro to your service desk. It reads tickets by status, client, agent or type with their notes and replies, and the clients, sites, end users, assets and invoices around them. It also reads the statuses, ticket types, agents, teams and priorities that ids refer to. When asked and granted, it can log, update or delete tickets, add a private note or delete one, and create or update clients, sites, users and assets. Halo's own rules may email the end user about a new or changed ticket. Asset custom fields, where credentials are often kept, are never returned.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right HaloPSA tool, reads what it needs, and answers with the source cited.
These tools change something in HaloPSA. 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.
Once HaloPSA 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.
Which open tickets does Northwind have with the 1st Line team?
What was the last reply on ticket 10423?
Which Acme Ltd invoices still have an amount due?
Which assets are at the Leeds site?
Add a private note to ticket 10423 that the engineer is booked for Tuesday.
Tom Reilly, service manager at BigCo, asked what was open for Northwind before a client review. Memtro listed the open tickets with status, agent and priority, and the invoices with an amount still due.
Priya Sharma, 1st Line lead at BigCo, asked Memtro to log a ticket for Acme Ltd about a failed backup. As granted, Memtro logged it with the ticket type and team she named. Halo's ticket-type rules decided who was notified.
The teams that lean on HaloPSA most, a question each of them asks, and what they connect beside it.
A record in HaloPSA 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.
In Halo, an administrator opens Configuration, Integrations, Halo API, View Applications, New. Set Client Credentials, choose the agent and permissions, save, and copy the client ID and secret.
In Memtro, open Connections → HaloPSA and enter the Halo address without https://, the Client ID and the Client secret. Hosted Halo also needs the Tenant.
An administrator grants the actions by name, such as deleting tickets, to the teams that may use them.
Ask which open tickets a client has with the 1st Line team.
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The HaloPSA tools are the same everywhere.
Only when you ask, and only what it has been granted: log a new ticket for a client; update a ticket's status, agent, team, priority, type or summary; add a private note to a ticket; delete a ticket; delete a note or action from a ticket; create a client; update or deactivate a client; create a site for a client; create an end user at a site; update or deactivate an end user; create an asset; update or deactivate an asset. 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.
Halo address, client ID and client secret. In Halo, an administrator opens Configuration, Integrations, Halo API, View Applications, New. Set Client Credentials, choose the agent and permissions, save, and copy the client ID and secret.
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