Where the workflow shifted
As agents enter support, quoting, order, and content workflows, service pages need scope, exceptions, and visible human fallback.
Separate automatic actions, confirmation-required steps, customer-provided inputs, and non-promises so the service feels purchasable.
Tool names are not outcomes
The signal matters when it clarifies a real service task, deliverable, and acceptance rule, not when it only shows a demo.
Check permissions and failure
- Use this issue's authorization table to improve service-scope language and FAQ anchors in `ai-vertical-services`
- Keep the test narrow: one service scenario with clear inputs, deliverables, acceptance rules, and human review
What still needs proof
Over-promising automation attracts low-fit demand and increases delivery disputes. Keep the original source open so the announcement, the evidence, and this site's interpretation stay separate.