Customer investigation

Understand the person.Follow the whole story.

Ask your agent what happened to a customer. It follows their journey, their recording and the technical evidence, then gives you a link to check.

Example: an agent session and its proofCustomer timelines / Account context / Proof links
  • Start with a person

    Identity and account context stay beside the activity your agent reads.

  • Connect the signals

    Events, replay, errors, traces and flag exposure, already joined to the same person.

  • Check the answer

    Open a read-only page that shows the evidence behind the claim.

01The customer timeline

Their journey should not end at the frontend.

A customer reports a failed payment. Your agent reads their timeline: the captured actions around it, with links into the recording and the backend evidence for the same person. You open the person page it gives you.

  • Anonymous and signed-in activity follow connected identity.
  • The customer, account and time window stay together.
  • Related errors, requests and recordings are linked from the story.
Explore the customer timeline

02Compare and follow

Who else was hit, and what do they share?

Ask your agent to find the people an Issue affected and compare them with customers who succeeded. It can save the group as a cohort for later work. Each result opens as a read-only page.

  • Find the people an Issue affected.
  • Compare them with customers who succeeded.
  • Save a group as a cohort to reuse.
Compare affected and successful customers

The workflow, connected

From “something went wrong” to a story you can check.

Your agent keeps the investigation anchored as it moves between people, product activity and technical detail.

  1. Find the person

    Ask about a customer, an account or an Issue. Name the project and the time window if they matter.

  2. Follow the moment

    Your agent reads their captured timeline and finds the replay, request or error around the problem.

  3. Open the proof

    The link shows the person’s story, read-only. Send it to a teammate in your workspace.

The capabilities behind it

More context for every customer question.

Individual journeys, business relationships and saved audiences give your agent several ways into the evidence.

Put it to work

Useful questions start here.

Why could this customer not pay?

Your agent finds the checkout moment, the recorded experience and the backend failure.

Explore this workflow

What happened across this account?

It brings the business relationship and the recorded account activity into one investigation.

Explore this workflow

What do these customers have in common?

It compares affected customers with successful ones and finds the recorded attributes that differ.

Explore this workflow

Your first useful workflow

Start with a journey you want to understand.

Connected context begins with the identity carried by the signals your application records.

  1. Choose your capture path

    Select the SDK or OpenTelemetry integration that fits your application.

    Read the guide
  2. Connect customer identity

    Associate the same person with the events and requests you want to follow.

    Read the guide
  3. Verify the first story

    Ask your agent to check the captured activity before you rely on it.

    Read the guide

A few useful answers

A few useful details.

Where can I begin?

Begin with a customer, an account, an Issue, a service or an agent run. The person appears when your captured signals carry identity.

How do people and accounts relate?

A person carries their individual story. Account context brings the business relationship and recorded account activity into the investigation.

How do I check what my agent tells me?

Ask for the link. A result about one person carries a link to a read-only page that shows their timeline. Each result also names the signals behind it and says where the evidence is partial.

Does everything need a customer ID?

No. You can investigate services, Issues and other technical signals on their own. The customer story connects the signals that carry recorded identity.

Can I check what my agent tells me?

Yes. Ask for the link. A result about one person carries a link to a read-only page with their timeline, and the result names the signals behind it.

Anectico / Private preview

Bring a customer question.Leave with connected context.

Connect your agent and ask your first customer question in Anectico private preview.