6.1: When Humans Need to Review β
Welcome to Part 6! So far, you've built automations that run completely on their own. But what about when you need a human to check something before it happens?
In this section, you'll learn when and why to add human review to your workflowsβand how it actually makes your automations better, not slower.
6.1.1: The Power of Human + AI β
Here's the thing: Complete automation isn't always the goal.
π‘ Think of It Like This
Imagine a sous chef in a restaurant:
- The sous chef preps all the ingredients (fast, reliable)
- The head chef does final plating and taste-checks (expertise, judgment)
- Together, they serve amazing food quickly
That's what human-in-the-loop automation looks like!
AI handles the repetitive, time-consuming work. You focus on the decisions that really need human judgment.
You get:
- β‘ Speed: AI does 95% of the work instantly
- π‘οΈ Safety: You review the 5% that matters
- π― Quality: Best of both worlds
Let's see how this works in practice.
6.1.2: Why Human Review Matters β
Not convinced you need review? Let's look at three big reasons:
Why Human Review Matters
Combining automation with human oversight gives you the best of both worlds
AI Is Powerful, Not Perfect
AI can make mistakes, especially with edge cases, sarcasm, or unusual requests.
Example: Customer asks "Can you cancel my subscription... NOT!" - AI might miss the sarcasm.
High-Stakes Decisions Need Judgment
Some actions have serious consequences if done incorrectly.
Example: Processing refunds, legal agreements, or financial transactions.
Learn From Human Corrections
When humans review and correct AI outputs, the system improves over time.
Example: First 100 responses reviewed β patterns emerge β improve AI instructions.
The Golden Rule
Automate the repetitive work, keep humans for judgment calls.
Let AI handle 95% of routine tasks automatically, so you can focus your energy on the 5% that really needs your expertise.
π‘ The Bottom Line
AI is your super-powered assistant, not your replacement.
Use AI for speed and scale. Use humans for judgment and accountability.
6.1.3: When Should You Add Review? β
Not every automation needs human review. Here are the most common scenarios where you definitely should add it:
Common Review Points
When should you add human review to your workflows?
Before Sending Important Emails
Always reviewExamples:
- β’Customer-facing messages
- β’Marketing campaigns
- β’Legal or compliance emails
- β’Anything with your brand name on it
Before Making Purchases
Always reviewExamples:
- β’Processing payments
- β’Creating invoices
- β’Issuing refunds
- β’Any financial transaction
When AI Is Uncertain
Flag for reviewExamples:
- β’Low confidence score (<80%)
- β’Unusual customer requests
- β’Multiple possible answers
- β’Complex edge cases
First 100 Responses (Training Period)
Review initiallyExamples:
- β’New automations need tuning
- β’Learn what works and what doesn't
- β’Improve AI instructions
- β’Build confidence before full automation
π‘ Pro Tip: Start with more review, then gradually reduce as your automations prove reliable. You can always add it back if needed!
A Simple Rule of Thumb β
Ask yourself: "If this goes wrong, how bad would it be?"
- β Really bad? β Add review
- β A little embarrassing? β Add review for now, remove later
- β No big deal? β Let it run automatically
π‘ Start Careful, Get Faster
When you first build an automation, it's smart to review everything. After you see it working correctly 50-100 times, you can start removing review steps.
You can always add review back if something changes!
6.1.4: Types of Reviews You Can Add β
There are several ways humans can oversee automation. Pick the one that fits your needs:
Types of Reviews
Different ways humans can oversee automation
Approve/Reject
Simple yes or no decision
How It Works
AI generates output β You check a box β Action happens (or doesn't)
Best For
When AI output is usually good and needs quick approval
Example use cases: Email drafts, social media posts, data categorization
Edit Before Sending
AI provides a starting point, you polish it
How It Works
AI creates draft β You edit and improve β Edited version is used
Best For
When AI gets close but needs human touch
Example use cases: Customer responses, marketing copy, reports
Flag for Exception Handling
Mark unusual cases for special attention
How It Works
AI tries to handle β Flags if uncertain β Human handles exceptions
Best For
Complex workflows where most cases are routine
Example use cases: Support ticket routing, fraud detection, order validation
Provide Feedback
Rate AI performance to improve over time
How It Works
AI performs task β You rate quality β System learns from feedback
Best For
Training period or ongoing quality improvement
Example use cases: Response quality ratings, categorization accuracy, sentiment analysis
β¨ Mix and match: You can combine multiple review types in the same workflow. For example, use "Edit Before Sending" for important emails AND "Provide Feedback" to improve over time!
π‘ Which Type Should You Use?
Not sure which review type to start with?
- Need speed? β Approve/Reject (fastest)
- Need quality? β Edit Before Sending (most control)
- Complex workflow? β Flag for Exception Handling (scales best)
- Just learning? β Provide Feedback (improves over time)
You can always change or combine them later!
6.1.5: How Review Workflows Work β
Let's see the basic pattern you'll use in the next sections:
How Review Workflows Work
Automation stops at checkpoints for your approval
Speed of Automation
- β AI handles repetitive work instantly
- β Drafts ready in seconds
- β No manual data entry
Safety of Human Review
- β Catch mistakes before they go out
- β Add personal touch
- β Full control and accountability
π§ Real Example: Email Campaign
AI writes personalized emails for 100 leads (saves you hours) β You review and approve in 15 minutes β Only approved emails send β Perfect balance of speed and safety!
The Steps Explained β
Here's what happens in a typical review workflow:
1. AI Generates (Automatic)
- New row appears (from trigger, form, or manual entry)
- AI columns run automatically
- Draft or recommendation is created
- β No human needed yet
2. You Review (Manual)
- You open the table and see the draft
- Read through what AI generated
- Decide if it's good enough
- β This is where your judgment matters
3. You Approve (Manual)
- If it looks good, check an "Approved" box
- If it needs work, you can edit or skip it
- Only approved items move forward
- β You're in control
4. Action Happens (Automatic)
- Once approved, the final action runs
- Email sends, record creates, etc.
- Everything tracked in the table
- β Automation finishes the job
π‘ See How This Helps?
Imagine you have 50 customer emails to respond to:
Without AI:
- Write 50 emails from scratch = 3-4 hours
- β Exhausting and slow
With Full Automation:
- AI writes and sends 50 emails = 5 minutes
- β Fast but risky (what if AI makes mistakes?)
With Review Workflow:
- AI writes 50 emails = 5 minutes
- You review and approve = 20 minutes
- β Total time: 25 minutes with full control!
You just saved 3 hours while staying safe.
6.1.6: Real-World Example: Email Approval β
Let's make this concrete with a real scenario you might face:
The Scenario β
You run customer support and get 30-50 emails per day. You want to:
- β Respond quickly (customers expect fast replies)
- β Keep quality high (can't send bad responses)
- β Save time (writing 50 emails is exhausting)
The Solution: Review Workflow β
Here's what you build:
- 1. System automatically generates email draft
- 2. You review the draft and make any edits
- 3. You check an "Approved" checkbox when ready
- 4. Send Email column only runs if approved
- 5. You manually click "Send" button for final safety
- β’ Safe (human oversight)
- β’ Can edit before sending
- β’ Accountability tracked
- β’ Prevents mistakes
- β’ Slower (waits for human)
- β’ Requires attention
- β’ Need review process
- β’ Not fully automated
- Email arrives β Creates new row automatically
- AI reads email β Understands the question
- AI searches knowledge base β Finds the right answer
- AI drafts response β Creates professional reply
- STOP! You review β Check if the response is good
- You approve β Check the "Approved" box
- Email sends β Only if you approved it
The Results β
Before (Manual):
- 50 emails Γ 5 minutes each = 4+ hours per day
- π« Exhausting
After (Review Workflow):
- AI drafts 50 emails in 5 minutes
- You review 50 emails in 30 minutes
- β¨ Total: 35 minutes per day
You saved 3.5 hours every day while keeping full quality control!
π‘ And It Gets Better...
After a month of reviewing, you notice patterns:
- 90% of password reset emails: AI is perfect, no edits needed
- 80% of shipping questions: AI is great
- 50% of refund requests: AI needs help
You can now adjust:
- Let password resets send automatically (no review)
- Keep reviewing refund requests (needs judgment)
Your workflow gets smarter as you learn!
6.1.7: The Training Period Approach β
One of the smartest ways to use review is during a training period:
How It Works β
First 100 responses:
- β Review every single one
- β Note what works and what doesn't
- β Improve AI instructions
- β Build confidence
After 100 responses:
- β Remove review for types that work well
- β Keep review for edge cases
- β Automation gets faster and smarter
Why This Works β
Think of it like training a new employee:
Week 1-2: Check everything they do Week 3-4: Check important stuff only Month 2+: They work independently
Your AI assistant is the same way!
π‘ Pro Tip: Track Your Success Rate
Keep a simple tally:
- How many AI drafts do you approve unchanged?
- How many need small edits?
- How many need major changes?
If 90%+ are approved unchanged, you might not need review anymore!
What You've Learned β
Congratulations! You now understand:
- β Why human review matters (AI is powerful but not perfect)
- β When to add review (high-stakes decisions, training periods)
- β Types of review (approve/reject, edit, flag, feedback)
- β How review workflows work (AI generates β you approve β action happens)
- β The training period approach (start careful, get faster)
What's Next? β
In the next section, you'll get hands-on and actually build your first approval workflow. You'll see exactly how to:
- Add an approval checkbox
- Make actions wait for approval
- Set up notifications
- Test the complete flow
Ready to build something safe and powerful? Let's go!
Previous: 5.3 More Sub-Table ExamplesNext: 6.2 Setting Up Approval Workflows