Bulk unsubscribe from promotional emails
Scan inbox newsletters and execute bulk unsubscribe requests.
Group bulk promotional clutter and initiate customer service calls.
A purged inbox categorized by subscription types, plus call resolution notes from customer support.
"Muse first helped the author clean up 40,000+ Gmail emails, then called Costco customer service on his behalf to resolve an issue, with a call transcript to follow."
Access to Gmail (explicitly mentioned). The authorization method for placing the support call was not specified.
Email OAuth & voice calling feature
Review authorization prompts carefully before connecting.Review generated values, dates, or messages before executing binding transactions or payments.
Gather materials: Access to Gmail (explicitly mentioned). The authorization method for placing the support call was not specified.
Copy the prompt template below, substituting bracketed text like [date range] or [account details] with your real information.
Paste into your Muse session. Watch for required tool authorizations or review prompts.
Compare generated figures, dates, or communication drafts against your original records before taking binding actions.
Do this in two steps. 1) Clean up my Gmail inbox: first summarize the biggest categories of clutter (e.g., newsletters, promotions, old notifications) and how many emails are in each. Then archive or delete [specific categories or senders] for emails older than [30/60/90 days], but do not touch any email from the last [30] days, or anything that looks like a bill, receipt, tax document, or legal correspondence, without asking me first. 2) Then call Costco customer service at [phone number] on my behalf to resolve this issue: [describe the issue, membership number, and the desired outcome]. Do not agree to any charges, returns, or account changes without asking me first. After the call, provide me with the full call transcript and a summary of the resolution.
Before relying on the output or confirming irreversible actions, run these targeted verification checks:
If third-party service connections fail or require permissions, inspect your account tokens.
Check Connections & permissions guide →If large context blocks cause partial truncation, break input into smaller batches.
Review token caps in Access & limits →