Separate reader traffic
Brands increasingly want customer agents to understand loyalty rules, returns, promotions, and internal systems in ways generic support bots cannot.
Customer-agent quality starts becoming a control-surface problem: what custom logic matters most for conversion and support costs.
Requests are not readers
The useful question is not whether traffic looks busy; it is which activity represents readers, monitoring, crawlers, retries, or system errors.
Check the logs first
- Start with five skills: order tracking, returns, loyalty benefits, discount logic, and next-best action
- Keep the test narrow: one priority product or checkout flow before expanding recommendation, authorization, payment, and support work
What still needs proof
Custom skills do not help if the underlying business logic is inconsistent or poorly documented. Keep the original source open so the announcement, the evidence, and this site's interpretation stay separate.