Post-sales customer work with Grok Bot

全屏预览

Break the work into roles, handoffs and acceptance checks. Use the following task arrangements as practice scenarios, and verify results in your own setup.

Post-sales is everything that happens after the sale. you are the customer's main contact from kickoff through renewal. you own getting teams onboarded, making sure they see value, and making deployment as painless as possible. It's energizing work.

What's hard isn't the customer relationship, it's the context. Every account is a pile of call transcripts, Slack channels, email threads, calendar invites, and promises you made in passing, and you own a lot of accounts.

Start with one small task that has clear inputs and deliverables. Separate preparation, execution and verification; record the owner, output location and next step before expanding the scope.

you only manage one bot

His name is Gus. Gus is your chief of staff, and he manages everyone else so you can keep the parts of the job you love: the relationships, the strategy on each account, face time, deciding what matters today, and the final yes on anything that goes out with your name on it.

Gus exists because you tried running twenty agents yourself first, and it was overwhelming. Twenty chats, twenty personalities, all wanting a reply from you. Now you have one. If you can't tell by the end of this, you are a cat person.

Assign engineering roles for mobile, desktop, infrastructure and verification. Define inputs, deliverables and permissions, then complete one small task and its acceptance checks before expanding the scope.

• Follow-ups holds every draft waiting on me and remembers what happened to it.
• Account specialists, one per account, whose entire job is to know that customer better than I do.
• Ink writes emails and Slack messages that sound like me.
• Questions is wired to our docs, for anything a customer might ask about the product.
• Career gives me feedback weekly and quietly keeps a list of my wins.
• Scout reads our internal channels so I don't have to.

Days go by where you don't open a single one of those chats. They remember your directions, they report to Gus, and Gus decides what actually needs you. There's a dozen more behind them you haven't touched in weeks, which is exactly how you like it.

Bot's own computer

Plugins cover the systems where there are connections available: calendar, Slack, mail, docs, call transcripts. Grok Bot also has its own computer, which handles everything that doesn't have a plugin set up. you log the bots into the tools you use, they work the way you do, and they keep going when your laptop is closed.

The rest of what your agents use their computer for:

• Checking LinkedIn before a first call
• Internal pages I have access to but that no connector reaches. I point it at the page instead of pasting the page into a chat.
• Deck review. I ask Gus to open the PowerPoint and tell me what is working visually and what isn't.
• Screenshots and short screen recordings, so a customer's how-do-I question gets a picture instead of three paragraphs.

The routines

These are one of your favorite parts of Grok Bot. A routine has a trigger, scheduled or event based, and runs whether or not you show up.

Most runs of my watches produce nothing, and that's by design. A routine that runs, looks, and decides I don't need to know is doing its job.

Here's the roster of your routines:

全屏预览

全屏预览

• Daily brief, 8:30 on weekdays. Calendar, Slack, and call transcripts, folded into one brief that starts my day with exactly what to focus on. This is such a great way to start the day aligned on what needs to happen.
• Before-every-call prep. Checks every fifteen minutes but only writes a prep when a call is fifteen to thirty-five minutes out, so the card lands just in time. It includes things like who's on the invite and who actually accepted, the one thing to make sure we leave with, a few talking points with links, and a short do-not list.
• Unfinished promises, at 9, 1, and 4. Things I said I'd do, they link back to where I said it if needed. Done things drop off on their own.
• Unanswered asks, every fifteen minutes. Only looks at messages I sent that got no reply, and only surfaces the ones where the next move is mine. It never replies for me. Most runs are silent.
• Visibility watch, weekday mornings. Finds one customer win worth telling the company about and stages a post I could paste.
• Exhaust watch, weekday mornings. Scans the live accounts for a usage cliff or a brewing escalation.
• Friday dashboard. Regenerates the account heatmaps and trend charts and files them into the Drive tracker, so Friday I open one view to see where I need to focus my time.
• Self-improvement scan, Wednesdays. Gus audits himself: which routines fired and got ignored, what I've now asked for by hand three times, what should exist and doesn't. He proposes the fix, I say yes or no.

When an account has you underwater

Some days an account gets away from you. Too many threads, too many people, and you have lost track of what you owe who. So you open Gus and type exactly that: "you are overwhelmed with x account."

He tells you a joke first. Why? Because you are overwhelmed, and why not.

Then he pulls everything together: what's actually happened across the transcripts, calendar, and Slack, what you have promised and to whom, and what to do next.

A day in the life

8:30. The brief is waiting. Four calls, six accounts, three sends, and one flag: usage at one account dipped by a third last week.

9:26. Prep card sent to you for the 9:45 meeting. Who's in the room, and follow ups that you haven't heard.

9:45 to 11:30. Customer time. you are in back-to-back meetings and every time you leave a call the transcripts land, recaps get drafted, research is done for questions they asked, and materials are created that you told them you would send them.

11:30. Gus has three recaps waiting and email responses are sitting in your Gmail drafts. A quick update on the customer flag from the morning. you tweak the recaps and press send. The delta between the drafts and what is sent is shared as feedback to Ink.

2:10. A customer asks a question in a Slack channel; your Questions bot drafts you an answer with sources and you press send when you get a free moment. Another call ends with a feature request; Scout knows your team’s process, Gus drafts it, you post it, and then one nudge reminds you to reach back out to an IT lead who never answered your SSO question.

4:30. Tomorrow's prep from Gus, plus tonight's short list to do before you sign off. you do them and close the laptop. Career quietly logs some call feedback for later this week.

you build out weekly routines too. Every Wednesday there's a self-improvement proposal waiting for a yes or no. Every Friday the dashboard updates itself. And on the weekend the agents are quiet. Gus still keeps an eye out and will ping you if anything urgent pops up.

Success is measured by how much time you now get to spend with customers, while Grok Bot runs the system in the background.

More time in the rooms

Grok Bot has fundamentally changed where your attention goes. you walk into a customer room already knowing what moved since the last meeting, and you can send follow ups faster, and with greater accuracy, because the promise list is with Gus and Gus doesn't forget.

If you want to build a version of this for your own work

you started with a voice memo of your day. you talked for over ten minutes about how you spend your time, what you love doing, what you don't like spending time on, and the parts you refuse to automate away. Then send that over to your bot and ask it to build you a system that makes your life easier.

If you want a quicker path, open your first agent, send it this post for inspiration, and ask it to turn this into a playbook that it should follow.

Let's keep learning from each other.