Creating memories
Add a memory by hand, or ask Uniportal's AI to remember something for you.
There are two ways a memory gets created: you write one directly on the Memories page, or you tell the AI to remember something mid-conversation and it captures the memory for you.
Creating a shared memory
Open Memories and select Add shared memory
Go to Memories > Shared and select Add shared memory.
Set the scope
Pick All companies, Company, Device, or End user. Choosing Company, Device, or End user opens a search field, type to find the specific company, machine, or person this memory is about.
Write the title and the memory
The title is the short summary the AI scans first, make it specific enough to act as a label on its own: "Dunder Mifflin Scranton's change window is Saturday 8 PM to midnight," not "change window." The memory field is where the actual instruction goes. Uniportal's own guidance for this field: write it as an instruction to the AI, what is true, and what to do about it. A fact with no instruction attached ("Kevin's desktop runs a nightly job") is weaker than one that tells the AI what that means for its behavior ("...so never schedule a reboot or patch window before 6 AM").
Choose when the AI should use it
Always applied sends the memory to the AI on every ticket within its scope, a standing rule the AI has in context before it starts work. When relevant holds it as background knowledge the AI only fetches if the ticket or task it's working on actually calls for it. Default to When relevant. Reach for Always applied for anything the AI needs to obey even when nothing on the ticket would obviously trigger a search for it: an approval requirement, a change freeze, a VIP SLA.
Set an expiration, if it's temporary
Optional. If the fact won't be true indefinitely, leave an end date instead of leaving it to go stale. See Expiring memories.
Save it
Select Add memory.
Why the choice matters
Always applied costs a little context on every single ticket in scope, whether or not that ticket needed it. When relevant costs nothing until a ticket actually matches, but depends on the AI recognizing that it should go looking. That trade-off is why the two options exist instead of the AI just deciding: a VIP acknowledgment SLA has to fire even on a ticket that gives no obvious sign it's urgent, so it needs to be always applied. A device's firmware quirk only matters on tickets that are already about that device, so it's safe to leave as when relevant and let the AI find it there.
Creating a private memory
Open Memories and select Add my memory
Go to Memories > Mine and select Add my memory.
Write the title and the memory
Same fields as a shared memory, a title and the instruction itself, just no scope to set. A private memory applies to you, not to a company, device, or end user, so there's nothing to attach it to.
Save it
Select Add memory.
Asking the AI to remember something
Tell the AI to remember something mid-chat, the same way you'd tell a coworker, and it creates the memory for you instead of you filling out the form. For example: "Remember that Dunder Mifflin Scranton's guest wifi password gets reset every quarter."
Check what it captured
When the AI creates a memory on its own, it's also deciding the scope, the shared-vs-private split, and how the memory gets used. That's a guess based on the conversation, not something you confirmed. Open the memory it created on the Memories page and fix anything it guessed wrong.
Editing, archiving, and deleting
Each memory has Edit, Archive, and Delete. Edit changes the fields directly. Archive takes it out of use without deleting it, an archived memory can be restored later, and it's the right move for something that's no longer true but worth keeping a record of. Delete removes it permanently.
Editing or archiving a shared memory changes what every technician's AI sees within its scope, immediately. Treat that edit with the same care you'd give a change to a firm-wide Skill.