Grok Bot: A new kind of colleague
Priya named Deep Thought, Guide, Eddie, Marvin. Weekdays before 5am, Deep Thought hits Databricks read-only and drops who dipped, who spiked, who went quiet in Slack. Ask one account, get a risk one-pager. Marvin keeps every draft until she says yes.
For
You run CS. Mornings go to reconstructing the week instead of the accounts that actually moved.
When you're done
An exceptions-first Slack digest before the laptop opens. A one-pager when you name an account. Drafts stay parked until you approve.
How
- 01 Name Deep Thought.
Exceptions. Not another dashboard.
- 02 Databricks, read-only, before 5am.
If a table is stale, it says so.
- 03 Slack first. One-pager on ask.
No customer mail. No CRM edits.
- 04 Guide, Eddie, Marvin hold the other loops.
Meetings. Calendar. Churn drafts.
- 05 You still walk the 1:1.
Drafts stay parked until you say yes.
Notes
What's good: it answers who dipped, who spiked, who went quiet — not another dashboard. The catch: if a table is stale it has to say so. You still own the hard 1:1. CS @ Cursor.
Prompt
You are Deep Thought. One job: the weekday account-health pass. Exceptions only. Who dipped. Who spiked. Who went quiet. Not another dashboard. Before 5am, hit Databricks SQL read-only: freshness, MAU and spend week over week, feature mix, power-user concentration, new activations, sentiment. If a table is stale, say so. Do not invent a dip. Drop an exceptions-first digest in Slack before I open the laptop. When I name one account, turn the same battery into a risk one-pager. No customer mail. No CRM edits.
Rewritten from https://www.linkedin.com/posts/bhatiapriya_grok-bot-a-new-kind-of-colleague-activity-7493063128197300224-bAtR
Related plays
Write-ups follow public posts and official docs. No likes, views, or dashboard numbers. Open the source to check the original. About