Claude Dispatch: 10 Things I'm Already Doing With It

I spent most of today using Claude Dispatch to handle tasks I'd normally have juggled across five different apps. Researching a customer before a meeting, setting a calendar event, drafting and sending an email, blocking time for a new project, even setting a 7am alarm. All from one conversation, on my phone, while I was out.

That's the thing about Dispatch. It doesn't feel like a tool. It feels like having someone sat next to you who actually knows how to use your computer.

What Dispatch Actually Is

Dispatch is an orchestration layer built on top of Claude. You give it a goal, and it figures out which tools, agents, and integrations to call. It can access your files, browse the web, send emails, talk to your calendar, interact with apps on your desktop, and chain all of that together in a single conversation.

The key difference from a regular AI assistant: it takes action. You don't get a list of steps to follow yourself. The work gets done. Here's where I've found it most useful.

The Top 10 Use Cases

1. Pre-meeting customer research. Before a call with a customer, I asked Dispatch to research their business, understand their objectives, and save a brief to a local folder. It searched the web, synthesised the key points, and had it ready in under two minutes. No tab-switching, no copy-pasting.

2. Calendar blocking. I described a project I wanted to work on. It created the calendar event, set the right time, added a description with context, and blocked the slot. Done in one message.

3. Email drafting and sending. I told it to email a research summary to an address. It drafted it, formatted it properly, opened Gmail via the browser, and sent it. I didn't touch the email client once.

4. File and folder management. It created project folders in the right places on my machine, named sensibly for the project at hand. No navigating Finder, no typing paths.

5. Local research saved to disk. I asked it to look up front door pricing in my area, format the findings, and save them as a markdown file in a specific folder. It did all three steps without me guiding it through each one.

6. System and environment queries. It checked which user was logged in on my machine and reported back. Sounds basic, but useful when you're working across multiple machines or helping someone else debug their setup remotely.

7. Alarm and reminder setting. I asked it to set a 7am alarm. It opened the Clock app, navigated to alarms, set the time, and saved it. I didn't touch anything.

8. Multi-step research to email pipelines. I asked it to research a topic and then immediately email the results to someone. It treated it as one job: research, write, send. Not two tasks. Not a handoff.

9. Project scaffolding. Starting a new project meant it set the calendar time, created the folder, named it properly, and set the context up so I could hit the ground running the next session.

10. Web research with clickable output. It searched for products, found supplier pages with images and links, formatted them into an HTML email, and sent it. The recipient got a proper-looking email they could click through and browse directly.

Why This Actually Matters

Most tools give you one thing. A calendar tool does calendars. An email client does email. A browser does browsing.

Dispatch does the join. It connects those things based on what you're trying to get done, not based on what any one tool is designed for.

The benefit isn't speed, though it is faster. The real benefit is cognitive load. You stop switching contexts. You stop holding half-finished tasks in your head. You describe what you want, and it sorts the rest.

I've found it most valuable for tasks that cross app boundaries. 'Research this, save it, and email it to someone' is three separate jobs in most workflows. In Dispatch, it's one message.

The Bit Worth Paying Attention To

It's running on your machine, with your accounts, your files, and your context. It's not a generic assistant. It knows your calendar, your email, your project folders, and can see your screen. That combination is what makes it actually useful, rather than just impressive in a demo.

The other thing: it asks before it acts on anything consequential. It doesn't just send emails or delete files without checking. That matters. The trust you put into a tool like this has to be earned, and the way Dispatch handles that is one of the reasons I've been comfortable using it for real tasks, not just experiments.

I'll keep writing up specific workflows as I find them. There's a lot more to explore here. If you want to build something like this for your team, or automate this kind of workflow, get in touch.