Hire Zara.
Returns handled. Exceptions surfaced.

Zara is UnleashX’s Returns & Refunds Specialist. Zara autonomously matches purchases, checks return eligibility, answers policy questions, creates authorized return requests and tracks return and refund status separately. Routine actions run within your configured knowledge, permissions and business rules; exceptions and decisions outside that authority go to your team with context.

Autonomous execution within your rules. Human handoff when required, not at every step.

ZARA AT WORK

From return request to a clear next step.

Illustrative workflow

The conversation

CUSTOMER REQUEST

The item I received is the wrong size. Can I return it?

ZARA

Let’s check the purchase and the return rules that apply to this item.

Conversation → structured context

Zara

Read the matched purchase record

Autonomous · within your rules

Commerce + returns

People join only when needed

Return request

EXAMPLE RECORD · NOT LIVE DATA

Purchase · matched
Reason · size mismatch
Eligibility · policy checked

SYSTEM ACTION

Read the matched purchase record

Awaiting workflow steps

Step 1 of 4 · Match

Example sequence only. Channels, integrations and permitted actions are configured and validated for your deployment.

SELF-SERVICE SETUP

You configure Zara.
Zara gets to work.

Sign up and make this pre-built role your own. Prepare your approved knowledge, business rules, system access and escalation owner before launch.

ILLUSTRATIVE SETUP · NOT A LIVE PRODUCT SCREEN

Define the job

YOUR ROLE BRIEF

Starts with: A return, refund or exchange enquiry
Works toward: A verified request or an assigned policy exception
First responsibility: Locate the purchase
Human authority: Policy waivers, disputed refunds and unapproved reimbursements

A defined scope for Zara to work within.

Create your account, then configure your employee in UnleashX. This preview does not save settings or connect systems.

THE JOB TO BE DONE

A clear responsibility.
A verifiable outcome.

Hire Zara to own the routine work, not just recommend the next step. Zara matches purchases, checks return eligibility, answers policy questions, creates authorized return requests and tracks return and refund status separately, without step-by-step supervision. Your team sets the rules and handles policy waivers, disputed refunds and unapproved reimbursements.

Work Zara executes autonomously

Locate the purchase
Understand the request
Explain the policy
Coordinate the next action
Track the recorded outcome

Your team handles the exceptions

Policy waivers, disputed refunds and unapproved reimbursements stay with authorized people in the scope described here.

Use approved knowledge instead of guessing an answer.
Separate customer intent from a confirmed system result.
Assign unresolved work to a named team.
Test policy changes before expanding responsibility.

Define Zara’s knowledge, system permissions and business rules before launch. Zara executes within that scope autonomously. The examples illustrate the workflow; they are not measured customer results.

FROM REQUEST TO RECORDED RESULT

How Zara executes the work.

Starting with a return, refund or exchange enquiry, Zara runs these steps autonomously within your configured permissions and business rules. Routine work does not wait for manual approval. Exceptions and unverified outcomes follow the agreed recovery or human-handoff path.

01
Locate the purchase
Match the customer and order using approved checks.
Information needed
Order reference, item and fulfilment state.
What moves forward
A valid purchase context.
02
Understand the request
Clarify the item, reason and whether the customer wants a return, exchange or refund.
Information needed
Customer explanation and item details.
What moves forward
A correctly categorized request.
03
Explain the policy
Use the applicable current rules while checking the order-specific conditions.
Information needed
Policy version, timing and item restrictions.
What moves forward
An approved path or a review requirement.
04
Coordinate the next action
Create only permitted return requests or direct the customer to the approved process.
Information needed
Eligibility result and authorized system operations.
What moves forward
A confirmed request with accurate next steps.
05
Track the recorded outcome
Distinguish request creation, item receipt, refund initiation and completed payment.
Information needed
Return and payment status.
What moves forward
An accurate status or an assigned unresolved case.

HUMAN HANDOFF

When an exception needs a person, send the full context.

A handoff should explain the request, completed steps and unresolved decision. Do not make customers repeat information already captured, or leave a failed operation without an owner.

Customer and source-record references
The customer’s stated request or concern
Completed actions and verified results
Unresolved questions and exception reason
Relevant knowledge or policy version
Assigned team and the next decision needed

DESIGN THE DIFFICULT CASES

Exceptions need a path, not a success message.

Use these role-specific cases when reviewing the workflow with business and technical owners. The expected behavior must be agreed before a pilot, not inferred after something fails.

Return window appears exceeded

Route the exception rather than promising a waiver.

Review: Policy basis and customer explanation.

Refund was initiated but not completed

Explain the recorded state and use the approved investigation path.

Review: Payment reference and status.

Requested replacement is unavailable

Offer only approved alternatives or route assistance.

Review: Inventory evidence and customer preference.

SYSTEMS & PERMISSIONS

Connect the work to the source of truth.

Agree the exact records, fields and operations needed for Zara’s role. Reading context and changing a record are different permissions. The categories below are a requirements map, not a guarantee of a native connector for every vendor.

Integration requirements for Zara
System category	Workflow use	Review before connecting
Commerce / orders	Read item, purchase and delivery state.	Customer matching and order eligibility.
Returns management	Create permitted requests and read receipt status.	Policy versions and authorized operations.
Payments / support	Reconcile refunds and assign exceptions.	Distinguish initiation from completion.

Bring system names, versions, API documentation and test-environment access. Review identity matching, retention, network boundaries, credential ownership and how an ambiguous write is reconciled.

Explore integration requirements

PILOT EVIDENCE

Measure the result.
Inspect the failures.

Choose an eligible cohort and record the current baseline. Keep successful conversations, verified outcomes and unresolved exceptions separate. Define a review sample that includes normal cases as well as failed tools and difficult customer requests.

Policy accuracy

Responses consistent with the applicable approved return policy.

Request correctness

Return or exchange requests recorded for the correct item and reason.

Refund-state clarity

Communications distinguishing pending, initiated and completed refunds.

Sample acceptance tests, not published benchmark results
Test case	Expected behavior	Evidence to inspect
Return window appears exceeded	Route the exception rather than promising a waiver.	Policy basis and customer explanation.
Refund was initiated but not completed	Explain the recorded state and use the approved investigation path.	Payment reference and status.
Requested replacement is unavailable	Offer only approved alternatives or route assistance.	Inventory evidence and customer preference.

Agree thresholds and exclusions before testing. Review both business outcomes and action correctness. No uplift, speed improvement or cost saving is claimed here without evidence from the configured workflow.

Review the evaluation approach

IMPLEMENTATION GATES

Prepare the workflow before production.

Pre-built means the role is a starting point. It does not replace knowledge review, integration mapping or your organization’s release decision.

Scope

Define eligible cases around this trigger: a return, refund or exchange enquiry. Agree what counts as a verified request or an assigned policy exception and which requests are excluded.

Output: approved role brief and named business owner.

Connect

Map required fields and approved knowledge to the systems listed above. Separate read permissions from writes, test identity matching and document failure recovery.

Output: reviewed access and data-flow map.

Evaluate

Exercise the normal journey and the exception cases on this page. Inspect responses, system actions and final records together, with a reviewer for unresolved results.

Output: acceptance record and documented open issues.

Release

Start with limited traffic, monitoring ownership and stop conditions. Review the first outcomes before expanding scope; keep a way to pause work and return it to people.

Output: rollout, support and recovery plan.

Estimate the timeline from actual dependencies. Confirm privacy, contact requirements and decision authority with the relevant internal owners. Deployment design is not a substitute for their review.

BUYER GUIDANCE

Choose the right level of responsibility.

Use simpler automation when…

The input is structured, the action is fixed and there is no ambiguity to clarify. A form, notification or rule-based workflow can be the appropriate tool. Do not add a conversational role solely to perform a deterministic system update.

Consider Zara when…

You want routine work executed end to end, without supervising each action. Keep the outcome explicit: a verified request or an assigned policy exception. Validate that the configured role can meet that outcome under your constraints.

Keep a human in charge when…

The case requires policy waivers, disputed refunds and unapproved reimbursements. The specialist can prepare information and route the request without assuming decision authority.

Build a custom workforce when…

The job spans several distinct responsibilities or the pre-built brief does not fit. Define separate roles only where the coordination adds value, and give each handoff a clear owner.

Explore the custom path

BUYER & IMPLEMENTATION QUESTIONS

What to know before hiring Zara.

Does Zara need human approval at every step?

No. Once knowledge, system access and business rules are configured, Zara autonomously matches purchases, checks return eligibility, answers policy questions, creates authorized return requests and tracks return and refund status separately. Human handoff is required for policy waivers, disputed refunds and unapproved reimbursements, or an unresolved case outside the configured rules. The handoff includes the request, completed actions and the decision needed.

Does Zara automatically approve every return?

No. Apply the approved eligibility rules and route exceptions. A customer request is not itself approval.

Can Zara confirm that money reached the customer?

Only communicate a completion state supported by the approved payment record. Refund initiation alone is not proof of receipt.

How do exchanges differ from refunds?

An exchange also needs availability and replacement-order coordination. Keep inventory, return and payment states separate so one successful step does not imply the entire process is complete.

What does Zara do?

Zara autonomously matches purchases, checks return eligibility, answers policy questions, creates authorized return requests and tracks return and refund status separately. Routine actions run within your configured knowledge, permissions and business rules; exceptions and decisions outside that authority go to your team with context. The workflow starts with a return, refund or exchange enquiry and is designed around this outcome: a verified request or an assigned policy exception. Agree the actual configuration and supported actions before release.

Can I set up Zara myself?

Yes. Sign up for UnleashX and configure Zara yourself. Prepare your approved knowledge, business rules, system access and exception owners. Test the configured workflow before using live traffic; supported connections and actions depend on your setup.

Can we customize Zara for our business?

Use the role as a starting brief. Define your knowledge sources, required fields, permitted actions and escalation paths. Keep policy waivers, disputed refunds and unapproved reimbursements outside automatic authority unless a separately reviewed workflow explicitly defines the relevant permissions.

Are the listed integrations available out of the box?

The system categories are a requirements map, not a certified connector list. Confirm your vendors, versions, API operations and network requirements with the integration team. Document read and write access separately and test system failures before production.

How long will deployment take?

Estimate the schedule after reviewing scope, data readiness, integration access and approval requirements. Agree milestone owners and dependencies; a pre-built role does not eliminate configuration, security review or evaluation. No fixed rollout time is promised here.

What happens when a system fails?

Define bounded retries, result reconciliation and human recovery for every write. A timeout can leave the outcome uncertain: inspect the destination record before retrying an action that could create a duplicate. Keep unresolved work visible with an owner.

What evidence supports the performance claims?

The workflows describe autonomous execution within configured rules. The evaluation criteria are proposed tests, not measured customer results. Use an agreed baseline, eligible cohort and reviewed system outcomes to build your own business case. Customer testimonials from other workflows should not be treated as proof of this role’s performance.

Make Zara part of
your workflow.

Configure Zara’s knowledge, connect your supported systems and test the journey. You decide the scope before live work begins.

E-commerce workflows Deployment readiness All AI specialists