BotCurrent↗
← Back to examples

Official recipe

Adjust future subscription shipments and charge timing

A subscriber wants fewer or later deliveries without ending the service, but their words may refer to one box, the next charge or the recurring schedule.

Read original recipe
Suggested result

A schedule-change receipt naming the subscription, affected occurrence, continuing cadence and next expected charge.

What you need: Source-named agent: Gorgias AI Agent. Suggested inputs: Subscriber request; Schedule snapshot; Timing policy. Use fictional subscription schedules and simulated action responses. Retain both previous and proposed timing for review. Workflow costs and current compatibility remain unverified.

Proposed: obtain approval for the selected subscription, affected shipment and next charge date. Confirm recurrence changes clearly; do not convert a cancellation request into retention without the shopper’s choice.

Official recipe. BotCurrent has not independently tested this workflow.

Setup and access

Proposed inputs

  1. Name

    Subscriber request

    Owner

    Shopper

    Minimum scope

    Desired occurrence or date

    Quality check

    Confirm whether future recurrence changes.

  2. Name

    Schedule snapshot

    Owner

    Merchant

    Minimum scope

    Subscription IDs and pending occurrences

    Quality check

    Check current version and local timezone.

  3. Name

    Timing policy

    Owner

    Merchant

    Minimum scope

    Cutoffs and permitted intervals

    Quality check

    Separate billing and warehouse authority.

Access and setup — proposed or unknown

Proposed minimum

  1. Use fictional subscription schedules and simulated action responses.

  2. Retain both previous and proposed timing for review.

Compatibility unknowns

  1. Unknown: plan-specific action support and downstream cutoff synchronization.

External actions requiring approval

  1. Subscription writes, customer notices, payment changes and persistent connections.

Detailed steps and output format

At a glance

Suggested result
A schedule-change receipt naming the subscription, affected occurrence, continuing cadence and next expected charge.Suggested; untested.
Tool
Gorgias AI AgentSource-named; check current access.
Suggested inputs
Subscriber request; Schedule snapshot; Timing policyProposed; access notes below.
Human review
Proposed: obtain approval for the selected subscription, affected shipment and next charge date. Confirm recurrence changes clearly; do not convert a cancellation request into…
Read full note

Proposed: obtain approval for the selected subscription, affected shipment and next charge date. Confirm recurrence changes clearly; do not convert a cancellation request into retention without the shopper’s choice.

Suggested boundaries; source approvals below.
Setup notes
Use fictional subscription schedules and simulated action responses. Retain both previous and proposed timing for review.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 · Single task

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 subscriber wants fewer or later deliveries without ending the service, but their words may refer to one box, the next charge or the recurring schedule.

Suggested task · untested

Proposed: clarify the intended duration, identify the correct subscription and prepare a confirmed before/after timing change.

What you could produce

A schedule-change receipt naming the subscription, affected occurrence, continuing cadence and next expected charge.

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. “I have enough for now” does not say whether to skip once, defer until a date or change the ongoing interval. Confusing these choices can create an unwanted charge or prolonged interruption.

  2. A conversational agent can surface that distinction and preserve the customer’s choice, leaving billing exceptions and already-committed work for staff review.

Why an agent / simpler alternative

Useful judgment

Separate a temporary pause from a permanent cadence change and resolve which subscription the shopper means.

Simpler alternative

Use a clear self-service subscription calendar with validated options when available.

Unsuitable when

The shopper disputes charges, requests account closure, or cannot identify the affected subscription.

Expected deliverable and review checks

Proposed artifact

Before/after schedule receipt.

Critical checks

  1. The intended occurrence changes only once.

  2. Continuing cadence matches the shopper’s choice.

  3. Existing orders are explicitly accounted for.

Missing output evidence

Unknown: no actual schedule-change or charge outcome inspected.

First check — proposed, unexecuted

Status

proposed_unexecuted

Synthetic fixture

Three fictional requests: skip once, resume on a named date and change cadence; add one already-created order.

Acceptance checks

  1. Keep the three intents distinct.

  2. Show the next two expected dates.

  3. Flag committed work separately.

Stop conditions

  1. Real billing data, live writes or customer messages.

Tasks: General workflows

Useful for: Customer support specialistRetail and ecommerce operator

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

    “Next Friday” resolves differently across systems

    Why it matters

    The customer may be charged on an unintended date.

    Proposed response

    Confirm an absolute date and timezone.

  2. Signal

    Request repeats after a timeout

    Why it matters

    A second skip could suppress another delivery.

    Proposed response

    Read the current schedule before retrying.

Effort and cost — unknown

Setup work

  1. Define date interpretation, cutoffs and version checks.

Ongoing review

  1. Review retries and disputed timing.

Unknowns

  1. Unknown: usage fees, connector maintenance and exception rates.

Limits

  1. Proposed guidance only; no retention improvement or payment reversal is claimed.

Full source evidence

Official recipe · Tool workflows

Original task title: Adjust future subscription shipments and charge timing

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-manage-recharge-subscriptions-757839 ↗

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
Collects timing preferences and updates future subscription cadence or charge dates; can skip an upcoming shipment. Recharge pause postpones the next charge. Most actions require one active subscription; selected-subscription pause is an exception.
Source outcome limits
Documented future schedule updates, not cancellation of an already-created order, refunded payment or measured retention benefit. Skipping is supported only before order creation. Customer authentication details 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
Confirms charge dates. Shopper approval for skips is enabled by default, but configurable.
Named tools
Gorgias AI Agent; Recharge actions. Loop Subscriptions is a same-job alternate.
Model or version
Unknown
Publication date
Unknown
Source last checked
2026-10-14
Demonstrated in Canada
Unknown
Canadian availability
Unknown
Proposed Canadian adaptation
Proposed: verify local billing dates, currency, merchant terms and Canadian subscription disclosures. Keep customer timing requests separate from financial advice or debt arrangements.
Recommended approval boundaries
Proposed: obtain approval for the selected subscription, affected shipment and next charge date. Confirm recurrence changes clearly; do not convert a cancellation request into retention without the shopper’s choice.