Skip to content
Adoptiv

Activities & Timeline

The account of what changed and what was worked on, assembled by reading the tables rather than by anyone remembering to write it up. A field change keeps both readings, the one before and the one after.

One record's day, assembled from the tables it already sits in

5 of 6 merged
Where each row comes from
  • changelogentity_change_logs · created_at
  • emailemails · sent_at
  • notenotes · updated_at
  • meetingmeeting_activities · start_time
  • commentcomments · updated_at
  • tasktasks · due_date
each with its own ordering, merged and re-sorted after the fact
The feed
Calls, voicemails and texts are not in this feed · they are the touchpoint history, from a different set of tables entirely
Each of these is its own query against its own table, with its own ordering, over-fetched and then merged and re-sorted into one column. Nothing here was typed into a timeline; every row is the by-product of doing the work.
0
sources merged into one record history
0
field names carrying a written label
0
values stored on every change

Product figures from the platform’s own defaults - not customer averages

The mechanism

How it works.

01

Composed, never typed

The record being created, fields being edited, two separate activity tables, notes, comments, mail and the deals it was attached to are read from where they already sit and interleaved by when they happened.

02

Both readings, and who

An edit stores the field's written label, what it said before, what it says now, the person and the moment. That is why an entry reads as a sentence instead of a diff nobody can interpret six months later.

03

Names are resolved before storing

A stage or source change is written with the names of the two stages, not their internal identifiers. Rename the stage afterwards and the entry from last quarter still reads exactly as it did on the day.

04

Nothing quietly disappears

A deleted note or comment leaves its entry standing, and a note reopened more than a minute after it was written leaves an edited entry beside the original, so the history does not silently rewrite itself.

Where it sits

Two moments in every record.

Every record passes through the same seven. Activities & Timeline is the lit ones, and everything either side of it is a different page in this category.

  1. 01
    Capture

    how it arrives, and from where

  2. 02
    Shape

    the fields and stages it carries

  3. 03
    Find

    getting back to the right ones

  4. 04
    Work

    what happens against it day to day

  5. 05
    Advance

    moving it towards a decision

  6. 06
    Protect

    who may see it, and staying clean

  7. 07
    Report

    what the floor is judged on

The specifics.

8 facts
Merges
Creation, field edits, two activity tables, notes, comments, deal links and mail
Each edit
Field label, previous value, new value, the person and the timestamp
Labels
Seventy-three fields carry written labels; anything else falls back to its name
Custom fields
Recorded one at a time, labelled from the field definition rather than as a blob
Rendering
Yes and no for booleans. Stage and source read as names; other references stay identifiers
Not the phone
Calls, voicemails and texts are the touchpoint history, on their own line
Views are remembered
Opening a lead stamps who and when against it, for a recently-viewed list rather than as an audit trail
Paging
Twenty-five entries at a time, a hundred as the ceiling

More in Leads & Sales CRM

11 capabilities

The system of record the phone writes to directly - no sync job.

Deals & Pipelines

Unlimited pipelines, each with its own stages, win probability, colour and temperature. Seven seeded, and every stage change writes itself onto the deal.

Lead Stages

Create the stages your floor argues about, colour them, order them and rate them hot, warm or cold, while six fixed categories keep the reporting stable.

Lead Sources

Ten sources seeded and sealed, your own added beside them, each with a colour and a live count, and one stamped across a whole import rather than per row.

Custom Fields

Eleven field types, all of them on the picker, with options, defaults and a section of their own, on leads, deals, products and vendors. No cap on how many.

Field Groups & Layouts

Sort the fields you add into named sections with their own colour, order and table visibility, then grant or withhold a whole section per permission profile.

Saved Views

Columns, sorts, filters and layout save together and hand to a CRM role, so a new starter opens the same board instead of rebuilding it every morning.

Advanced Filtering

Eighteen type-aware operators, a trigram search across seven columns, and a straight account of where a custom-field filter is resolved and what it costs.

Bulk Actions

Tick rows and reassign, export, delete or enrol them at once, filtered per record by permission, so a mixed selection returns a verdict per row.

Bulk Import

Upload, map, review. Headers auto-map against the full field catalogue, imports stream so memory stays bounded, and a failed row never stops the run.

Duplicate Detection

Matched on normalised email then phone, at the moment a record is written, so the duplicate is caught on the way in rather than found in a report later.

Goals & Leaderboards

Ten measures over six windows, with attainment read from won deals and logged work the moment you open the target rather than filed by hand or overnight.

Leads & Sales CRM

See activities & timeline on your own floor.

Thirty minutes, your numbers and your data. We will set activities & timeline up live and you can decide from the thing itself rather than from this page.

14-day trial · no card · migration included