SarahThe agent said my refund was approved, but this order was outside the return window. Which answer is correct?
Get everyone working
from the same evidence
Connect what your agent did with the people who know whether it was right. neatlogs keeps production evidence, business judgment, team decisions, and engineering action together, from the first report to the verified fix.
Works where your team already does:
Context becomes evidence
Connect business contextwith production data.
A trace can show that the agent issued a refund. It can’t tell you whether that customer was entitled to one. neatlogs connects production runs with the feedback, policies, exceptions, and decisions that define what correct meant in that case.
“The agent said my refund was approved, but this order was outside the return window.”
Use neatlogs without
opening neatlogs.
Review an eval, answer an investigation question, acknowledge an alert, or reply to a thread from Slack. The question arrives with the output and evidence needed to answer it.
Reply in Slack. The same thread updates in neatlogs.The create_refund span failed with the following error:
PolicyViolation: refund attempted before return eligibility and support approval were confirmed.
Does the enterprise exception apply to this customer?
Policy check did not run before the tool call.
No. The exception requires support approval, and this run did not have it.
Agreed. I’ll add the approval check before the refund tool can run.
MatthewNo. The exception requires support approval, and this run did not have it.
Issue created — issue_refund — Refund RF-88244 for $240 issued on NL-10517 with return_eligible=false and vip=false
From feedback to a verified fix
The customer was promised a refund before eligibility was checked. Can someone look at this?
I found the matching production run and attached the reported outcome.
Someone notices
A customer, support lead, PM, or engineer says something went wrong, in the tool they’re already working in.
neatlogs finds the run
It connects the message to the runs it’s about, and raises it as an issue with severity and source attached.
The refund path continued after the policy lookup returned an exception.
@neatlogs this account is in the enterprise exception group. Did the run load that policy?
Good catch. I found a second policy lookup and added it to the evidence.
The investigation uses their context
The reported outcome, business rules, and team decisions become part of the diagnosis.
Require escalation before enterprise refunds
Prevent `create_refund` when the account policy requires a specialist review.
- Evidence
- 4 spans + report
- Acceptance
- 3 verification cases
The fix moves forward
The report goes to the owner as a ticket, or to your coding agent with the evidence intact.
Enterprise refund guard
Watching the same failure path in production.
The loop closes
The person who raised the problem can see what changed. neatlogs watches your agent to check whether the fix held.
Product questions and answers
The practical details about connecting team feedback, discussing evidence, and keeping decisions attached to production work.
Do reviewers need to understand traces?
No. Someone answering a question in Slack sees the output being judged and the evidence behind it, not a span tree. The people who know what correct means at your company are usually not the people who read traces.
No. Someone answering a question in Slack sees the output being judged and the evidence behind it, not a span tree. The people who know what correct means at your company are usually not the people who read traces.
Comment on the exact thingthat’s wrong.
Highlight the evidence. Leave a comment. Tag the person who knows. Keep the answer where the question began.
Sarah This promise is made before eligibility is checked.
On a span
Point to the prompt, tool argument, retrieval, or line of output that needs attention.
Comment stays attached“…sent to account ending in 4821.”
Chris Useful signal, but mask the last four digits from this rule.
On a detection
Decide whether the signal is useful, noisy, or scoped incorrectly.
Comment stays attachedRequire a policy outcome before issuing the refund.
Jon Add the enterprise exception before this ships.
On an investigation
Challenge the root cause, supply missing context, or review the recommended action.
Comment stays attachedMatthew The rubric should require eligibility before any promise.
On an eval
Discuss the verdict, the rubric, or why two reviewers disagreed.
Comment stays attached