BotCurrent↗
← Back to examples

Official recipe · Tool workflows

Prepare lapsed-customer win-back outreach

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

The problem

Businesses need a clear way to revisit inactive customer relationships without composing every re-engagement message from scratch.

Attributed source action

Identify inactive buyers and draft personalized win-back messages.

Proposed review output

Proposed review artifact: Customer-specific draft candidates with inactivity evidence, exclusions and owner-review notes.

Where this framing comes from
  • Core problem: Editorial purpose framing
  • Agent job: Attributed source documentation or report
  • Expected output: Original proposed guidance; not a source-reported result
  • Relevant job roles: Editorial purpose framing
  • Benefit type: Editorial purpose framing
Editorial framing and outcome limits

Describes the task’s purpose and intended output; measured benefit, safe unsupervised operation and successful delivery are not established by this framing.

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

Case-specific decision guidance · untested

Case-specific decision guidance and first checks are original proposals. The linked source supports the attributed task; this added guidance has not been executed.

Read the attributed source evidence and original caveats below ↓

Why use this

  1. A business revisiting inactive buyers may have stale purchase records or an unresolved customer-service issue that changes whether outreach is appropriate. A personalized message can feel careless if it ignores recent contact or invents a reason for the customer’s absence.

  2. A reviewable win-back queue could connect each draft with the evidence for inactivity and any relevant exclusions. The owner could judge whether to re-engage and approve wording without automatically promising incentives or sending messages.

Why an agent / simpler alternative

Useful judgment

Distinguish plausible inactivity from incomplete records and tailor wording to documented relationship context.

Simpler alternative

Use an approved standard campaign when audience criteria and message content are already settled.

Unsuitable when

Contact permissions, customer identity or the reason for exclusion cannot be established.

Proposed inputs

  1. Name

    Buyer-history sample

    Owner

    Sales or retail owner

    Minimum scope

    Relevant last-purchase dates and account identifiers

    Quality check

    Check for recent purchases under merged or alternate records.

  2. Name

    Outreach rules and context

    Owner

    Marketing owner

    Minimum scope

    Approved inactivity definition, exclusions and factual offer terms

    Quality check

    Verify audience permission and unresolved support concerns.

Access and setup — proposed or unknown

Proposed minimum
  1. Read-only scoped customer extracts and a private draft queue.

Compatibility unknowns
  1. Unknown: exact runtime, customer-data connectors and current outreach-platform support.

External actions requiring approval
  1. Sending messages, enrolling recurring campaigns or offering discounts and new commercial terms.

Expected deliverable and review checks

Proposed artifact

Customer-specific draft candidates with inactivity evidence, exclusions and owner-review notes.

Critical checks
  1. Each recipient satisfies the approved selection rules.

  2. Personalization uses supported facts and does not invent dissatisfaction, preferences or offers.

Missing output evidence

No audience query, outreach send or re-engagement outcome is tested here.

Failure signals and proposed responses

  1. Signal

    A recent purchase exists under a different customer record.

    Why it matters

    A “we miss you” message could be factually wrong.

    Proposed response

    Hold the draft and reconcile identity before classifying inactivity.

  2. Signal

    An unresolved complaint is ignored in promotional wording.

    Why it matters

    The message may worsen the customer relationship.

    Proposed response

    Route the case to the account owner and avoid a generic promotion.

Effort and cost — unknown

Setup work
  1. Define inactivity and verify exclusion rules.

Ongoing review
  1. Check customer context and approve each proposed message or bounded campaign.

Unknowns
  1. Unknown: data completeness, delivery costs and response rates.

First check — proposed, unexecuted

Status

proposed_unexecuted

Synthetic fixture

Fictional buyers include one genuinely inactive record, one recent duplicate-account purchase and one open complaint.

Acceptance checks
  1. Only the clear inactive case receives a routine candidate.

  2. Other cases retain specific review blockers.

Stop conditions
  1. Recipient permission, factual context or offer authority is missing.

Limits

  1. Editorial outreach preparation; no message delivery or recovered revenue is established.

Tasks: Sales & outreachCampaigns & growthWriting & content

Useful for: Retail and ecommerce operatorMarketerSales professional

Editorial relevance from the title and source-supported actions; not evidence of the operator’s occupation.
Claude CoworkIndependent testing: No

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://academy.claude.com/tutorials/how-to-install-the-claude-for-small-business-plugin ↗

Attributed to: Anthropic

Official recipe

Read the attributed source action above ↑

Original action type
tool_action
Source outcome limits
This official recipe describes a procedure; it does not prove successful execution or independently reproduced results.
Evidence attribution caveat
This official recipe describes a procedure; it does not prove successful execution or independently reproduced results.
Source approval description
User review before execution.
Named tools
HubSpot; Gmail
Model or version
Unknown
Publication date
Unknown
Source last checked
2026-10-14
Demonstrated in Canada
Unknown
Canadian availability
Unknown
Proposed Canadian adaptation
Check Canadian commercial-message consent and suppressions; human approves audience and send.
Recommended approval boundaries
Review source references and artifacts; approve any posting, external send, ledger entry, contract acceptance or sensitive-data disclosure separately.