Policies, runbooks, SharePoint
The pages the team already trusts: VPN policy, posting guides, and the handbook that was current when the decision was made.
Memory
The company's knowledge, connected
Memory captures documents, mail, tickets, meetings, and decisions, then answers people and agents with the sources attached.
What it holds
Everything the company already knows, in one place you can ask
The answer to “why did we change this?” is usually split across a policy, a ticket, a meeting, and a mail thread. Memory connects those records so the reply can cite them.
The thread that forced the change
INC-1988, the supplier mail, the case notes. Memory keeps the incident next to the document it changed, instead of leaving both in separate tools.
What was agreed, and when
Teams meetings, decision logs, and the date a rule took effect. People and agents ask the same knowledge, and get the same sources.
In the chat
A question, then the sources that support it
Memory is for the knowledge the company already has. You choose which sources it may use. It does not invent a missing decision.
Why did the VPN policy change in March?
INC-1988 opened after a remote access failure. Security required MFA. The 12 March meeting approved it, and SharePoint holds the policy that took effect that week.
What did we agree with this supplier?
The signed rate is in the contract. The last quote sits in mail. Memory cites both, so purchasing can see whether the new price matches what was agreed.
Who decided we would stop that process?
The decision log names the owner and the date. The meeting notes record who was in the room. Memory returns those two sources instead of a rumour from last year.
Has this exception happened before?
Related tickets and the runbook that closed them. Memory shows the earlier case and the page the team used, so the next person does not start from zero.
- Ticket INC-1988
- Meeting Teams 12 Mar
- Doc VPN policy
Colleague
Why did we change the VPN policy in March?
Memory
After INC-1988, security required MFA on remote access. The 12 March meeting approved it, and the SharePoint VPN policy took effect that week.
Open INC-1988
Show the policy
How we set Memory up
1. The sources in scope
Documents, mail, tickets, meetings, and decision logs. Memory learns where those records live for your company, including SharePoint, Microsoft 365, and the helpdesk you already run.
2. How they connect
A ticket that changed a policy, a meeting that approved it, the mail that followed. We connect those threads so a question can follow them instead of stopping at one file.
3. Who may ask
Staff, and the agents that need the same knowledge. You decide who can see which sources. See integrations.
4. What it may cite
You write the boundary. Outdated pages can be left out. Every answer shows the sources it used, so the team can audit a reply.
Questions about a live ERP or CRM record, and the fix that follows, stay on First Line. Mail that should become a ticket or an ERP record stays on Email Orchestration.