← Back to library

Run a cold-email reply desk from one written charter

Max Pidvalnyi details a single-job Grok Bot that handles replies and bookings for his agency. A webhook starts it on each positive reply; a charter covers the offer, booking link, calendar rules, qualification, tone and when to ask him. A gate drops auto-replies, logs opt-outs and checks for duplicates; odd cases need his yes.

  • OutcomeHand positive cold-email replies to a single-purpose agent that follows a written charter, answers within minutes, books the call and updates the CRM, asking you only about odd cases.
  • SetupAn afternoon+
  • LevelAdvanced
  • CreditMax Pidvalnyi (@marioleads)
View original
Works with
Grok BotClaude Code

Published Oct 23, 2026Updated Oct 23, 2026AI dry run on sample input: passed Oct 23, 2026Source verified Oct 24, 2026

When should you use it?

  • Positive replies sit for hours before anyone answers
  • You run cold outreach for your own agency
  • Booking back-and-forth eats your day

Not for: Lists bought without consent where local email law applies; Teams with no CRM or calendar discipline

What do you need, and what do you get?

You need

  • Sending tool with reply webhooks
  • Calendar and booking link
  • Charter document

You get

  • Replies sent within minutes
  • Booked calls with notes
  • CRM updated in the same run

How does it work, step by step?

  1. Write the charterPut the offer, booking link, calendar rules, qualification bar, tone and escalation rules in one document the agent reads every time.
  2. Trigger on positive repliesHave the sending tool call the agent when a reply is classified as interested.
  3. Gate every messageDrop out-of-office notes, log unsubscribe requests without replying, and check the thread for an earlier answer.
  4. Ask one clear questionPropose a single time with a yes or no, put the booking link in a postscript, and ask qualification in the same email.
  5. Book and recordWhen a time is chosen, check the slot, book with notes, confirm and update the CRM together.

The prompt

Our own prompt, inspired by Max Pidvalnyi (@marioleads) and written to work in Grok Bot and Claude Code. Values in lime are placeholders.

Fill in the blanks (optional; the copied prompt uses your values)

Prompt3 variables
Read the charter: {charter}
New reply in thread: {thread}
Classify it: interested, objection, auto-reply, unsubscribe, unclear. For unsubscribe, log it and stop. For auto-reply, stop. For interested, check the thread for an earlier answer, then draft one reply proposing a single time from {calendar_rules} as a yes or no question, with the booking link in a PS. Flag anything the charter says needs my approval.

Inspired by Max Pidvalnyi (@marioleads): Post on booking agency sales calls from cold email replies. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.

What can go wrong?

  • Answering an unsubscribe request with a sales message is a legal and reputation problem; log it and stop.
  • Two runs on one thread can double-reply; check before sending.

Our take

Max Pidvalnyi (@marioleads) details a single-job Grok Bot that handles replies and bookings for his agency. A webhook starts it on each positive reply; a charter covers the offer, booking link, calendar rules, qualification, tone and when to ask him. The charter is the heart and the easiest piece to copy. Put everything needed to sound and decide like you in one place, and fold each correction into it. The gate is what keeps it safe: drop out-of-office replies, log unsubscribe requests and stop rather than answer them with a pitch, and check the thread for an earlier answer so two runs cannot double-reply. Propose one time with a yes or no question. When a time is agreed, check the slot, book and update the CRM together. Do not use it on bought lists where consent rules apply. Fold each correction you make into the charter, so the agent improves rather than repeating the same mistake next week.

Where the time goes back: Interested replies get answered while the prospect is still at their desk, and booking logistics stop eating your day.

FAQ

What still needs a human?
Unusual cases, like extra people copied in, a doubtful fit or a pricing oddity, wait for the owner's approval in his setup.
Does qualification block booking?
No. If revenue is unknown, the question rides along in the booking email.

Source and credit

Inspired by Max Pidvalnyi (@marioleads). We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.

Inspired by
Post on booking agency sales calls from cold email replies
Creator
Max Pidvalnyi (@marioleads)
Published on
X
Original date
Oct 6, 2026
License
Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
Originally for
Grok Bot
AI dry run
Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS: Gates held on desk check; no live sends or purchases.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails.
Verified
Oct 24, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.

Are you the creator? Claim or correct this page.

More in Sales

All 59 Sales playbooks →

Related playbooks

SalesPrompt✓ AI dry run

Draft cold emails to Lavender's reply rules

Get a short cold-email draft and subject line that follow Lavender's published length, clarity, subject and ask rules — held as a draft until you send it.

Credit: Chelsea Castle (Lavender)

Minutes