Intelligence
Customer memory (DPMem)
Customer memory is where Frontline PSA keeps lasting knowledge about a customer: how their environment is set up, who to call, what a particular contact prefers, what fixed the problem last time. It is stored in DPMem, a separate memory service, as two kinds of entry:
- Notes are short pieces of free text filed under a category.
- Facts are single name-and-value pairs, such as a contact's preferred channel. Recording a fact replaces the previous value for the same name.
AI triage reads this memory when it assesses a ticket, and it can suggest saving something new to memory once the ticket teaches you something worth keeping.
Where memory appears
| Place | What you see |
|---|---|
| A company's Memory tab | Everything held for the company, grouped by category, plus its facts and a Write log |
| A contact's Memory tab | Notes and facts about that person, plus the write log |
| A ticket | A card titled What we know about the ticket's contact, showing their facts and first three notes. Click Show all to see the rest. The card only appears when the ticket has a contact. |
| Intelligence → Memory | Connection status, search across memory, the knowledge base sync, the company mapping table and the full write log |
Each note shows where it is filed, who added it and when. Use the reload button on the panel to read from DPMem again.
Note: A MOCK DPMEM tag means no memory service is configured and you are looking at a local stand-in with demo data. DPMEM OFF means memory is switched off. In both cases nothing is read from or saved to a real memory service.
Shared and client memory
Memory is split into two areas:
- Client memory belongs to one customer. Each company is mapped to its own area, and only that customer's tickets, company and contacts read from it.
- Shared memory is general knowledge that applies to every customer, such as your global knowledge base articles.
When you open a company or contact, Frontline PSA reads that customer's client memory together with shared memory. When you save, it writes to the client memory only. Customer knowledge is never filed in shared memory.
Add a note
You need permission to write to memory, and the company must be mapped (see below). If either is missing, the Note and Fact buttons do not appear.
- Open the Memory tab on a company or contact, or the memory card on a ticket.
- Click Note.
- On a company, choose the category and the sub-area within it. The categories are Profile, Environment, Operations, Security, Learnings and Docs. Contact notes are filed under the contact automatically.
- Type the note. It must be at least 8 characters. Write something that will still be true and useful next month.
- Click Save to DPMem.
The line under the text box shows exactly where the note will go. A note added from a ticket is linked to that ticket. Every save is checked for duplicates first: if memory already holds near-identical content, nothing new is written and you are told so. The Last save line shows the result.
Record a fact
- Click Fact.
- Enter the fact name. The field suggests
prefers_channel,primary_device,works_hours,is_vip,role,recurring_issueandneeds, and you can type your own. - Enter the value, for example
phone. - Click Record.
The new value replaces the previous one for that name. The history is kept in DPMem. Facts appear as chips at the top of the memory panel.
Limit: You cannot edit or delete an existing note from Frontline PSA. To correct a fact, record it again with the new value.
Search memory
- Go to Intelligence → Memory.
- Under Search memory, type at least two characters describing what you are looking for.
- Choose the scope: Shared only, or a mapped company to search that customer's memory together with shared memory.
- Click Search or press Enter.
Results list matching notes with where each is filed, followed by matching facts.
Map a company to its memory
A company must be mapped to a memory area, called a namespace, before anything can be saved for it. You need memory administration rights.
- Go to Intelligence → Memory and find the Company → namespace table.
- In the Namespace column, enter a value in the form
client:slug, using lowercase letters, digits, hyphens or underscores (for exampleclient:acme). - Click Save on that row.
To remove a mapping, clear the field and click Save.
Things to know:
- Child companies inherit. Leave a child company's namespace blank and it uses its parent's. The memory panel then shows the namespace with "via" and the parent's name.
- Unmapped companies are read-only. They get shared knowledge only, the Note and Fact buttons are hidden, and nothing is ever written for them.
- Mapping is not enough on its own. The memory service must also grant Frontline PSA access to that namespace. A DPMem administrator does this. Until then you will see the "no grant" message below.
Sync knowledge base
Sync knowledge base now, on Intelligence → Memory, copies every published knowledge base article into memory so AI triage and other tools that read DPMem can use it. Global articles go to shared memory. Customer-specific articles go to that customer's client memory. You can run it as often as you like without creating duplicates, and articles that are no longer published are removed from memory.
After a run, a table shows each scope with its article count and a result of synced, skipped or failed. Articles for a company that is not mapped are skipped. The sync runs only when you click the button and needs memory administration rights.
Messages you may see
Problems are shown on the panel rather than hidden, so you know when memory is incomplete.
| Message | What it means | What to do |
|---|---|---|
| "This company is not mapped to a DPMem namespace yet (Intelligence → Memory). Only shared knowledge is available." | The company and its parents have no mapping | Ask an administrator to map it |
| "... is not mapped to a DPMem namespace, so nothing was written" | You tried to save for an unmapped company | Map the company, then save again |
"The PSA's DPMem identity has no grant for this namespace — ask a DPMem admin to grant it." (forbidden) | The memory service has not given Frontline PSA access to this customer's area | Ask your DPMem administrator for the grant |
"DPMem could not be reached ..." (unavailable) | Network problem or the memory service is down. After repeated failures Frontline PSA pauses briefly before retrying. | Wait, then use reload |
"DPMem did not answer in time." (timeout) | The memory service was too slow | Use reload to try again |
"DPMem is not configured ..." (not_configured) | No memory service is set up | See Deployment |
| "DPMem already holds near-identical content; nothing new was written." | Duplicate note | Nothing; the knowledge is already there |
Failed and duplicate saves also appear in the Write log, with who tried and from which ticket.
Who can do what
With the default roles:
- View memory: administrators, managers, dispatchers, technicians, sales and read-only users. Finance users do not see memory or the Intelligence module.
- Add notes and facts: administrators, managers and technicians.
- Map companies and sync the knowledge base: administrators only.
Roles are managed under Administration.