Claude Dispatch and Remote Sessions

Chapter 1: What Dispatch Actually Is (And Why It Matters)

When you use Claude normally, it works like this: you type something, you wait, Claude responds. You're always there, watching. This is called working "synchronously" — both of you working at the same time.

Dispatch flips this around. You give Claude a task and walk away. Claude does the work on its own. When it's done, it gives you the results. This is called working "asynchronously" — Claude works while you do other things.

Why This Changes Everything

Think about tasks you do over and over:

• Summarizing your daily numbers from different tools
• Drafting social media posts from your content plan
• Reviewing new leads and rating which ones are worth your time
• Organizing customer feedback into neat reports

Every single one of these can be dispatched. You set it up once. Claude does it on command — or on a schedule, without you lifting a finger.

Think of Dispatch Like Delegating to a Great Assistant

• Task definition: What exactly needs to happen
• Context package: What information Claude needs to do the job
• Output format: What the finished result should look like
• Trigger: When it should run (on command? every morning? every Monday?)

Chapter 2: Setting Up Remote Sessions

A remote session is when Claude works on your behalf without you being there. Think of it like leaving instructions for a house sitter — they do the work while you're away.

How Remote Sessions Work

1. You define the task clearly
2. You give Claude all the context it needs (files, data, instructions)
3. You tell Claude what the output should look like
4. Claude runs the task
5. You come back and see the results

Setting Up Your First Remote Session

Step 1: Write clear instructions

Be specific. Instead of "look at my data," say:

"Read the sales data in the file sales-march-2026.csv. Calculate total revenue, average order value, and top 3 products by units sold. Output the results as a summary with bullet points."

Step 2: Provide the context

Give Claude everything it needs:

• Any files it should read
• Background about your business
• Any rules or preferences ("always round numbers to the nearest dollar")

Step 3: Define the output

Tell Claude exactly what format you want:

• "Give me a bulleted summary"
• "Create a Google Sheets-compatible CSV file"
• "Write me an email I can send to my team"

Step 4: Run it

Send the task. Go do something else. Come back for the results.

Chapter 3: Scheduled Tasks (Cron Automation)

"Cron" is a technical word that just means "running something on a schedule" — like an alarm clock for tasks. You can set Claude to do things at specific times.

Examples of Scheduled Tasks

Every morning at 8am:

"Check my Google Analytics data. Send me a summary of yesterday's website visitors, top pages, and any unusual changes."

Every Monday at 9am:

"Review all customer support tickets from last week. Categorize them by issue type. Tell me which issues came up most and if any need my personal attention."

Every Friday at 5pm:

"Summarize this week's social media performance. Tell me which posts did best and worst, and suggest 5 content ideas for next week."

First of every month:

"Review all my subscriptions and recurring charges. Flag any that increased in price or that I haven't used in 30+ days."

How to Set Up a Scheduled Task

1. Define the task — Write clear, specific instructions
2. Set the schedule — When should it run? (Daily? Weekly? Monthly?)
3. Define the output — Where should results go? (Email? File? Dashboard?)
4. Test it manually first — Run the task once by hand to make sure it works
5. Turn on the schedule — Set it and forget it

Tips for Good Scheduled Tasks

• Keep each task focused on ONE thing. Don't try to cram five tasks into one schedule.
• Include error instructions: "If the data file is missing, send me a notification instead of crashing."
• Review your automated tasks monthly to make sure they're still useful.

Chapter 4: Background Task Patterns

Here are proven patterns for tasks that run in the background.

Pattern 1: The Daily Briefing

What it does: Every morning, Claude gathers info from multiple sources and gives you a single summary.

Example: "Check my email for anything urgent, review my calendar for today, and pull my website stats from yesterday. Give me a 5-bullet morning briefing."

Pattern 2: The Content Factory

What it does: Claude creates content on a schedule.

Example: "Every Monday, take the top-performing blog post from last month and create 5 social media posts from it. Save them as a document I can review."

Pattern 3: The Lead Scorer

What it does: Claude reviews new signups or inquiries and tells you who to focus on.

Example: "Every day at noon, check the new contact form submissions. Rate each lead as hot, warm, or cold based on: business size, specific problem mentioned, and urgency language."

Pattern 4: The Report Builder

What it does: Claude creates regular reports from your data.

Example: "Every Friday, take this week's sales data and create a report showing: total revenue, compared to last week, top products, and any trends I should know about."

Pattern 5: The Cleanup Crew

What it does: Claude maintains your systems.

Example: "Every Sunday, review my Notion task list. Move any tasks that are overdue by more than 7 days to a 'Review' section. Add a note asking if I still need to do them."

Chapter 5: Monitoring and Error Handling

When things run automatically, you need to make sure they're working correctly.

The 3 Rules of Monitoring

Rule 1: Get notified when something fails.

Always include instructions like: "If this task fails for any reason, send me an alert with what went wrong."

Rule 2: Check the output regularly.

Even when things are "working," review the output once a week. Is it still accurate? Still useful? Still formatted correctly?

Rule 3: Have a fallback plan.

For critical tasks, have a backup: "If the primary data source is down, use the backup spreadsheet instead."

Common Error Types and How to Handle Them

| Error Type | What It Means | How to Handle |

|------------|--------------|---------------|

| Data not available | The file or source Claude needs isn't there | "If data is missing, use yesterday's data and flag it" |

| Output format wrong | The result doesn't look right | Review your instructions for clarity |

| Timeout | The task took too long | Break it into smaller tasks |

| Wrong results | The output is incorrect | Check your instructions and test data |

Chapter 6: Real-World Examples and Templates

Template 1: Weekly Business Report

"Read the following data sources: [list your sources]. Create a weekly business report with these sections:

1. Revenue this week vs. last week
2. New customers/subscribers
3. Top performing content
4. Key issues or problems
5. Recommended actions for next week

Format as a clean document with section headers and bullet points."

Template 2: Social Media Content Generator

"Based on my content calendar for this week (attached), create:

• 5 Instagram captions with hashtags
• 5 Twitter/X posts (under 280 characters each)
• 2 LinkedIn posts (professional tone, 150-200 words each)

Save each platform's content in a separate section."

Template 3: Customer Feedback Analyzer

"Read all customer feedback received this week (attached). Categorize each piece as: praise, complaint, feature request, or question. Count how many in each category. Highlight the top 3 issues by frequency. Suggest one action I should take based on the patterns."

Template 4: Competitor Watch

"Search for recent activity from these competitors: [list competitors]. Check their websites, social media, and any news mentions. Summarize: new products or features they launched, pricing changes, notable content they published, and any interesting moves. Give me a 1-page briefing."

Chapter 7: Advanced Patterns

Chaining (One Task Triggers Another)

You can set up tasks that trigger other tasks. Like dominoes:

1. Task 1: Pull this week's data and create a report
2. Task 2: Based on the report, draft an email summary to my team
3. Task 3: Based on the report, create next week's priorities list

Each task uses the output of the previous one. Claude handles the chain.

Conditional Logic (If This, Then That)

Include conditions in your instructions:

"Review the daily sales number. IF revenue is above $5,000, send me a congratulations message. IF revenue is below $1,000, send me an alert with possible reasons and suggested actions."

Multi-Source Aggregation

Pull information from multiple places and combine it:

"Combine data from my email (new inquiries), my website (traffic stats), and my social media (follower growth). Create a single dashboard summary."

Escalation Patterns

"Review customer support emails. Handle any simple questions directly. For complex issues or complaints, create a summary and flag them for my personal review."

Your Dispatch Checklist

• [ ] Understand the difference between regular chat and dispatch
• [ ] Set up your first remote session task
• [ ] Test it manually to make sure it works
• [ ] Set up at least one scheduled task
• [ ] Add error handling instructions to every task
• [ ] Review automated output weekly
• [ ] Try chaining two tasks together

The difference between people who are okay with AI and people who are great with AI isn't prompt quality. It's whether they've moved from "I ask Claude things" to "Claude works for me in the background." This guide gets you there.

Our AI Recommendation