Activity & touchpoints
Every meaningful thing that happens to a record lands in its activity feed — automatically for system events, and via the "+ Log" affordance for manual ones.
A record without context is just a row in a table. Activity is what makes Corto a CRM: the full history of how your team has interacted with a Company, Person, or Opportunity — notes, tasks, emails, calls, meetings, stage changes — merged into one chronological feed.
Two ways activity gets into the feed
Automatically, on every meaningful write
Anything your team does that touches a record generates an activity event:
- Creating a record ("Created opportunity Acme Q4")
- Editing a tracked field ("Updated Acme: amount $30k → $45k")
- Moving a deal between stages ("Moved Acme to Proposal")
- Linking or unlinking related records
- Soft-deleting a record
These events fire from the server the moment the write happens, so the feed is always current — no separate "save to timeline" step.
Manually, via the "+ Log" menu
For touchpoints that don't have a system trigger — a phone call, a quick note about a meeting, a follow-up task — you log them yourself.
Every record's Recent activity card carries a + Log button in its title bar with three options:
- Note — a free-form note attached to this record
- Task — an actionable to-do, optionally with a due date and assignee
- Call — a phone call you just got off, with direction (in/out) and duration
All three show up in the activity feed the instant they're saved.
Where activity shows up
Two places, designed for different jobs:
| Surface | Job | Length |
|---|---|---|
| Recent activity card on the side panel | Quick scan: "what's happened to this record lately?" | 5 entries, newest first |
| Activity / Timeline tab on the detail page | Deep history: scroll back through everything | All entries, paginated |
The card and the detail page read from the same data, just at different limits. An entry you see on one will be on the other.
What lives in the feed
A single record's activity feed merges six sources server-side:
| Source | Examples |
|---|---|
activity_event | Stage changes, field edits, creation, deletion. |
| Notes attached to this record | "Pricing discussion", "Discovery call notes". |
| Tasks attached to this record | "Follow up by Friday", with check-off status. |
| Call logs attached to this record | "Outbound call: Pricing follow-up", with direction and duration. |
| Email threads (Companies / People only) | Gmail-synced threads where this record's primary email is a participant. |
| Calendar events (Companies / People only) | Google Calendar events where this record attended. |
The merge happens in a single backend request and returns a uniform projection, so the UI doesn't need to know which source each entry came from.