Missing points explained
Sarah Chen, support lead at Acme Ltd, had a customer asking why their points had not appeared. Memtro found the member by email and showed the purchase activity still pending, with the points it carried.
How many points does this customer have, and what can they claim?
LoyaltyLion connects Memtro to your loyalty programme. It reads members by email with points, tier, rewards claimed and segment, points activities, the points ledger and the rewards a member can claim now. It syncs new points activities into memory. When asked, and once an administrator has granted them by name, it can give or take points with a reason the member sees, claim or refund rewards, approve, decline or void activities, block a member, enable or disable rewards, and unsubscribe an email address. A claim may issue a voucher or gift card, and a refund cannot be undone.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right LoyaltyLion tool, reads what it needs, and answers with the source cited.
These tools change something in LoyaltyLion. 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, choose the kinds you want, and Memtro registers its address with LoyaltyLion for you. Each event can start a job, with the event as its input, and can be remembered where you choose. LoyaltyLion signs every delivery, and one whose signature does not check out is refused before it is read.
Events and webhooksOnce LoyaltyLion 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 points does jessica@example.com have?
Who earned points this week?
Which members are in the At Risk segment?
What rewards can jessica@example.com claim right now?
Give jessica@example.com 200 points for the late delivery.
Sarah Chen, support lead at Acme Ltd, had a customer asking why their points had not appeared. Memtro found the member by email and showed the purchase activity still pending, with the points it carried.
Dan Fletcher, retention manager at Northwind, asked Memtro to give a member 200 points for a late delivery. Memtro added the points with the reason he approved, which the member saw in their account, and the adjustment appeared in the points ledger.
The teams that lean on LoyaltyLion most, a question each of them asks, and what they connect beside it.
A record in LoyaltyLion 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 LoyaltyLion, open Manage → API keys and choose Create API key.
Grant read_customers, and read_orders for the points ledger. Add write_customers, write_configuration or write_unsubscribes only for the actions Memtro may take, then copy the key, which is shown once.
In Memtro, open Connections → LoyaltyLion and paste it into API key. The older token and secret are not accepted.
Ask your first question: who earned points this week?
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The LoyaltyLion tools are the same everywhere.
Only when you ask, and only what it has been granted: give a member points, with a reason the member can see; take points from a member, with a reason the member can see; claim a reward for a member, spending their points; refund a claimed reward, returning the points; approve, decline or void a points activity; track an activity so its rule awards a member points; set a member's birthday, or block or unblock them; enable a reward in the programme; disable a reward in the programme; unsubscribe an email address from programme emails. 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 LoyaltyLion records into memory as entities.
API key. In LoyaltyLion, open Manage → API keys and choose Create API key.
Yes. Turn events on in the connection's Events tab on the Connections page, choose the kinds you want, and Memtro registers its address with LoyaltyLion for you. 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