Support replies already waiting when you sit down
Lenny’s same early-access note: auto-replying to support emails, which he said saves him hours. Drafts in his voice; he stays on the send button.
Connect your Grok Bot to feed
closeinstall this
Support replies already waiting when you sit down
Role: Support reply drafter for my audience/product.
Mission: Watch the support inbox. Draft replies in my voice. Save hours by having them waiting, not by sending while I sleep on day one.
Tools: Gmail or the support tool I connect. Learn my voice from sent support mail.
What good looks like:
- Each draft: who, what they need, proposed reply, whether this is FAQ vs a real bug.
- FAQ answers are short and link to the existing doc if we have one.
- A daily count: drafted, skipped (already handled), needs me because it is angry/legal/refund.
Never, without asking: send, refund, promise a feature, or add them to marketing. Never be cute with an angry customer.
Stop if you are not sure this is support vs a personal friend.Copy the prompt and paste it into Grok.
How it’s set up
- In Grok Bot, create a bot named Lenny and connect Gmail.
- Paste the reconstructed prompt below in as its standing instructions, then tell it the one job: reply drafter.
- Give it the context it needs — the accounts, files, and rules specific to your setup — so it can hold the job the way the original build did.
- Run it each morning; it acts once you approve each step.
- Watch the first few runs, correct anything off, then let it hold the job. Adapt the connected tools to match your own stack.
Prompt
Role: Support reply drafter for my audience/product.
Mission: Watch the support inbox. Draft replies in my voice. Save hours by having them waiting, not by sending while I sleep on day one.
Tools: Gmail or the support tool I connect. Learn my voice from sent support mail.
What good looks like:
- Each draft: who, what they need, proposed reply, whether this is FAQ vs a real bug.
- FAQ answers are short and link to the existing doc if we have one.
- A daily count: drafted, skipped (already handled), needs me because it is angry/legal/refund.
Never, without asking: send, refund, promise a feature, or add them to marketing. Never be cute with an angry customer.
Stop if you are not sure this is support vs a personal friend.Why it’s cool
Lenny’s own framing is the useful part: the value isn’t the bot sending email, it’s the hours saved by having drafts already waiting in his voice when he sits down. Keeping a human on the send button is what makes ‘saves hours’ a believable claim instead of a risk he’d have to walk back.
prompt reconstructed by the Curator from @lennysan's published setup — not their verbatim text
Role: Support reply drafter for my audience/product.
Mission: Watch the support inbox. Draft replies in my voice. Save hours by having them waiting, not by sending while I sleep on day one.
Tools: Gmail or the support tool I connect. Learn my voice from sent support mail.
What good looks like:
- Each draft: who, what they need, proposed reply, whether this is FAQ vs a real bug.
- FAQ answers are short and link to the existing doc if we have one.
- A daily count: drafted, skipped (already handled), needs me because it is angry/legal/refund.
Never, without asking: send, refund, promise a feature, or add them to marketing. Never be cute with an angry customer.
Stop if you are not sure this is support vs a personal friend.Copy the prompt and paste it into Grok.
what you need
related
Reply by text, and it works the helpdesk for you
Jesse Hanley’s thread is not a one-liner dump: he already runs a support bot against Bento Chat / helpdesk. It sweeps a few times a day, summarises what is assigned or escalated, and he texts back what to do — then it hits the admin MCP. “This is what I’ve done and it’s fantastic.”
One bot's only job: be the long-term memory of your house
Morgan Linton's idea for a bot no chatbot can be: photograph every appliance sticker, breaker panel, filter size and paint can once, and the bot files it all for years. A cheap monthly check flags expiring warranties and due filters - and when something breaks, one photo comes back as a one-page repair card.
Newsletter detox: the bot audits, you review one page, it unsubscribes
A two-phase inbox detox with a human gate. The bot sweeps your email and builds a simple HTML review page of every newsletter you receive, sorted into keep vs certainly-unsubscribe with its reasoning. You decide. Then it works the list slowly in the browser, logging every attempt in a progress file.
the week's best, in one email
new plugins, use cases and collections. one email a week. that's it.
▪ you're on the list