Skip to content

Client Approval Chaser · Operations

Get client sign-off on time without chasing it by hand

Add a row when a proof goes out: the client gets a clear approval request, a firmer reminder after 2 business days, and your team gets a deadline-at-risk alert in Slack.

Available now $79 one-time · never renewsIncluded in Enterprise
Get this agent See how it works

Free account to start. Buying and running live need a paid plan.

  • Starts from an event in a connected app
  • 3 AI steps
  • A person approves before it acts
  • About 15 min to set up

Sound familiar?

The job, before and after this agent.

What it feels like today

  • “Clients sit on proofs and then blame us when the deadline slips.”
  • “Writing polite reminder emails takes up half my week.”
  • “Account managers find out a job is late when the print slot is already gone.”

What you get with the agent

  • A clear approval request for each item: what to check, how to approve and what the deadline means.
  • After 2 business days, the Status in your sheet is checked; approved or changes requested stops the chase.
  • Otherwise one firmer reminder goes out.
  • One business day later, still waiting means a deadline-at-risk alert in Slack naming the account manager.
  • Optional review so you approve every request and reminder first.

Before

The menu proof went out Monday. By Thursday you've sent two awkward nudges, the client hasn't looked, and the print slot is about to go to someone else.

After

The client got a clear request Monday and a firmer reminder Wednesday. Thursday morning your account manager saw the at-risk alert in Slack and called the client before the slot was lost.

How it works

The whole workflow, step by step.

Add a row to your approvals sheet when a proof or deliverable goes to a client. AI writes a clear approval request (what to check, how to approve, what the deadline means) and emails it. After 2 business days the agent checks the row's Status: if the client approved or asked for changes it stops, otherwise a firmer reminder goes out. One business day later, if the item is still waiting, your account team's Slack channel gets a “deadline at risk” alert naming the account manager. Review is off by default; switch it on to approve every request and its reminder first. Approval is recorded in the sheet, by you or by the client's form. It doesn't read email replies and sends one reminder at most.

  1. TriggerNew item sent for approval
  2. LogicCheck the needed-by date
  3. AI stepWrite the approval request
  4. LogicCheck before sending
  5. LogicApprove it first?
    • Send without review:Has an email?
    • Review first:Check the request
  6. Human approvalCheck the request
    • Approved:Has an email?
  7. LogicHas an email?
    • No email:No client email
    • Send:Email the approval request
  8. OutputNo client email
  9. OutputEmail the approval request
  10. LogicWait 2 business days
  11. App callCheck the row
  12. AI stepApproved yet?
  13. LogicStill waiting?
    • Dealt with:Dealt with
    • Still waiting:Send the firmer reminder
  14. OutputDealt with
  15. OutputSend the firmer reminder
  16. LogicWait 1 business day
  17. App callCheck the row again
  18. AI stepApproved now?
  19. LogicStill waiting?
    • Dealt with:Dealt with
    • Still waiting:Alert the account team
  20. OutputDealt with
  21. App callAlert the account team
  22. OutputAccount manager alerted

This is the workflow that opens in your workspace when you set the agent up. Every step can be edited.

  1. Step 1New item sent for approvalStarts a run for each row added to your approvals sheet: client, email, item, proof link, needed-by date and account manager.
  2. Step 2Check the needed-by dateIn code, not AI: reads the row's needed-by date in your time zone (its weekday, long form and the days left) and checks it is today or later. A past or unreadable date doesn't stop the run: the request then waits for the account manager.
  3. Step 3Write the approval requestAI writes a clear approval request: what to check, how to approve and what the deadline means — plus the firmer reminder, ready for later. The needed-by date and its weekday come from the date check.
  4. Step 4Check before sendingIn code: the needed-by date is today or later, there is a client email, and the request and the reminder have no placeholders left. Anything that fails waits for the account manager instead of going out at once.
  5. Step 5Approve it first?Review off (the default), nothing unclear and every code check passed: sent at once. Otherwise the account manager approves the request and its reminder first.
  6. Step 6Check the requestThe account manager checks the request (and the reminder) in Reviews, edits if needed and approves. Reject to send nothing.
  7. Step 7Has an email?Rows without a valid client email can't be sent; everything else is emailed (as approved, when review is on).
  8. Step 8No client emailThe row has no valid client email; nothing was sent.
  9. Step 9Email the approval requestEmails the client the request, with replies to the account team's inbox.
  10. Step 10Wait 2 business daysPauses for 2 business days (Monday–Friday).
  11. Step 11Check the rowFinds the item's row in the approvals sheet to read its Status.
  12. Step 12Approved yet?AI reads the row's status: approved or changes requested stops here; still waiting gets the firmer reminder.
  13. Step 13Still waiting?Approved or changes requested: stop. Still waiting: the firmer reminder goes out.
  14. Step 14Dealt withThe client approved or asked for changes; no reminder sent.
  15. Step 15Send the firmer reminderEmails the reminder written (and approved, when review is on) with the request.
  16. Step 16Wait 1 business dayPauses for 1 more business day.
  17. Step 17Check the row againFinds the item's row again to read its Status.
  18. Step 18Approved now?AI reads the status again and, if it's still waiting, writes the deadline-at-risk alert for the account manager.
  19. Step 19Still waiting?Approved or changes requested: stop. Still waiting: the account manager is alerted.
  20. Step 20Dealt withThe client approved or asked for changes after the reminder.
  21. Step 21Alert the account teamPosts “deadline at risk” to your account team's Slack channel, naming the account manager.
  22. Step 22Account manager alertedThe run history keeps the request, the reminder and the alert.

Example run

What goes in, and what comes out.

Example with fictional data

Comes in

New row: client Lantern Bistro (fictional), item “Spring menu proof v2, job 1042”, needed by Friday, account manager Jess.

The agent produces

Approval email with a check list (prices, spelling, allergen icons) and how to approve. Two business days later, Status still “Sent”: firmer reminder. Next day: Slack alert, deadline at risk, Jess named.

What you need

Everything it takes to run it.

About 15 minutes from purchase to live. A checklist above the canvas takes you through each step.

Plan

Included in Enterprise; on other paid plans it's $79 once. Agents run live on paid plans, from Basic ($39/mo).

Your AI key

Connect any of 14 AI providers on your own key. Your provider bills usage directly, at cost; we add no markup.

Apps

Checklist

  • A paid plan (agents run live on paid plans).
  • An AI provider key (Settings → AI Providers).
  • Google Sheets and Slack, connected in Settings → Integrations.
  • An approvals sheet with a unique Item column and a Status column you (or your approval form) update.

Setup, about 15 minutes

  1. Connect your AI provider. The AI steps run on your own key (OpenAI, Anthropic, Google and more). Add one in Settings → AI Providers.
  2. Connect Google Sheets. Connect the Google account that can open your approvals sheet (Settings → Integrations → Google Sheets).
  3. Connect Slack. Connect the Slack workspace your account team uses (Settings → Integrations → Slack).
  4. Add your approval details. Open “Write the approval request” and replace the placeholder with what clients check, how they approve and your sign-off.
  5. Pick the approvals sheet. Open the trigger, “Check the row” and “Check the row again” and pick the same account, spreadsheet and tab in each.
  6. Add your inbox and Slack channel. Open the two email steps and enter the Reply-to address, then “Alert the account team” and pick the account and channel.
  7. Test it with Dry Run. Press Dry Run: the agent runs on sample data with no messages sent and nothing written to your apps.
  8. Switch the trigger on. Open the trigger and press “Activate app trigger”. New rows are picked up on your plan's schedule interval.

Is it a fit?

Who it's for, and what it won't do.

Built for

  • Print shops and production studios
  • Design and marketing agencies
  • Account managers handling client proofs
  • Video and photo studios waiting on sign-off

What it doesn't do

  • It doesn't read email replies: approval is recorded in the sheet's Status, by you or your form.
  • It sends one reminder at most and doesn't change deadlines, the work or the proof.
  • It finds the row by its Item name, so duplicate item names can be confused.
  • Waits need Wait steps (migration 0062) in your workspace.

We list the limits up front so you can decide before you buy.

Price

$79 one-time

Per workspace. It never renews.

Available now
  • Included at no extra cost on Enterprise.
  • Buying and running it live need a paid plan, from Basic ($39/mo).
  • Dry Run costs nothing: simulated AI and app calls, nothing sent.
  • AI usage is billed by your own provider, at cost. No AI credits to buy from us.
Get this agent See how it works

One-time agent purchases aren't covered by the 30-day money-back guarantee. Refund policy

FAQ

Questions about Client Approval Chaser.

Does it read client email replies?

No. Approval is recorded in the sheet's Status, typed by you or written by your approval form. Keep item names unique so it finds the right row.

Will it pester my clients?

It sends one request and at most one reminder, and stops as soon as the Status shows approved or changes requested. Turn review on to approve each email first.

What do I need to set it up?

About 15 minutes: an approvals sheet in Google Sheets and Slack. To run it live you need a paid plan and your own AI provider key (OpenAI, Anthropic, Google and others), added in Settings. Dry Run on sample data is free, so you can see real output before you commit.

Is it worth the price?

It's a one-time purchase that never renews. One deadline saved, or one lost production slot avoided, covers it.

What should the approvals sheet look like?

One row per item: Client, Email, Item (unique, e.g. “Spring menu proof v2 — job 1042”), Proof link, Needed by, Account manager, Status. The checks find the row by its Item, so keep item names unique and the column named exactly “Item”.

How does it know the client approved?

From the Status cell: type “Approved” (or “Changes requested”) when the client replies, or have your approval form write it. It doesn't read email replies.

Can I approve each request first?

Yes. Change “REVIEW EVERY REQUEST: no” to yes in the request step; the reminder is approved at the same time.

Is this a subscription?

No. Client Approval Chaser is a one-time purchase of $79 per workspace and never renews. The Enterprise plan includes it at no extra cost. Running it live needs a paid plan (from Basic ($39/mo)), and your AI provider bills you directly for usage.

Can I test it before it touches real data?

Yes. Once it's set up in your workspace, Dry Run plays every step on sample data with simulated AI and app calls: nothing is sent and nothing in your apps changes. Switch the trigger on only when you're happy.

Put Client Approval Chaser to work.

Free account, no credit card. Your Agents page opens with Client Approval Chaser ready to buy and set up, then Dry Run it before it goes live.

Get this agent See how it works