BotCurrent↗
← Back to examples

Official recipe

Arrange a no-charge replacement for a lost or damaged order

A missing or damaged purchase can leave staff uncertain whether to replace it, await better evidence, or investigate an earlier remedy.

Read original recipe
Suggested result

A packet linking purchase, evidence, approved remedy and replacement reference.

What you need: Source-named agent: Gorgias AI Agent. Suggested inputs: Incident bundle; Remedy history; Replacement policy. Use fictional claims and simulated order responses first. Assign one incident key across repeated contacts. Workflow costs and current compatibility remain unverified.

Proposed: approve the merchant’s replacement policy and value limits. Require the shopper to accept the selected remedy and address; escalate disputed loss, repeat claims and hazardous damage.

Official recipe. BotCurrent has not independently tested this workflow.

Setup and access

Proposed inputs

  1. Name

    Incident bundle

    Owner

    Support lead

    Minimum scope

    One original order and relevant evidence

    Quality check

    Exclude unrelated customer history.

  2. Name

    Remedy history

    Owner

    Support lead

    Minimum scope

    Earlier claims and actions for this incident

    Quality check

    Check for an existing replacement or refund.

  3. Name

    Replacement policy

    Owner

    Merchant

    Minimum scope

    Evidence requirements and value limits

    Quality check

    Identify exceptions requiring staff.

Access and setup — proposed or unknown

Proposed minimum

  1. Use fictional claims and simulated order responses first.

  2. Assign one incident key across repeated contacts.

Compatibility unknowns

  1. Unknown: duplicate-prevention, inventory reservation and carrier callbacks.

External actions requiring approval

  1. Replacement release, address disclosure, customer messages and stock changes.

Detailed steps and output format

At a glance

Suggested result
A packet linking purchase, evidence, approved remedy and replacement reference.Suggested; untested.
Tool
Gorgias AI AgentSource-named; check current access.
Suggested inputs
Incident bundle; Remedy history; Replacement policyProposed; access notes below.
Human review
Proposed: approve the merchant’s replacement policy and value limits. Require the shopper to accept the selected remedy and address; escalate disputed loss, repeat claims and…
Read full note

Proposed: approve the merchant’s replacement policy and value limits. Require the shopper to accept the selected remedy and address; escalate disputed loss, repeat claims and hazardous damage.

Suggested boundaries; source approvals below.
Setup notes
Use fictional claims and simulated order responses first. Assign one incident key across repeated contacts.Guide notes; proposed setup untested.
Cost
Workflow cost not established. Check current tool pricing, setup and human review costs before trying it.No measured cost or time added.
Content depth
Source-linked example · suggestions untestedDepth does not establish successful execution.
Check source evidence and limits ↓

Function and scope

Customer support, Operations · Multi-step workflow

Editorial classification; no execution or compatibility test is implied.

No tool mapping reviewed for this task.

Source-backed example. Practical decision guidance is proposed and untested; this is not a full implementation guide.

The problem

A missing or damaged purchase can leave staff uncertain whether to replace it, await better evidence, or investigate an earlier remedy.

Suggested task · untested

Proposed: check an incident against replacement rules and prepare one remedy or exception.

What you could produce

A packet linking purchase, evidence, approved remedy and replacement reference.

Where these suggestions come from
  • Core problem: Our suggestion; no result reported by the source
  • Agent job: Our suggestion; no result reported by the source
  • Expected output: Our suggestion; no result reported by the source
  • Relevant job roles: Our suggestion; no result reported by the source
  • Benefit type: Our suggestion; no result reported by the source
Suggestions and their limits

Describes the proposed purpose and review output; measured benefit and successful delivery are not established.

Editorial synthesis based on the linked source. This framing does not add evidence of successful delivery or results.

Before you try it · suggestions untested

Original decision guidance and first check are proposals. The source supports the attributed task; this guidance has not been executed.

Read the attributed source evidence and original caveats below ↓

Why use this

  1. A customer may contact several channels about the same parcel. Without shared incident identity, an apparently helpful response can create several replacements.

  2. A bounded agent can gather missing details conversationally and prepare the next operational step, while leaving disputes and policy exceptions visible to a person.

Why an agent / simpler alternative

Useful judgment

Distinguish a request for an update from acceptance of a replacement and recognize conflicting delivery evidence.

Simpler alternative

Use a structured claims form and staff-approved replacement button for low volume.

Unsuitable when

Evidence is disputed, damage suggests a safety issue, or stock ownership is unclear.

Expected deliverable and review checks

Proposed artifact

Incident-to-replacement audit trail.

Critical checks

  1. Exactly one authorized remedy for the incident.

  2. Replacement items match the approved remedy.

  3. Creation, dispatch and receipt remain separate statuses.

Missing output evidence

Unknown: no actual replacement order or delivery proof inspected.

First check — proposed, unexecuted

Status

proposed_unexecuted

Synthetic fixture

Three fictional claims: an overdue parcel, a damaged item and a repeated claim already replaced.

Acceptance checks

  1. Prepare only eligible new remedies.

  2. Flag the duplicate.

  3. Never label an order record as delivered.

Stop conditions

  1. Real customer data, outbound messages or fulfilment release.

Tasks: Shopping & productsResearch & discoveryEmail & messages

Useful for: Customer support specialistRetail and ecommerce operatorOperations manager

Editorial relevance from the title and source-supported actions; not evidence of the operator’s occupation.
Gorgias AI AgentIndependent testing: No
Failure handling, costs and limits

Failure signals and proposed responses

  1. Signal

    Repeated contact starts a new replacement

    Why it matters

    Retries can create duplicate goods movements.

    Proposed response

    Look up the incident outcome before retrying.

  2. Signal

    Carrier evidence arrives after approval

    Why it matters

    A late scan may change the remedy.

    Proposed response

    Pause unreleased work for human reconciliation.

Effort and cost — unknown

Setup work

  1. Define incident identity and remedy rules.

Ongoing review

  1. Sample repeated claims and unresolved carrier conflicts.

Unknowns

  1. Unknown: replacement costs, carrier charges and review workload.

Limits

  1. Unexecuted proposal; no fraud finding or delivery guarantee is implied.

Full source evidence

Official recipe · Tool workflows

Original task title: Arrange a no-charge replacement for a lost or damaged order

Editorial candidate. This is source-backed reporting or a documented workflow. BotCurrent has not independently tested this task. A proposed Canadian adaptation is not evidence of a Canadian deployment or compliance certification.

Original source

https://docs.gorgias.com/en-US/ai-agent-actions-make-changes-to-shopify-orders-757792 ↗

Attributed to: Gorgias Help Center

Supporting source context

Project documentation supporting the linked recipe’s scope, permissions and limits. These references do not establish an independent test or add counted jobs.

Official recipe
Original action type
tool_action
What the source reports
Evaluates shipping evidence or reported damage, offers free reshipment, duplicates the order and emails confirmation.
Source outcome limits
Creation does not prove dispatch, delivery or inventory correctness. Loss thresholds, duplicate-claim controls and authentication are unspecified. Vendor test chats act on connected real records. Multi-step failure stops later actions; earlier writes can persist before staff handoff.
Evidence attribution caveat
This official recipe describes a procedure; it does not prove successful execution or independently reproduced results.
Source approval description
Explicit reshipment execution approval is unspecified.
Named tools
Gorgias AI Agent; Shopify.
Model or version
Unknown
Publication date
Unknown
Source last checked
2026-10-14
Demonstrated in Canada
Unknown
Canadian availability
Unknown
Proposed Canadian adaptation
Proposed: check Canadian carrier evidence, address coverage, inventory ownership and cross-border duties before a replacement. Do not infer Canadian operation from documentation.
Recommended approval boundaries
Proposed: approve the merchant’s replacement policy and value limits. Require the shopper to accept the selected remedy and address; escalate disputed loss, repeat claims and hazardous damage.