Check supporting evidence
Identify missing evidence and prepare a complete packet for the returns team.

Retail & commerce / Customer service / Solution blueprint
Prepare a return review with the supporting records attached.
Business problem & expected outcomes
Return requests arrive without the order references or evidence needed for review.
Identify missing evidence and prepare a complete packet for the returns team.
How to measure the improvementEvidence completeness; repeated evidence requests.
Order references, return policy, submitted evidence, and item details.
Interactive workflow diagram
Identify missing evidence and prepare a complete packet for the returns team.
Order references, return policy, submitted evidence, and item details.
Designed around the work
Give the agent the context and tools this process needs, with an explicit output and an accountable owner.
Identify missing evidence and prepare a complete packet for the returns team.
Bind only the operations this workflow needs. Keep credentials in ART and choose the permitted tools explicitly.
Retain source references and review state only where this implementation requires persistence.
Retain source references and review state only where this implementation requires persistence.
Package the checklist, instructions, and expected output as a reusable skill.
Authorized staff approve refunds or replacements; evidence collection does not authorize them.
ART product mapping
Agent Lab prepares the work described below. These are the capabilities that support this workflow.
Keep the supporting files accessible within the review’s project and environment.
Track the case, owner, source references, and review state as structured records.
Package the checklist, instructions, and expected output as a reusable skill.
The implementation, step by step
Order references, return policy, submitted evidence, and item details.
Agree the trigger or manual request, record identifiers, and the process owner.Identify missing evidence and prepare a complete packet for the returns team.
Define instructions, permitted tools, and the expected output. Keep missing information explicit.Authorized staff approve refunds or replacements; evidence collection does not authorize them.
Keep the pilot in preparation mode and use the team’s existing review process.Evidence completeness; repeated evidence requests.
Compare outputs with reviewed examples and test incomplete, conflicting, and unauthorized inputs.Before you build
A document inventory, resource access scopes, and a file-retention policy.
Typed fields, record identifiers, relationships, and a table-retention policy.
A process checklist, example inputs, and a reviewer-approved output format.
Also prepare an ART project and environment, the model configuration appropriate to your agent, an accountable process owner, and approved sample data.
Authority stays with your team
Authorized staff approve refunds or replacements; evidence collection does not authorize them.
Explore execution governanceMap the source material and responsible owners first. Where the selected components require system access, configure scoped APIs or tools. A document-based pilot can start with approved material already available in the workspace.
Keep source references with the prepared output and review representative results before expanding scope. If the implementation includes executable actions, define their required facts and authority first. Apply retention to any stored records, files, or memory used by the case.
Build evidence from your own work
Evidence completeness; repeated evidence requests.
Choose a bounded sample of completed cases, record the current process, and agree review criteria with the process owner.
Use approved sample data and read-only connections. Compare prepared outputs with reviewer expectations, including incomplete and conflicting inputs.
Enable a limited set of actions only after the team accepts the results. Check approvals, failures, and handoffs before increasing scope.
Make it your workflow
Start with return request. Connect your approved tools, configure the review boundary, and adapt the output to your team's process.
Open your ART workspace to configure this use case.
Discuss the setup with usIndustry & department library
3 use cases in Retail & commerce
Give support a complete view of an order that needs attention.
Prepare consistent catalogue updates with source evidence attached.
Help store teams find the current operating procedure.
Retail & commerce / Let’s explore the fit
Tell us where work slows down. We’ll discuss how ART could fit your process, your systems, and the decisions your team needs to own.