How to use Grok Bot to find subscriptions to cut and check refunds

@SirMaximusIX describes running several Grok Bots for personal administration. The financial workflow begins with a deliberate access decision: he linked his bank accounts and asked Grok to optimise them. He says it found two subscriptions to cut, worth about $50 a month.

That wording establishes identified cuts, not evidence that the subscriptions were cancelled or that the monthly saving has already been realised. The post does not name the subscriptions, show cancellation confirmations or explain the permissions required for any binding account changes.

A second useful responsibility is checking that refunds actually land in his accounts. Rather than treating an expected refund as completed, the reported task follows through to the account-level result. No particular refund, amount, recovery rate or checking schedule is supplied, so none is inferred here.

The accompanying image is a Grok Bot illustration, not a transaction record. Both the subscription finding and refund monitoring remain firsthand claims by the poster. This entry deliberately excludes his separate cash-movement recommendation and savings-rate claims.

The practical boundary is between reviewing financial activity and authorising changes: the post establishes that he granted access, but does not describe a cancellation or payment approval process.

Prompt
Suggested prompt (written by Agents In Use, not the author's)

Source: X · @SirMaximusIX