@Texas_Twins_Dad agree. with 16 bots the hard part was never the prompt, it was who owns what. every bot gets one job and one rules file, and a chief of staff bot handles anything that crosses desks
@Safety checked mine after this. 260 posts in October, no post labels, but 3 days of SpamHighRecall on the account. that was me replying too much in bursts. now it's max 2 posts a day and replies spread out, and reach came back
@CallumMelly the sheet plus the nudge is what makes it stick. my property bot works the same way: every bill goes into a sheet, it checks on the 1st and 15th, and it only pings me when one is actually coming up
@PrajwalTomar_ sharing is the step I'd slow down on. the apps, files and skills attached to a shared bot work in every teammate's chat, so before sharing any of mine I'd go through that list first. I wrote down what my 16 can touch yesterday and the no row was anything with a card
Grok Bot 1.0 lets a whole team share one bot.
last month 3 friends and I needed one free hour together. each of us has our own bot, so my chief of staff spent a couple of days emailing their 3 bots until Saturday at 7pm worked for everyone.
it worked. it was also 4 bots doing one bot's job ๐
Introducing Grok Bot 1.0. AI teammates that work alongside your whole team.
Share Bots, collaborate with them in Slack and Teams, invite them to meetings, and watch them learn and become more helpful.
@Michael_Fenech_ same pattern here. when I correct a bot on a task it repeats, the fix goes into a saved skill instead of staying in the chat, so the next run starts from the method and not from my last message
@milesdeutscher the audit is the part I'd charge for. before my bot dials anyone it gets 3 rules: only numbers I gave it, never agrees to pay or cancel on a call, every call ends with a written summary. that's the first thing a local owner will ask about
Grok Bot can plug into custom connectors now, so before adding any I wrote down what my 16 bots can touch today.
mostly read and draft. the Cloudflare connector can only read, deploys go through a separate token scoped to Pages.
my no row is one line: anything with a card.
what's on yours?