Build a Claude Dispatch workflow on your mobile device.

Your workflow, your rules.

Quick summary : In Lesson 7, we learned about troubleshooting—diagnostic diagrams, breakdown strategies, and best practices to improve reliability from 50% to over 80% . Now it's time to combine it all into something you'll actually use every day.

 

In the past seven lessons, you've learned what Dispatch is, how to set it up, what it can access, how to build workflows for developers and businesses, why the security model works, and how to troubleshoot problems.

This final exercise is not theoretical. You will design a workflow for YOUR work, based on YOUR files, using YOUR Global Instructions. And you will test it before the end of this lesson.

Step 1: Identify those "off-desk" moments.

When are you not near your Mac but still want to get work done? Here are 5 top scenarios:

For example:

• Commuting to work (30 minutes each way, 5 days a week)
• Lunch meetings (3 times a week)
• Children's activities (wait 1-2 hours)
• Business trip date (airport, hotel)
• Walking between buildings at work.

For each situation, please record:

• How long were you away from the computer?
• What kinds of tasks tend to pile up during this time?
• What would you do if you could access your Mac?

This provides you with the raw materials to build your workflow.

Step 2: Design the workflow

Choose a scenario where Dispatch will save you the most time. Now, design a workflow for that scenario.

 

Template workflow:

## [Tên workflow của bạn] ### Khi nào tôi sử dụng cái này [Tình huống — ví dụ: "Trong chuyến đi làm buổi sáng 30 phút của tôi"] ### Danh sách kiểm tra trước khi khởi hành - [ ] Máy Mac đã được cắm điện và ứng dụng Caffeineate đang chạy - [ ] Ứng dụng Cowork đã được mở và cập nhật - [ ] Ứng dụng Dispatch đã được ghép nối và kiểm tra - [ ] Thông báo trên điện thoại đã được bật cho Claude ### Trình tự tác vụ Bước 1: [Đọc thao tác để hiểu ngữ cảnh] Prompt: "[prompt chính xác]" Kết quả mong đợi: [những gì bạn sẽ thấy] Nếu thất bại: [kết quả dự phòng] Bước 2: [Tác vụ phân tích hoặc tạo] Prompt: "[prompt chính xác]" Kết quả mong đợi: [những gì bạn sẽ thấy] Nếu thất bại: [kết quả dự phòng] Bước 3: [Lưu file hoặc hành động] Prompt: "[prompt chính xác]" Kết quả mong đợi: [những gì bạn sẽ thấy] Nếu thất bại: [Phương án dự phòng] ### Xác minh Cách tôi xác nhận workflow đã hoàn thành thành công: [bước xác minh của bạn] ### Thời gian tiết kiệm Không sử dụng Dispatch: [X phút tại bàn làm việc] Sử dụng Dispatch: [Y phút trên điện thoại, bao gồm cả các lần thử lại] Tiết kiệm ròng: [X - Y phút mỗi lần] Tần suất: [bao nhiêu lần mỗi tuần] Tiết kiệm hàng tuần: [tổng cộng]

Step 3: Example of a real-world workflow

Here are three examples to inspire your process. Adapt them, don't copy them – the workflow should be tailored to your actual work.

Example 1: Code review during a morning commute.

Time : 30-minute train ride, Monday to Friday

Sequence :

Step 1: "Show me any PRs that have been opened since yesterday in ~/projects/main-app. List the author, title, and files that have changed."

Step 2: (For each PR to be reviewed) "Read the changes in [specific file] from PR #[number]. Are there any security issues, missing error handling, or rule violations?"

Step 3: "Save my review note to ~/Documents/reviews/pr-[number]-[date].md"

Step 4: (Return to your desk) Post your review to GitHub using the saved note.

 

Time saved : 20 minutes of desk time is converted into travel time. Total: 20 minutes/day x 5 days = 100 minutes/week saved.

Example 2: Managing sales while on a business trip

Timing : Hotel rooms during business trips (2-3 times per month)

Sequence :

Step 1: "Read ~/Documents/sales/pipeline.csv and show me the top 10 deals by value. Which deals should I watch this week?"

Step 2: "For each transaction due this week, check ~/Documents/sales/notes/ to see the latest notes file. Summarize what we've accomplished with each customer."

Step 3: "Draft follow-up emails for [customer 1] and [customer 2] based on the notes. Focus on the next steps and timeline. Save to ~/Documents/drafts/"

Step 4: "Read ~/Documents/reports/regional-q1.csv and give me three bullet points about our best performing region for tomorrow's team meeting."

Time saved : 45 minutes of preparation can be done from your hotel room instead of rushing to the office the next morning.

Example 3: The content creator's idea machine

Time : Waiting rooms, queuing for coffee, between meetings - whenever inspiration strikes.

Sequence :

Step 1 (note): "Add to ~/Documents/content/ideas.md: [ideas and context]"

Step 2 (when you have more time): "Read ~/Documents/content/ideas.md and choose the 3 most promising ideas. For each idea, sketch a short paragraph. Save it to ~/Documents/content/outlines/[date].md"

Step 3 (next): Develop the sketches into a complete draft.

Time saved : Ideas that might otherwise be forgotten are instantly captured. A 5-minute sketch saves 15 minutes of thinking, "What was that idea?".

Step 4: Review your workflow

Quick check : Before testing, review your workflow and count the steps. Is each step a single, focused operation? Is each write operation followed by a verification step? If not, revise it now. These two principles predict success more than anything else.

Don't just design the workflow—test it. Right now, if you can.

1. Run your entire workflow from your phone.
2. Record what works on the first try.
3. Record what failed and why.
4. Adjust your prompts based on what you learn.
5. Run again

The first test will reveal problems you didn't anticipate. That's the key point. A workflow that's been tested once is 10 times more reliable than one that only exists on paper.

 

Test checklist:

Step 5: Record and Repeat

Save your workflow somewhere you can access it from your phone:

• Notes app
• A document is pinned.
• A bookmark to a file on your Mac (accessed via Dispatch!).

Include:

• Precise prompts (so you can copy and paste, no need to retype on the small keyboard)
• Expected results for each step
• Contingency plan in case of failure
• Checklist before leaving

Then, repeat. Each time you use the workflow, record it:

• Which step was successful?
• Which step failed?
• Execution time
• Is saving time really effective?

After a week of use, you will have real-world data to optimize.

Measure actual ROI

Be honest about whether Dispatch saved you time. Here's how it's calculated:

Time saved per use = (Time spent working directly on the same task) - (Time spent on automated processing, including errors and retries)

If a task takes 10 minutes to complete directly but takes 8 minutes using Dispatch, and the error rate is 30% (an average of an additional 4 minutes of retry):

Direct processing time = 8 + (0.3 x 4) = 9.2 minutes

Savings: 0.8 minutes. Almost negligible for that specific task.

But if a task that would normally take 30 minutes of manual work takes only 10 minutes using Dispatch with a 90% success rate:

Direct processing time = 10 + (0.1 x 3) = 10.3 minutes

Savings: 19.7 minutes. That's worth it.

The greatest return on investment (ROI) comes from tasks that:

• The desktop version is time-consuming.
• The version on Dispatch is much shorter (the tasks require a lot of reading).
• High success rate (simple tasks, focused on a single goal)

What Dispatch doesn't replace

After 7 lessons, you know Dispatch's strengths. But let's clarify what it doesn't replace:

• Intensive work sessions - Dispatch is for quick, focused tasks. Long programming sessions lasting several hours require you at your desk.
• Complex debugging - Logs can be read remotely. Step-by-step debugging is not possible.
• Final editing - Drafted on phone, finalized at the desk.
• Tasks requiring a full graphical user interface—design tools, complex spreadsheet editing, presentation building—these things need your screen.
• Anything that requires 100% reliability – If the task absolutely must succeed, do it at your desk.

Dispatch is your "pocket assistant" for 30% of your work that is quick, focused, and doesn't require your entire workstation. That 30% is equivalent to a certain number of hours per week.

Exercise: Complete the workflow on mobile devices.

1. Complete the workflow template from step 2 with your actual tasks and prompts.
2. Check the workflow (step 4)
3. Calculate the expected time savings.
4. Save the workflow to your phone for daily reference.
5. Use it for a week and monitor the actual results.

After a week, you'll know exactly which of Dispatch's workflows are worth keeping and which need adjustment.

Key points to remember

• The workflow design is based on real-world scenarios when you're "off your desk"—not hypothetical situations.
• Using template workflows: Scenarios, pre-departure checklists, task sequences with contingency plans, verification, and time savings.
• Test every workflow before using it - the first test always yields surprises.
• Measuring actual ROI includes error rates and retry times – be honest about whether Dispatch actually saved you time.
• Weekly improvements - your first workflow design won't be the best.
• Dispatch replaces 30% of your work quickly and efficiently – not intensive work sessions or complex tasks.
• The skills from this course (analysis, data-driven design, full path, verification) apply to every Dispatch task you will send.

 

What Dispatch needs to do next: Anthropic launched Computer Use in late March 2026 - Claude can now control your mouse, browser, and applications directly on your desktop (macOS only, research preview). Combined with Dispatch, this means you can send task messages from your phone, and Claude not only works with your files but also operates your actual computer. Fill out spreadsheets, navigate web applications, click through forms. The Dispatch skills you learned in this course (analysis, verification, contingency planning) also apply directly to the Computer Use workflow.

• Question 1:

  How do you measure whether your Dispatch workflow is actually saving time?

  • A. Count the number of tasks you submit each day – a common mistake leading to suboptimal results.
  • B. Track the time spent on tasks sent via Dispatch compared to the time you actually spend on those tasks at your desk, including time lost due to errors and rework.
  • C. Ask your boss if they were impressed.
  • D. Check your internet speed

  EXPLAIN:

  The true return on investment (ROI) means tracking the total time: the time it takes to complete a task via Dispatch, plus any errors and rework, compared to performing the same task at your desk. If a 5-minute task at your desk only takes 2 minutes via Dispatch but fails 30% of the time (plus 3 minutes for rework), then your actual time savings are less than they appear. Be honest about which workflows are truly beneficial.

• Question 2:

  Why should your mobile workflow documentation include both 'success' and 'failure' scenarios?

  • A. Because Dispatch has a significant error rate, knowing about backup plans in advance will help avoid wasted time and frustration when a mission fails.
  • B. To make the document longer
  • C. Because compliance with regulations requires it.
  • D. Because the actual error scenarios never happen – which would be great if true, but the evidence suggests a more complex story.

  EXPLAIN:

  Given Dispatch's current reliability (~50% for complex missions, ~80-90% for simple ones), errors are not the exception—they are predictable events. Documenting your contingency plan means that when a mission fails, you won't waste five minutes figuring out what to do. You already know: try again, simplify, or wait for the person in charge.

• Question 3:

  What makes mobile workflows 'delegation-friendly'?

  • A. It uses as many connectors as possible.
  • B. It requires complex multi-step operations – confusing correlation and cause here leads to ineffective strategies.
  • C. It includes tasks focused on a single thing, primarily reading data, with clear success criteria and built-in backup plans in case the task fails.
  • D. It can only be done from a phone.

  EXPLAIN:

  Workflows that are user-friendly utilize tasks that are focused on a single activity (doing only one thing at a time), prioritize data-reading operations (high reliability), have clear success criteria (you can verify the results), and include contingency plans in case of task failure. These design principles help increase your success rate from around 50% to 80-90%.

Submit your work

 

Training results

You have completed 0 questions.

-- / --

Review the lesson