Member Memory
How Atlas remembers short support facts about each member, such as their platform or setup, what it never keeps, and how staff see and delete what is kept
Member memory lets Atlas remember short support facts about each member, such as the platform they run, the software and version they use, or how they like to be helped. Facts are learned automatically from the member's own messages when their ticket closes, and in their later tickets Atlas uses them to give steps that fit their setup instead of asking again. Staff see what is kept on the member's profile and can delete it. This page is for the server admin deciding whether to turn it on.
Member memory needs a Pro or Enterprise plan on the bot owner's account and the Atlas switch. The Remember members switch is on by default; turn it off to stop it. On other plans nothing new is learned or used, but staff can still see and delete what is already kept. Upgrade your plan
Turn it on or off
Member memory is on by default on every server whose bot owner has a Pro or Enterprise plan and where Atlas is on. Learning starts with the next ticket that closes; tickets closed before member memory was available, or while the switch was off, are never read.
Open the Atlas page
Go to AI assistant → Atlas. The Atlas switch at the top must be on for the jobs below it to show.
Find Remember members
In the Help your staff section, use the switch on the Remember members card. Its description reads: "Atlas learns short support facts about each member, such as their platform or setup, from tickets closed after you turn this on."
Save
Click Save changes in the bar at the bottom of the page. Off stops learning and use at once; facts already kept stay until they expire or staff delete them.
Turning it back on needs the bot owner's Pro or Enterprise plan. Dashboard staff can turn it on or off, and turning it off always works.
Settings
| Setting | Options | Default | What it does |
|---|---|---|---|
| AI assistant → Atlas → Remember members | On, Off | On | Learns facts from tickets as they close, and lets Atlas and AI Help drafts use them. Off stops both, and so does turning off the Atlas switch; facts already kept stay on member profiles until they expire or staff delete them. |
| Stop remembering / Resume remembering (on a member's profile) | Per member | Remembering | Stops learning about one member and stops using what is kept about them, until staff resume. |
What happens
-
A ticket closes. Atlas reads what the member who opened it wrote in the ticket. The first time a ticket closes, it also reads what they answered in the ticket form that opened it (application forms are not read). Each answer is read together with its question, and an answer to a question that asks for a password, PIN, token or another secret (in the question, its description or its placeholder) is left out. Messages from staff, from Atlas and from other people are only context, and so are the form's questions: a fact always comes from the member's own message or form answer, about themselves. A ticket where the member's messages and form answers together say almost nothing (only "hi" and "thanks", for example) is skipped.
-
Atlas keeps short facts on fixed topics. Each fact is one short sentence, in the language the member wrote in (the language of the form's questions when they only filled in the form), on one of eight topics, worded so that it makes sense without the ticket (it names the product or device it is about). Anything that fits none of the topics is not kept.
Topic on the profile What it covers Example Forgotten after Platform Operating system, host, device or game platform Runs the server on Ubuntu 22.04 180 days Software Frameworks, plugins, game modes or tools Uses the ESX framework 180 days Version The version of something they use Runs FXServer build 6683 180 days Hardware The hardware they use 180 days Setup How their setup is configured Has OneSync enabled 180 days Preference How they asked to be helped every time, such as a language or level of detail Prefers answers in English 180 days Problem A problem with their own setup or account that they still had when the ticket closed 30 days Fix A fix the member said worked for them Login loop fixed by clearing the launcher cache 30 days -
The newest statement wins. When the member later says something that changes a fact (a newer version, a switch to another framework), the new statement replaces the old fact. Saying the same thing again keeps the fact and restarts its clock.
-
Facts expire. A fact is forgotten 180 days after the member last mentioned it (30 days for Problem and Fix). Each member keeps at most 20 facts; when a new one would go over, the oldest Problem and Fix facts make room first, then the oldest of the rest.
-
Atlas uses the facts in later tickets. See How Atlas uses memory.
Members are never told that anything was remembered, and nothing is posted in the ticket when facts are learned.
What is never kept
Every fact is checked before it is saved, and a fact that fails the check is dropped:
- Contact and identity details: email addresses, phone numbers, IP addresses, US Social Security numbers and Discord mentions of people, roles or channels.
- Secrets and payment details: passwords, PINs, one-time codes, recovery codes, tokens and API keys, licence keys and card numbers.
- Claims of rank or entitlement: being an owner, admin, moderator, staff or VIP, or being owed or promised a refund, compensation, free time or special treatment. A member saying "I'm an admin" or "my refund was approved" never becomes something Atlas repeats.
Atlas is also told not to keep:
- real names, home or business addresses, contact handles and sensitive personal traits (health, religion, politics and the like);
- anything staff or another person said, and what the member reports about someone else;
- guesses, questions, plans, a switch or install the member has not finished, and anything it would have to infer;
- a preference the member did not ask for. The language a member writes in is not one, and neither is a request for that one ticket, such as a person instead of Atlas, a call or a guide;
- a statement that says nothing specific, such as that something does not work, without the product, the error or what goes wrong;
- order and other reference numbers, and the details of an order, such as a late delivery or how long a licence runs. That the member uses or owns a product is kept;
- what was only true at that moment, such as which apps were open or what they had just restarted;
- that a product or the service was down, updating or under maintenance;
- a problem that was solved in the same ticket (it keeps the fix instead).
The check for claims of rank or entitlement is strict and works on English words. A harmless fact that contains one of those words, such as "staff" or "approved", is dropped too.
How Atlas uses memory
Facts are used only for the member they are about, in the server where they were learned:
- Answers in tickets and ModMail. When a fact bears on the question, Atlas picks the steps or the variant that fits the member's setup and states the assumption lightly so the member can correct it, for example "Since you're on QBCore, ...". It does not say that it remembered anything or list what it knows. What the member says in the current ticket always comes first.
- AI Help drafts. Drafts see the member's facts, plus the values staff filled in on the member's profile fields. Drafts are for staff; a draft still never quotes or lists the details to the member.
- Not in the ticket summary. The ticket summary is saved on the ticket, so it never uses memory or profile fields: a fact you delete never lives on in a summary.
Facts never change what Atlas says about your product. Every step, price, limit and policy still comes from your knowledge base: when a fact disagrees with your content, Atlas gives your content's answer. Facts never prove a role, plan or purchase, so they never unlock anything you keep for certain roles.
Memory is not used in answers in public help channels or in Test Atlas. Nothing is learned from, or used in, tickets from members on Keep Atlas away from or tickets opened from a panel button that turns Atlas off.
Seeing and deleting what is kept
Open the member's profile
Open one of their tickets in Tickets and select Member profile under its heading.
Find the Memory section
Memory lists each fact with its topic, when it was last confirmed (Confirmed and a time), and the ticket it came from (Ticket # and its number, linked). A fact within 14 days of being forgotten also shows Forgotten and when. Before anything is learned it says Nothing learned yet.
Delete, forget or stop
- The bin button next to a fact deletes it, after Delete fact in the confirmation. It can be learned again if the member says it in a later ticket.
- Forget everything deletes every fact about the member. This cannot be undone.
- Stop remembering keeps the facts on the profile but stops using them and stops learning anything new about this member. Resume remembering undoes it.
Bot owners and dashboard staff with access to the server can see the section and use all three actions, on any plan and with Remember members off. Nobody can type, edit or add a fact by hand: memory only changes when the member says something in a ticket, when a fact expires, or when staff delete it.
Members cannot see or manage their memory in Discord or anywhere else. A member who wants to know what is kept about them, have it removed, or stop it being used should ask your staff, who can do all three on the profile.
Tokens
Learning uses the bot owner's AI tokens: one small AI request for each closed ticket in which the member wrote enough to read. It is counted under Atlas AI on AI usage and billed like every other Atlas response (AI model and tokens). Using facts in answers and drafts adds no extra requests.
When the owner's tokens are used up, closed tickets are not read, and they are not read later either when tokens come back.
While AI usage on the Atlas page is set to Essentials only, learning is paused in the same way: no new facts are learned, and tickets that closed meanwhile are not read later. Facts already kept are still used in answers and drafts. The Remember members switch stays as it is, and learning starts again when the bot owner chooses Default.
Retention
Facts follow your ticket data retention. When a ticket's saved data is deleted, because of Keep closed tickets for in General → Privacy and data or because the bot owner purged the ticket, every fact that came only from that ticket is removed with it. A short retention time therefore removes facts before their 180 days: with Delete right after closing, facts learned from a ticket are removed with the ticket's data.
If the bot owner's plan drops below Pro, memory stops learning and stops being used. Facts already kept stay viewable and deletable and are forgotten on schedule.
Limits and gotchas
- At most 20 facts per member, each up to 200 characters.
- Memory belongs to one bot and one server. A member's facts in one server are never used in another.
- Only the member who opened the ticket is remembered. Other people added to the ticket are not.
- Learning happens when a ticket closes, not while it is open. A reopened ticket that closes again is read only for what was written since the last close.
- Facts are what the member said, so they can be out of date. Atlas treats them as a hint and follows what the member says now.
Troubleshooting
| Symptom | Cause | Fix |
|---|---|---|
| No Remember members card on the Atlas page | The Atlas switch is off, so the jobs are hidden | Turn on Atlas at the top of AI assistant → Atlas |
| Turning it on fails with a plan error | The bot owner's plan is below Pro | Upgrade the owner's plan |
| The profile says Memory is off for this server. | Remember members or the Atlas switch is off | Follow Turn it on in the AI assistant settings., make sure Atlas is on, and save |
| Nothing learned yet after several tickets | The tickets closed before memory was turned on, the member wrote too little, nothing they said fits a topic, or every fact was dropped by the never-kept check | Wait for the member's next ticket to close. Nothing can be added by hand |
| A fact that looks harmless was not kept | It contained a word the rank and entitlement check refuses, such as "staff" or "approved", or something that reads like a phone number or IP address | Nothing to fix: the check prefers dropping a harmless fact to keeping a risky one |
| Nothing is learned for one member | Staff chose Stop remembering, the member is on Keep Atlas away from, or their tickets come from a panel button that turns Atlas off | Choose Resume remembering on their profile, or change the list or panel button |
| The profile says learning needs the bot owner's Pro or Enterprise plan | The owner's plan is below Pro | Upgrade the owner's plan. Existing facts can still be deleted |
| Learning stopped for every member | The owner's AI tokens are used up | Check AI usage; tickets that closed meanwhile are not read later |
| Learning stopped for every member, and the Remember members card says Paused while AI usage is set to Essentials only | The bot owner set AI usage to Essentials only | The bot owner chooses Default on AI assistant → Atlas → AI usage and saves |
Common questions
Can members see what TicketCord remembers about them? No. Members never see their memory, and Atlas does not tell them what it knows. A member who wants it shown, removed, or no longer used asks your staff, who can see it on the member's profile, delete it, and stop remembering that member.
Can staff add or correct a fact? No. Facts are only learned from the member's own messages in their tickets. Staff can delete a fact; if the member states the right detail in a later ticket, the newer statement replaces the old one.
Does member memory store passwords or personal details? No. Emails, phone numbers, IP addresses, passwords, codes, keys, card numbers and claims of rank or entitlement are checked for and never saved. See What is never kept.
Can a member get special treatment by claiming to be an admin or by saying a refund was promised? No. Claims of rank or entitlement are never saved, and facts never prove a role, plan or purchase, so they never unlock content you keep for certain roles.
How long are facts kept? 180 days after the member last mentioned them, or 30 days for problems and fixes, and never longer than the ticket data they came from under Keep closed tickets for. Each member keeps at most 20.
Does member memory cost extra tokens? Learning uses one small AI request per closed ticket in which the member wrote enough to read, from the bot owner's tokens. Using the facts in answers adds nothing.
What happens to memory if I turn it off or downgrade? Nothing new is learned or used. Facts already kept stay on member profiles, where staff can still delete them, and they are forgotten on schedule.
Does memory work in ModMail? Yes. Facts are learned when a ModMail ticket closes, from what the member wrote, and Atlas uses them when it answers the member's ModMail messages.
Join our Discord server for support
Was this page helpful?
Last updated on