How to Dispatch Claude Cowork From Your Phone to Build a Meeting Follow-Up Packet Before You Reach Your Desk

Warning: Phone dispatch extends Cowork access to a mobile surface. Be deliberate about what file, connector, and plugin access you have already granted on the desktop side.

Cowork requirements at a glance: Claude Desktop, a paid Claude plan (Pro/Max/Team/Enterprise), and Cowork research preview access.

If Claude Cowork is new to you

Start with the Claude Cowork explainer page in the site's Tools menu before you run this workflow. Cowork runs in Claude Desktop and can work on the local files you choose to share. For related examples, see the Claude Cowork tool hub and the Anthropic Workflows series. For phone-to-desktop dispatch, update both the desktop app and the mobile app first, and keep the desktop app open while your computer stays awake.

Problem and who this is for

You leave a meeting and already know what needs to happen next: a follow-up email, action list, decision recap, maybe a quick handoff note. The problem is timing. By the time you get back to your desk, context has faded and the next interruption has already started.

This workflow is for admins, executive assistants, coordinators, and operations leads who move between meetings and want a follow-up packet building while they walk back to their desk.

Prerequisites

• A Pro or Max Claude plan for phone-to-desktop dispatch.
• Claude Desktop open on your computer and your computer awake.
• The latest Claude mobile app on your phone.
• A place on your desktop where follow-up files should be created.

How to gather the source material

1. Right after the meeting, record a 30 to 90 second voice memo on your phone.
2. Keep the memo in the same order every time: decisions, action items, open questions, deadlines.
3. If the meeting used a standard template or recurring agenda, store that file in a known desktop folder Cowork can reach.
4. Create one small desktop text file called followup-template.txt with the exact sections you want in the final packet.
5. If names are hard to spell, say them slowly in the voice memo or text them into the dispatch thread afterward.

Numbered workflow steps

1) Open Dispatch and send the voice-based task from your phone

Use Cowork's Dispatch feature from mobile. Tell Claude where the relevant desktop template lives and what outputs you want back.

{
  "task": "Turn my post-meeting recap into a follow-up packet on my desktop",
  "input": {
    "voice_memo_summary": "PASTE OR DICTATE YOUR DECISIONS, ACTIONS, OPEN QUESTIONS, AND DEADLINES",
    "desktop_template_file": "FULL PATH TO followup-template.txt",
    "output_folder": "FULL PATH TO THE DESKTOP FOLLOW-UP FOLDER"
  },
  "rules": [
    "Use my desktop template structure.",
    "Create three outputs: follow-up email, action list, and decision recap.",
    "Keep unclear names or deadlines marked [CONFIRM].",
    "Do not send anything externally."
  ],
  "output_format": {
    "type": "meeting_followup_packet"
  }
}

2) Let Cowork build the packet on the desktop side

Because the same conversation persists across phone and desktop, you can add corrections from your phone while Cowork works.

3) Review the outputs when you sit down

Check names, dates, owners, and anything politically sensitive. Then paste or send the final email yourself.

Tool-specific instructions

Claude Cowork with mobile dispatch

• If you have never used it, read the Claude Cowork explainer page in the site's Tools menu first.
• Mobile dispatch requires the latest desktop app, the latest mobile app, an open desktop session, and a Pro or Max plan.
• Your phone-side task uses the files, connectors, and plugins already configured on the desktop side.
• Keep the desktop awake. If the app closes or the computer sleeps, the task stops.

Quality checks

1. The final packet includes the three promised outputs and uses the template structure you specified.
2. No email is sent automatically.
3. Names, deadlines, and owners are either correct or visibly marked for confirmation.
4. The follow-up packet is saved in the expected desktop folder.

Common failure modes and fixes

Nothing happens after you dispatch the task

Fix: confirm the desktop app is open, the computer is awake, and you are on a Pro or Max plan.

The packet uses the wrong structure

Fix: store a clearer followup-template.txt on the desktop and point Cowork to it explicitly.

The voice memo is too loose

Fix: use the same spoken order every time: decisions, actions, open questions, deadlines.

Sources Checked

• Anthropic Claude Help Center: Get started with Cowork (accessed 2026-03-23) https://support.claude.com/en/articles/13345190-get-started-with-cowork
• Anthropic Claude Help Center: Installing Claude Desktop (accessed 2026-03-23) https://support.claude.com/en/articles/10065433-installing-claude-desktop
• Anthropic Claude Help Center: Use Cowork safely (accessed 2026-03-23) https://support.claude.com/en/articles/13364135-use-cowork-safely
• Anthropic Claude Help Center: Assign tasks to Claude from anywhere in Cowork (accessed 2026-03-23) https://support.claude.com/en/articles/13947068-assign-tasks-to-claude-from-anywhere-in-cowork

Quarterly Refresh Flag

Review on 2026-06-21 to confirm any updates to Claude Skills, Cowork availability, mobile dispatch requirements, project behavior, and supported setup paths.