Investigate with Customer Detective

Customer Detective is Teml’s hosted investigation assistant. It gathers relevant telemetry, explains what it found, and links claims back to evidence in your project.

Start from the right place

Use Investigate for an organization or project question. Use Explain this person on a customer or the Detective action on an Issue when you already know the investigation anchor.

The current project, environment, and time range limit what Detective can retrieve.

Ask a bounded question

Good questions include a customer, symptom, journey, or time boundary:

• “Why did checkout failures increase after the last release?”
• “What happened to buyer@acme.example this morning?”
• “Are errors, latency, and logs pointing to the same service?”
• “Which customers are driving LLM spend this week, and why?”

Avoid prompts such as “Is everything okay?” They force a broad search and produce a less useful answer.

Read citations as part of the answer

Each important claim should cite an Issue, trace, log set, metric, replay, customer, account, or agent run. Open the citation and confirm:

• it belongs to the expected project and environment;
• its timestamp is inside the investigation window; and
• the evidence actually supports the conclusion.

Detective helps assemble evidence; it does not replace engineering judgment.

Ask follow-up questions

Keep follow-ups within the same investigation when they depend on earlier context. Start a new investigation when changing project, environment, customer, or incident.

When no answer is possible

A grounded “not enough evidence” result is preferable to a guess. Check whether the relevant signal was ingested, sampled, retained, and connected to identity. Use No data is appearing when the evidence itself is absent.