Audit subscriptions and email companies to cancel them
Claude Code pulled transactions across credit cards, flagged recurring charges, and drafted cancellation emails, recovering $700. Task: Suggested implementation: Grant an AI agent read-only access to transaction history and email drafts. The agent identifies recurring charges, queries the user for confirmation, and drafts cancellation emails for unused subscriptions. Human role: The user must explicitly approve each flagged charge and review the drafted email before sending.; tools: Claude Code. Human role: Source evidence is unavailable regarding specific human roles beyond granting initial access and confirming subscription usage.; limitations: Prerequisites include secure API access to banking and email services with strict read-only permissions. Operating costs involve AI subscription fees and potential integration development. Exception handling requires manual intervention for ambiguous transactions or failed email deliveries. Source reliability is low due to the inaccessible URL..
Tools
Published on Agent Work Atlas:
Overview
Claude Code pulled transactions across credit cards, flagged recurring charges, and drafted cancellation emails, recovering $700.
Workflow
Suggested implementation: Grant an AI agent read-only access to transaction history and email drafts. The agent identifies recurring charges, queries the user for confirmation, and drafts cancellation emails for unused subscriptions. Human role: The user must explicitly approve each flagged charge and review the drafted email before sending.
Reported result
Actual outcomes are unknown as the source returned a 403 error and no execution logs were provided. Proposed acceptance check: Verify that the agent correctly identifies at least 90% of active recurring charges in a sample month and that zero unauthorized emails are sent.
Human role
Source evidence is unavailable regarding specific human roles beyond granting initial access and confirming subscription usage.
Limitations
Prerequisites include secure API access to banking and email services with strict read-only permissions. Operating costs involve AI subscription fees and potential integration development. Exception handling requires manual intervention for ambiguous transactions or failed email deliveries. Source reliability is low due to the inaccessible URL.
Try it
Act as a financial audit assistant. I will provide [replaceable inputs: a CSV of credit card transactions and a list of known active subscriptions]. Your task is to identify recurring charges not in the active list. For each candidate, ask me: 'Do you use [Service Name]?' If I say no, draft a cancellation email to [Service Contact] using the template: 'Subject: Request to Cancel Subscription...'. Do not send any emails. Output a JSON object with keys: 'flagged_charges', 'user_responses', 'drafted_emails'. First, perform a dry run on 5 sample transactions to demonstrate the logic. Wait for my confirmation before processing the full dataset. If transaction data is missing, ask for the specific date range and card last four digits.
Source reports are not independently verified. Publication date is the catalog publication date, not the original article date.