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

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, the phone is the task assignment surface. The desktop app and local files are the execution environment. Update both the desktop app and the mobile app first, keep the desktop app open, and keep your computer awake while Claude works.

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.

Why Cowork fits this workflow

Cowork fits this workflow because the useful materials often live on your desktop: a follow-up template, a recurring output folder, prior packets, and meeting-specific context files. Your phone captures the meeting context while it is fresh, but the desktop project gives Claude the structure and file location for the finished packet.

Use Cowork when you want the same packet shape every time: follow-up email draft, action list, decision recap, and open questions. The phone dispatch starts the task. Cowork does the work on the desktop side, using the scoped project or folder you prepared.

Why not normal Claude chat?

Normal Claude chat can draft a follow-up if you paste the meeting notes into the conversation. That is fine for a one-off email.

Cowork is stronger when the follow-up process depends on a prepared desktop workspace. Normal chat cannot by itself use the already prepared local folder, desktop template, output rules, and recurring project instructions in the same way. Cowork keeps the template, meeting notes, archive, and packet outputs together so repeat meetings do not start from a blank prompt.

Prerequisites

• Claude Desktop with Cowork available on a paid Claude plan.
• A Pro or Max Claude plan if you are assigning the task from your phone through Dispatch.
• Claude Desktop open on your computer and your computer awake.
• The latest Claude mobile app on your phone if using phone assignment.
• An active internet connection on both devices for phone assignment.
• A clearly scoped desktop follow-up project or folder.

Set up the desktop project before you dispatch from phone

Create a reusable Cowork project or desktop folder before you try to use mobile dispatch. The phone prompt should be short because the desktop project already contains the structure.

Use this folder setup:

meeting-notes/
templates/
follow-up-packets/
archive/
followup-template.txt
meeting-context.txt

Use meeting-notes for dictated recaps, pasted voice memo summaries, or notes you want Cowork to inspect. Use templates for recurring agenda or follow-up examples. Use follow-up-packets for finished drafts. Use archive for older notes and packets.

Put the packet structure in followup-template.txt. Include the headings you want every time, such as follow-up email draft, action list, decision recap, open questions, and confirmation-needed items. Use meeting-context.txt for standing context, such as audience, tone, recurring attendees, naming preferences, and communication boundaries.

Add project instructions so the desktop side knows what to do before you dispatch from phone:

{
  "project_name": "Meeting Follow-Up Packet",
  "project_purpose": "Use Claude Cowork to turn a phone-captured meeting recap into a desktop follow-up packet with an email draft, action list, decision recap, and open questions.",
  "project_instructions": [
    "Use the newest meeting note or dictated recap as the primary source.",
    "Use followup-template.txt for the packet structure.",
    "Create three outputs: follow-up email draft, action list, and decision recap.",
    "Keep unclear names, owners, deadlines, or decisions marked [CONFIRM].",
    "Do not send emails or messages automatically.",
    "Save outputs only in follow-up-packets.",
    "Ask for review before finalizing wording that will be sent externally."
  ],
  "file_naming": "meeting-follow-up-packet-yyyy-mm-dd-topic"
}

This setup separates the two jobs. Your phone captures and assigns the task. The desktop project supplies the template, folder boundaries, and output rules.

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 templates or summarize it in meeting-context.txt.
4. Keep followup-template.txt current 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.
6. Keep the dispatch prompt specific to the meeting. Do not point Cowork at broad personal or company folders.

Numbered workflow steps

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

Use Cowork's Dispatch feature from mobile if your plan and app setup support it. Anthropic's current help lists phone assignment for Pro and Max plans. Tell Claude which desktop project to use 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_project": "Meeting Follow-Up Packet",
    "desktop_template_file": "followup-template.txt",
    "output_folder": "follow-up-packets"
  },
  "rules": [
    "Use the existing Meeting Follow-Up Packet project instructions.",
    "Use my desktop template structure.",
    "Create three outputs: follow-up email, action list, and decision recap.",
    "Keep unclear names, owners, deadlines, or decisions 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 conversation persists across phone and desktop, you can add corrections from your phone while Cowork works. The work still runs through the desktop environment, using the local files and access you have already configured.

If the computer sleeps, the desktop app closes, or the desktop loses connection, the task cannot continue. Treat the phone as the remote instruction surface, not the place where the local file work happens.

3) Review the outputs when you sit down

Check names, dates, owners, deadlines, decisions, and anything politically sensitive. Confirm that the packet used the right template and saved to the expected folder. Then paste or send the final email yourself.

Future meeting runs

For recurring meetings, reuse the same desktop project and keep the mobile prompt short. After the meeting, dictate a quick voice memo and send:

Build a meeting follow-up packet from this voice memo summary.

For a stricter reusable prompt, use this:

{
  "task": "Build a meeting follow-up packet from this voice memo summary.",
  "rules": [
    "Use the existing Meeting Follow-Up Packet project instructions.",
    "Use the desktop followup-template.txt file.",
    "Create the email draft, action list, and decision recap.",
    "Mark anything uncertain as [CONFIRM].",
    "Do not send anything."
  ]
}

The project instructions do most of the repeat work: where to save files, what outputs to create, what template to use, and what must be reviewed. Your phone prompt only needs the fresh meeting facts.

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, active internet on both devices, an open desktop session, an awake computer, 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.
• Do not use broad folder access for meeting follow-ups. Scope the project to the packet template, meeting notes, and output folder.
• Do not ask Claude to send emails or messages automatically. Draft first, review manually, then send yourself.

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.
5. Sensitive wording, internal politics, and external-facing commitments are reviewed before sending.
6. The desktop app stayed open and the computer stayed awake until the task finished.

Common failure modes and fixes

Nothing happens after you dispatch the task

Fix: confirm the desktop app is open, the computer is awake, both devices have internet, the mobile app is current, and you are on a Pro or Max plan for phone assignment.

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.

The packet includes sensitive wording

Fix: add review rules to the project instructions and keep sensitive political language marked [CONFIRM]. Draft only. Send the final email yourself after review.