What a feed is
A timeline that attaches to the record, not to the person. The memory of the system.
The definition
Every contact and every engagement has a feed: a timeline of everything that happened — notes, voice notes, uploaded documents, stage changes.
The important part is that a feed attaches to the record, not to whoever wrote it. When a colleague leaves, the history of their accounts stays exactly where it was. That difference is the whole reason feeds exist.
What lands in a feed
- Typed notes
- Decisions — a note deliberately marked as one
- Voice notes
- Uploaded documents
- A meeting card
- Pipeline stage changes
- Tasks created or closed
- An indicator threshold breach
Three scopes, three different behaviours
An engagement's feed belongs to that engagement. An organisation's feed carries its own items and rolls up its engagements' items too — so a client's page is the whole story of that client.
A person's feed stays separate: an item on a person has exactly one home and never leaks into the feed of an organisation where that person holds a seat. Your note about a named individual does not merge into the note about the company.
One item can appear in several feeds at once (cross-posting), but it is still one item: edit it once, and deleting it removes it everywhere.
An edit is never invisible
Change the body of a post and the edit is timestamped. A post that has been edited is distinguishable from an original.
That is deliberate: a feed is the firm's internal record, and a record that can be rewritten without a mark is not a record.
Read this next
- Contacts & engagementsNotes, replies and decisionsThe three things you write into a feed, and how they differ in practice.
- Work, tasks & PulseThe Work streamEvery feed and every task in one stream. The page you open in the morning.
- Contacts & engagementsVoice notesA minute of talking instead of five of typing — and what happens if transcription fails.
Still stuck?
If the answer wasn't here, write to us. It is a real inbox and it gets answered.