---
title: Memory | The company's knowledge, connected
description: Memory captures and connects what a company knows (docs, mail, tickets, meetings, decisions) so people and agents get grounded answers with sources.
canonical_url: https://www.synchronised.be/memory.html
last_updated: 2026-10-15
---

# Memory | The company's knowledge, connected

Human page: [memory.html](https://www.synchronised.be/memory.html).

Memory is the company's knowledge, connected. It captures documents, mail, tickets, meetings, and decisions, then answers people and agents with sources attached.

## What it holds
- **Documents**: policies, runbooks, SharePoint, and the pages the team already trusts
- **Mail and tickets**: the thread that led to a change, including the incident that forced it
- **Meetings and decisions**: what was agreed, who was there, and when it took effect

## What it can do
- Answer a question with the sources that support it, not a summary with no trail
- Show how two records connect: a ticket, a meeting, and the policy that changed
- Let people and agents ask the same knowledge, with the same citations

Answers stay inside the sources the company has allowed. Memory does not invent a missing decision.

## Setup
1. Choose the sources in scope: docs, mail, tickets, meetings, and decision logs.
2. Connect how they sit together, so a question can follow a thread instead of a single file.
3. Decide who may ask, including staff and the agents that need the same knowledge.
4. Write what Memory may cite, and what stays out.

See [integrations](https://www.synchronised.be/integrations.md) for the systems Memory can read.

Questions about a live ERP or CRM record, and the fix that follows, stay on [First Line](https://www.synchronised.be/first-line.md). Mail that should become a ticket or an ERP record stays on [Email Orchestration](https://www.synchronised.be/product.md).