Why is nobody talking about this? π
Your Grok Bot can make your phone calls for you. And you can try it for FREE π
Connect it to Bland and you get free credits to start. Zero cost to test it.
Tell it what you want once:
β "Bring my fiber bill back down"
β "Get the other $100 back from the spa"
β "Get money off my internet bill"
β "Cancel the old pet-store autoships"
It stays on the line, works the retention desk, and comes back with the money π°
50 minutes on the phone. NONE of them yours.
It costs you nothing to try. Save this and set it up this weekend π
FREE template below π
I exported my Grok Bot usage. 78% of my tokens were my Bots RE-READING old context π³
965 million tokens since Oct 1. Only 1% was my Bots actually writing anything.
Here's how to check yours, and the fix π
One reply in my file: it re-read 47,369 tokens to write 402.
That's how Grok Bot works. Every reply and every routine run re-reads the Bot's whole chat. The longer the chat, the more it re-reads on every turn.
Check yours:
β https://t.co/EgtMSQWvLo
β Usage
β Scroll to "Usage events"
β Hit Export
The fix: if a Bot's chat has been running for days, Duplicate it.
The copy keeps its settings, skills and routines. It starts with a clean chat.
Move anything it needs to remember into its description first. Duplicate drops learned memory too.
Then pause the old Bot's routines so nothing runs twice.
Save this for your next usage scare π
Your Grok Bot never forgets. That's the problem π³
It can quote you a 3-week-old price and sound 100% sure.
One rule fixes it π
Even xAI's FAQ says it: for anything important, check the current source, not memory.
β Memory: your taste and corrections
β Not memory: prices, features, schedules, anything that changes
Tell your Bot once:
"If a fact can change, don't answer from memory. Open the source and link it."
Don't remember the answer. Remember where to get it.
Full map π Save this π
The re-reading gets WAY worse when your Grok Bot runs on a timer π
My Bot found one routine firing 672 times a week. Every 15 minutes. Every run re-read the whole chat.
Here's the fix π
Every routine run re-reads the Bot's whole chat. Even the runs that find NOTHING new.
A quiet run still pays the full re-read. Every 15 minutes, all day, all night.
The fix: check first.
β Read one value (a count, a timestamp, the latest commit)
β Compare it to the last one saved
β Same? Log "no change" and stop
β Changed? Run the real job
Paste this into the routine:
"Before doing any work, read only [the status field / latest commit / item count / last-updated date] and compare it to the value saved in routines/state/[name].txt. If it matches, log no change and stop. Don't open anything else. Don't browse around. If it changed, save the new value, then do the job."
"Don't browse around" is the line that does the saving. Leave it out and the Bot tends to wander once the page is open.
Read a few days of the log before you trust it.
Save this before your next routine fires π