What it does

The timeline is the single control on a case form that agents spend most of their day reading. It merges activities, notes and posts into one chronological feed, with filtering, search, inline note entry and per-activity command actions. It's a Power Apps control rather than a Customer Service one, but the case form is where it gets pushed hardest.

Key facts

• Records shown per page defaults to 10 and can be raised to 50, with a Load more button beyond that.
• Three record categories: Activities, Notes and Posts. All three are on by default; each can be turned off independently.
• Quick entry at the top of the timeline is set to Notes by default and can be switched to Posts. One or the other, not both.
• Default sort is descending, newest first. Ascending is available but disorients agents used to email.
• The filter pane and search bar are configured on the control. Search covers title and description; the filter pane covers record type, activity type, status and date ranges.
• What you've missed, which surfaces new activity at the top, is on by default. Expand all records is off by default.
• Microsoft warns that enabling more than 10 activity types hurts performance, and the designer shows a warning past that point. Timeline is documented as failing outright beyond roughly 15 linked tables.
• Card forms control what each entry shows: Header supports up to 6 columns with the first 2 rendered on the timeline, Details up to 4 with the first 3 rendered. ColorStrip and Footer sections are not shown on the timeline itself.
• Activity sort date can be Last Updated (default), Date Created, Due Date, or a custom Sort date column — but a custom sort date has to be populated yourself via flow, business rule or script.
• Activity rollup type (Extended, Related or None) applies to Account and Contact tables only, not to Case.
• Custom tables set to type Activity appear in the timeline, but they render with the default activity icon; a custom icon is ignored.
• Command actions on cards — pin/unpin, assign, close, delete, add to queue — are limited to 5 per activity type and are documented as preview.
• The modern timeline control experience and Copilot timeline highlights are both preview, enabled at app or form level under Settings > Upcoming.
• Dashboard timelines only show records related to the current user, and notes aren't available there.

When to use / skip

There's no skipping it — the timeline is on the case form and agents will use it whether you configure it or not. The question is how much configuration it warrants. Default settings are fine for a small activity footprint. Configuration becomes worthwhile the moment a client has custom activity types, a heavy email volume, or agents complaining they can't find anything: at that point card forms and the filter pane are where you get the biggest improvement per hour spent. Skip the preview modern control on a project going live imminently.

Configuration decisions

• Which activity types appear, kept to 10 or fewer. This is the decision that determines whether the case form feels fast.
• Notes or Posts for quick entry, and whether user posts are allowed at all — posts are a different collaboration model and clients rarely want both.
• Page size: 10 keeps load light, 50 saves agents clicking. Pick by how long the client's cases actually run.
• Card form design per activity type, given only the first two Header and first three Details columns render on the card.
• Sort basis: last updated versus created versus a custom sort date, and if custom, who populates it.
• Which command actions to expose, remembering the limit of 5 and their preview status.
• Whether to take the modern timeline control and Copilot highlights in preview, or wait.

Gotchas

• Timeline configuration lives on the control on a specific form. Two case forms means two timelines, and they drift apart silently — usually discovered when a client reports the timeline "changed" after being given a different security role.
• Adding every activity type because it's easy is the most common cause of slow case forms in Customer Service. The performance warning is real, not decorative.
• Card forms are separate forms in their own right. Editing the main form's fields does nothing to what the card displays.
• Custom activity tables show a generic icon no matter what you set on the table, so a client expecting branded icons will be disappointed.
• Notes and posts don't behave the same on rollup or on dashboards, and rollup type only applies to Account and Contact, so a case timeline won't pick up related-record activity the way people assume.
• Rich text notes have their own configuration path via a web resource, and known quirks around specific characters and image formats — WebP images don't render, so tell agents to paste PNG or JPEG.
• Attachment size is governed by system settings on the Email tab, not by the timeline, which is where people go looking first.

Consultant notes

• Audit the activity type list before go-live and cut it. It's the single highest-value tidy-up on a case form.
• Design the card form with a real case in front of you — two header columns is less room than it sounds, and getting subject plus direction onto the card is worth the effort.
• If the client has more than one case form, put timeline configuration parity on the test script explicitly.
• Demo the filter pane to agents during training. Most never discover it and then complain the timeline is unusable on long cases.
• Hold off on the preview modern control unless the client has a reason to want it, and be clear which of the timeline features you're showing are preview when you demo Copilot highlights.

---

Worth another look when the modern timeline control and command actions reach general availability.