← Back to library

Run freelance admin through Telegram with one-tap approvals

Farooq Shabbir, a consultancy owner, built an always-on OpenClaw agent with three skill files and one workflow. Each morning Telegram gets a digest of stuck or failing PRs and Slack to-dos; each evening he can approve routine actions with one tap.

  • OutcomeStart each day with a short message of stale pull requests and Slack action items, and approve weekly client updates and follow-ups with a single reply.
  • SetupAn afternoon+
  • LevelAdvanced
  • CreditFarooq Shabbir
View original
Works with
OpenClawClaude

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?

  • You run a small dev consultancy
  • Weekly reports and chasing replies eat your week
  • You already use Telegram

Not for: Unreviewed client emails; Agencies with shared inboxes and many owners

What do you need, and what do you get?

You need

  • GitHub CLI access
  • Slack and Linear read access
  • Mail access for follow-ups

You get

  • Morning digest
  • Friday client update drafts
  • Follow-up drafts awaiting approval

How does it work, step by step?

  1. Define stale workChoose rules such as open a day with no review, failing checks or an urgent label.
  2. Write each skill as a fileOne for the PR digest, one for client updates, one for follow-ups.
  3. Schedule themMorning digest daily, client update weekly, follow-up scan regularly.
  4. Route to chatDeliver everything to Telegram with yes and no options.
  5. Send only on yesNothing reaches a client until you approve.

The prompt

Our own prompt, inspired by Farooq Shabbir and written to work in OpenClaw and Claude. Values in lime are placeholders.

Prompt0 variables
Every weekday at 8 AM, check my GitHub repos for pull requests waiting a full day with no review, with failing checks, or labeled urgent, and list Slack messages from yesterday that ask me to do something. Message me the digest on Telegram. Each Friday, write a draft update per client based on what was merged and which Linear tickets closed, and share those drafts with me. Never email a client until I reply yes.

Inspired by Farooq Shabbir: I Built a 24/7 Freelance Operations Agent with OpenClaw — It Runs My Business While I Sleep. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.

What can go wrong?

  • An always-on agent with mail access needs tight scopes.
  • Auto-drafted updates can miss context; skim every one.

Our take

Specific rules make the digest trustworthy: stale means something measurable. Approve-in-chat is the key safeguard for any always-on ops bot. What we would copy first is the definition of stale work: no review after a day, failing checks or an urgent label. Clear rules like that mean the morning digest only shows things that genuinely need you, so you keep reading it. Writing each job as its own skill file also helps, because a broken client update cannot take the PR digest down with it. The weak point is scope. An always-on agent that can read mail and post updates should start with read access, and every outgoing message should wait for your yes in Telegram, as Farooq set it up. Skim each drafted client update before approving; auto-written summaries miss context you carry in your head. If you run a team with shared inboxes and several owners, this design will need more than one approver.

Where the time goes back: Status reports and follow-up chasing become approvals in an app you already check.

FAQ

Did it need code?
No new code; the author used three skill files and one workflow on an existing gateway.
What changed for him?
He says about nine hours a week of switching and chasing became a morning yes or no.

Source and credit

Inspired by Farooq Shabbir. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.

Inspired by
I Built a 24/7 Freelance Operations Agent with OpenClaw — It Runs My Business While I Sleep
Creator
Farooq Shabbir
Published on
DEV Community
Original date
Apr 23, 2026
License
Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
Originally for
OpenClaw
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 Operations & Admin

All 203 Operations & Admin playbooks →

Related playbooks

Operations & AdminPrompt✓ AI dry run

Draft client documents from records with no guessed facts

Have an AI draft deal reviews, timelines, requirements docs and similar client-facing documents only from your CRM, estimates, contracts and call notes, with every line traceable, conflicts between sources flagged to you, unconfirmed items labeled as open, and a person signing off before anything goes out.

Credit: Antonio Perrone

Minutes
Operations & AdminPrompt✓ AI dry run

Hand off one offline task before you sign out

Before you go offline, get up to three useful task options with a concrete done artifact named for each, pick one, and wake up to a review-ready deliverable the agent prepared after your choice.

Credit: Scotty Beam (@ScottyBeamIO)

Minutes
Operations & AdminWorkflow✓ AI dry run

Move self-hosted agent cron jobs to cloud scheduled tasks

A clear plan for which scheduled agent jobs can leave your server, which need reshaping, and which can simply be deleted.

Credit: u/jonathanmalkin on r/ClaudeCode

An afternoon+
Operations & AdminWorkflow✓ AI dry run

Run parallel agents that debate into one sourced brief

Spin specialized research agents that gather sources, peer-review each other, and return one cited brief you can check — instead of a single unchecked summary.

Credit: tetsuoai (@tetsuoai)

Minutes
Operations & AdminWorkflow✓ AI dry run

Track coding-agent work as specs and GitHub issues

Turn a feature idea into a written spec, an epic and small GitHub issues that parallel agents can pick up and trace back.

Credit: aroussi on Hacker News

An afternoon+