Skip to content

Cross-Channel Timeline

Follow the conversation, even when it changes channels.

An email starts the discussion. A message moves it forward. A call adds context. Timeline brings captured activity and the people involved into one view, so your reviewers can follow the work across channels.

Client email and WhatsApp, internal Slack and Teams reviews, a RingCentral call, and Google Drive file entries. Demo data only.
Comma Timeline connecting Maya Chen, Daniel Reed and Priya Shah across email, WhatsApp, Slack, Microsoft Teams, a RingCentral call and Google Drive files

Start with the people, not the app

When the same people move between email, messaging and calls, a separate search in each channel leaves your team doing the joining. Timeline puts captured conversations, calls, voicemail, site scans and archived files into a dated view, with the entities associated with each record.

Choose the people relevant to the matter. Narrow by period, platform or activity. Open a record to inspect its content without losing your place in the wider review.

  1. Find the people involved

    Use entity identities to follow a person across their associated channel records. Narrow further by choosing specific people in the Involved parties or Counterparty filters.
  2. See where the conversation moved

    Read platform labels and participant badges together. A WhatsApp conversation and a phone call can belong to the same review, even though they arrived through different connections.
  3. Inspect the underlying content

    Open a row in the detail drawer, then use the full record view when you need more context. The message preview shows recent messages from the thread.
  4. Carry the evidence into the matter

    Use the case workflow to organize relevant records with the people responsible for reviewing them. Timeline helps find the material; the case records the investigation's work.

Three questions to work through

Deal review: follow the discussion before the decision

Maya Chen, an adviser, is working with client Daniel Reed on private-placement due diligence. Internal reviewer Priya Shah checks the written terms. The question is not just whether an email exists. It is how the client discussion connects with the team’s review across channels.

  • Start with the email. Identify the request and the people involved.
  • Follow the WhatsApp discussion. Read the clarification in the context of that request.
  • Connect the internal review in Slack and Teams. Follow Maya’s handoff to Priya, the questions they raise, and the written follow-up. These are internal exchanges, not messages sent to the client.
  • Check the call and supporting file entry. See the recorded activity around the discussion and identify the due-diligence document in the archive catalog.
Read the messages in the detail drawer, then open the full thread for more context.
The Timeline detail drawer showing Daniel Reed and Maya Chen's three-message WhatsApp exchange about liquidity terms and the fee schedule

What the reviewer gains: a way to follow the same people across channels, then read the source material before drawing a conclusion. The order of activity is context, not proof of intent.

Healthcare: trace an administrative vendor discussion

Elena Brooks, an operations lead, is working with vendor contact Jordan Ellis on onboarding. Colleague Marcus Lane reviews the visitor process and staff training. The review follows the vendor discussion and the internal handoff from the initial request to supporting documentation.

Vendor email, Teams clarification and internal Slack review alongside call activity and file entries. Demo data shown.
Comma Timeline connecting Elena Brooks, Jordan Ellis and Marcus Lane across email, Slack, Microsoft Teams, a RingCentral call and Google Drive files
  • Find the original request in email. Establish which requirement the team needed to resolve.
  • Read the Teams clarification and check the call activity. Follow the discussion beyond the inbox.
  • Check the internal Slack review. See how Elena and Marcus carry the vendor’s requirements into their administrative review.
  • Find the supporting file entry. Review its metadata alongside the conversations that explain why it matters.

What the reviewer gains: a connected view of the administrative work, without treating every channel as a separate investigation. The example concerns business communications, not clinical records.

Government: follow a supplier clarification across channels

Nora Bennett, a procurement officer, is reviewing a municipal bid with supplier contact Samuel Ortiz. Internal reviewer Olivia Park compares the written clarification with the proposal. The question is how the supplier’s response reached the review team and which records support its evaluation.

Supplier communications and internal evaluation across email, Slack and Teams, with call activity and file entries. Demo data shown.
Comma Timeline connecting Nora Bennett, Samuel Ortiz and Olivia Park across email, Slack, Microsoft Teams, a RingCentral call and Google Drive files
  • Locate the procurement team’s email. Establish the clarification requested from the supplier.
  • Follow the Teams discussion and call activity. Examine the communications around the response.
  • Read the internal Slack handoff. Follow Nora and Olivia’s review questions without confusing them with the supplier’s own statements.
  • Locate the clarification register. Use the file entry and its metadata to identify material relevant to the review.

What the reviewer gains: a clearer route through communications relevant to a procurement question or records review. The responsible team still determines the scope and obligations of any response.

Read the timeline, then read the record

Timeline lists message threads alongside other activity. A conversation appears as a thread, not as a separate row for every message; its position reflects its latest message time. Open the thread to understand the sequence within the conversation.

Entity badges reflect the identities associated with the available records. They help organize the review; they do not establish that two people coordinated or that a particular event caused another. File associations follow the owning custodian rather than proving who received a document.

From a useful view to a working investigation

Timeline gives e-discovery a place to begin with the people and activity. Cases organize related evidence, ownership and decisions. Surveillance can surface the communication that starts the review.

About Timeline

Is this a case activity log?
No. Timeline brings captured communications and other supported activity into a cross-channel view. A case activity log records work on a particular case, such as its creation or assignment.
Does choosing a person search across their channels?
The entity filter uses the identities associated with captured records across supported sources. Selecting several entities includes activity associated with any of them; it does not mean every result is a direct exchange between those people. Narrow further by choosing specific people in the Involved parties or Counterparty filters. Results depend on identity associations, source coverage and your access.
Does the list show each individual message?
Message activity is grouped into thread rows, positioned by the thread's latest message time. Open a row to preview recent messages, then open the full thread for the wider conversation.
Are these real customer investigations?
No. The screenshots show the actual product populated with fictional demonstration records. They illustrate review workflows, not customer outcomes or findings of misconduct. The file examples show catalog entries and metadata; document downloads are not part of this demo.
What do we need to use Timeline?
Timeline is part of the expanded e-discovery workspace, enabled for the team. The records available to review depend on connected sources, capture settings, identity associations and permissions. We'll demonstrate the sources and workflow relevant to your organization.

Bring a conversation that did not stay in one channel.

We'll walk through the people, captured activity and underlying records with your review team.

Share this page

More