When a person fails in your checkout, you get a complaint. When an agent fails there, a far better record gets written — just not on your servers.
Your own logs show a session that started and stopped. A timeout, an error code, a form that never submitted. They tell you something happened, not why.
The agent’s trace holds the why: what it read on the page, which field it tried, what came back, what it concluded, where it went next. That is a better diagnosis of your product than most usability studies produce. It sits in the infrastructure of whoever runs the agent.
So a new class of data now exists. It’s about you, it was generated by your failure, and you’re neither its owner nor its recipient. Nobody decided that. It’s what falls out when the one who observes the failure is also the one who leaves.
The old arrangement had a quiet symmetry. The person who hit the wall was your customer, so some account of the failure — however vague, “it wouldn’t let me pay” — arrived at your door. Imperfect, but it landed with you.
Now the observer and the recipient have separated. The party best placed to explain what broke has no relationship with you and no reason to send you anything.
Two things follow for whoever owns the product.
→ More thorough server-side telemetry won’t reconstruct these failures. The missing half was never on your side of the wire.
→ The agent’s operator can compare your failures against everyone else’s. You can’t.
None of this depends on how many agents are buying today. It depends on where the record of a failure gets written when the visitor is not a person, and who gets to read it.
A test for this week: pick one multi-step journey and write down where the failure record would live if the visitor were an agent. If the answer isn’t “here,” you’ve found the gap.