Activity management and the timeline

What it does

Activities are the record of every interaction with a customer — emails, phone calls, tasks, appointments — plus notes, which are not activities but sit alongside them. They hang off a customer record through the Regarding field and surface on that record's timeline and under My Work > Activities.

Key facts

The out-of-the-box types a seller works with in Sales are email, phone call, task and appointment, with notes on the timeline as a separate thing entirely.
Every activity type shares the activitypointer base table, which is why cross-type views, the Activities list and the timeline can show them together. Custom activity types are possible in Dataverse and inherit that behaviour.
Regarding is what associates the activity with a customer record. An activity with a blank Regarding belongs to nobody and shows up in the Activities list without context.
Rollup is the part people miss: an activity logged against a contact appears on the parent account's view of activities too. Log it against the account instead and it does not roll down to the contact.
My Work > Activities offers several presentations of the same data — a read-only grid, a calendar showing scheduled activities against deals, a focused view of the most relevant items, and a Kanban board.
The Kanban board exposes the states directly: Open, Scheduled, Completed, Canceled, and you can drag between them.
Filters on those views are by activity type and by due date window, which is the closest thing to out-of-the-box "my day" behaviour without building anything.
Mark Complete works on a single record from the form command bar or on a multi-select from a list, which is the fastest way for a seller to clear a backlog.
Activities can be created from the record's Related > Activities area, from the timeline plus button, or standalone from My Work — three routes that produce subtly different Regarding defaults.
Attachments go on emails through Attach File; notes take attachments through the paperclip on the timeline note control.

When to use / skip

Activities are not optional, but the amount of configuration around them very much is. Almost every project needs a decision on which types sellers actually use and what "done" means, and almost no project needs the elaborate activity taxonomy the client asks for in workshop two. Custom activity types in particular are a trap: they look tidy on a whiteboard and then need their own forms, views, security, timeline configuration and reporting, and sellers still log everything as a phone call.

The place to spend effort is the timeline configuration on the key forms — lead, contact, account, opportunity — because that is where sellers live. Getting the record types, the default filters and the collapse behaviour right on those four forms is worth more than any amount of activity modelling.

Configuration decisions

Which activity types are in scope for sellers, and whether any custom activity type genuinely earns its place over a phone call with a category field.
What appears on the timeline for each form, in what order, and what the default filter is when the form opens.
Whether appointments sync with Exchange through server-side synchronisation, since that dictates whether the calendar view reflects reality.
Who owns activities logged against a shared account — assignment and ownership rules matter once a team works the same customer.
Whether activities are expected against leads at all, given they do not follow the lead into the opportunity in the way people assume.
What sellers must complete before an opportunity can advance, if the client wants activity-based process gates rather than just a record of what happened.

Gotchas

Rollup only goes one way. Log against the account when the conversation was with a person and the contact record looks empty forever, which then makes relationship reporting look wrong.
Regarding is easy to leave blank, especially on activities created from My Work. Orphaned activities are the single most common cause of "the timeline is missing things".
Closed activities are effectively read-only in Dataverse. If a seller marks a call complete with the wrong notes, correcting it means reactivating the activity, which not every security role allows.
Deleting an account or contact cascades to its activities under the default relationship behaviour. Clients rarely realise their interaction history goes with the record until it has gone.
Timeline performance degrades on long-lived, heavily integrated records. Filters and the record types shown on the timeline control are the lever, not more hardware.
Emails and appointments created by server-side sync or by capture features land as activities like any other, so activity counts in reports include machine-generated items unless you filter them out.

Consultant notes

Ask the client what question they want to answer with activity data before you configure anything. "How many calls did the team make" and "what happened on this account" pull the design in different directions.
Demo the Kanban and calendar views. Most clients have never seen them and it heads off a request to build a custom activity dashboard.
Push back hard on custom activity types unless there is a reporting requirement that genuinely cannot be met with a category field on a phone call.
Check the timeline configuration on every form you touch as part of go-live, and check it again after a solution import — timeline settings are easy to overwrite.
Agree an activity hygiene expectation with the sales manager. Activity data is only as good as the team's habit of setting Regarding, and that is a management problem, not a configuration one.

Worth revisiting when timeline and activity capture change again — automatic capture keeps shifting what actually ends up on the record.