[For Non-Engineers Claude/ClaudeCode Series] A Claude Beginner Tried Using Cowork for the First Time to Automate Their "Routine Tasks" with /schedule

Introduction

This is Kawasaki from the Hokkaido Sales Division, East Japan Sales Headquarters.

I am in my 3rd month of cloud sales. While I had started casually using Claude's Chat feature,
with "Cowork" I knew the name but had no idea where to start.

When I actually tried it hands-on, I was able to automate "verification tasks I had been doing myself every time" more easily than I expected.

Who This Is For

• You've used Claude's Chat before, but haven't tried Cowork yet
• You have tasks where "you're just checking the same things every time, yet it still takes up a surprising amount of time"
• You want to know how to use the scheduling feature not just for "preventing missed items," but as a system to "eliminate manual input every time"

This article summarizes the steps I actually took for people like you.

What's the Difference Between Cowork and Chat?

Regular Claude chat is mainly used in a "ask once, get one answer" style. Cowork, on the other hand:

• Uses connectors (external tool integrations) like Gmail, Slack, and HubSpot
• Lets you delegate multi-step tasks all at once
• Allows you to switch your favorite tasks directly to scheduled execution

These are the key differences. The star of this article is precisely that third point — "switching to scheduled execution."
When thinking about what kind of tasks I do on a regular basis for scheduled execution, I first thought about checking my morning emails and wanting to avoid missing anything, so I decided to entrust this work to Cowork.

Step 1: First, Try It Through Regular Conversation

Rather than jumping straight to scheduling, start by giving instructions through conversation as usual and verify that the results are as expected.

What I tried this time was a task to "review Slack and Gmail from the past 3 days and organize anything with missing replies or follow-ups by urgency level."

Please check Slack and Gmail from the past 3 days and organize items requiring attention by urgency level.

[High] Action Required: Items with assigned responsibilities or approaching deadlines
[Medium] Consider Replying/Following Up: Replies are needed but not urgent
[Low] When You Have Time: Casual replies or information-sharing only

For each item, please include a 1–2 sentence summary after a heading in the format:
"[Source (HubSpot/Gmail/Slack DM)] Subject (Date)"

When I submitted this to Cowork with the Gmail and Slack connectors connected, it actually pulled together unanswered emails and DMs organized by urgency level.

[High] Action Required

[Gmail] Re: [Inquiry About Next Meeting] ◯◯ Corporation (08/04)
A reply from ◯◯ expressing interest in exchanging opinions about introducing the "◯◯ Service" has been received,
with proposed date candidates around 8/17.

[Gmail] Invitation: Proposal for Generative AI Utilization at ◯◯ University (dated 08/06 · held 08/10)
Confirmed Google Meet invitation. Content preparation is required.

[Medium] Consider Replying/Following Up

[Gmail] Invitation: [1-on-1] ◯◯ & ◯◯ (dated 08/03 · held 08/07)
Friday 4:30 PM 1-on-1 is confirmed. It may be worth checking if there are any items to prepare in advance.

[Low] When You Have Time

[Slack DM] ◯◯ (08/02 10:15)
A reply to "Let's grab lunch sometime!" is pending. A casual reply is sufficient.

[Gmail] ◯◯ Tool Maintenance Notice (08/03)
System maintenance scheduled for Sunday 8/10 from 2:00–4:00 AM. No reply needed, but
please note it may affect scheduling if relevant.

※ Dummy information has been used for this example.

Step 2: If You're Satisfied With the Results, Lock It In With /schedule

■ What Are "Commands" in the First Place?

When you type a word starting with / in the Cowork chat field, there is a mechanism that lets you ask Claude to perform specific actions.
These are called "slash commands."

Unlike making a request in regular text, sending a fixed keyword starting with / conveys to Claude that "this is not a regular question, but an instruction to invoke a specific feature." /schedule is one of these commands, and knowing it lets you quickly call up scheduled execution settings.

■ What Kind of Command Is /schedule?

/schedule is a command that can be used in any conversation within Cowork. When entered, it converts the current conversation content (i.e., the prompts and exchanges up to that point) directly into a scheduled recurring task.

When you type it, Claude will ask you — with selectable options — about:

• Execution frequency (hourly, daily, weekly, weekdays only, or manual)
• Whether to confirm before executing or run automatically (approval mode)

Just tap to answer and the setup is complete. Even if you don't remember the command, speaking naturally with something like "I want you to do this every morning at 7" will trigger the same feature.

After creation, you can access it anytime from "Scheduled" in the sidebar — use the pencil icon to edit instructions, the toggle to pause, and "Run Now" to do a test run. If you want to fine-tune the frequency or wording later, you can do it directly from there.

Once you're satisfied with the output, type /schedule within the same conversation.

/schedule Run every morning at 7

Then, Claude will ask you with multiple-choice options about:

1. Execution frequency (hourly, daily, weekly, weekdays only, or manual)
2. Whether to confirm before executing or run automatically (approval mode)

Just tap to answer and your scheduled task is complete.
What I found particularly helpful was that there's no need to copy and paste the prompt to a different screen. Since "what you tested" becomes "the live operation as-is," there are no steps to get confused by.

Even if you speak naturally — "I want you to do this every morning at 7" — it activates the same way, so you don't need to memorize the command.

Step 3: Understand the Difference in Execution Environments

There are 2 patterns for scheduled tasks.

Tasks like today's "unanswered message check" that are completed entirely with connectors run in the cloud, so even if your PC is closed, the results will be ready in the morning. It's a small but genuinely appreciated point that you're unlikely to run into the failure scenario of "it didn't run because my PC was off."

Examples Applicable Across Job Roles

Even outside of sales, I think every job role has "regular verification and review tasks" that consistently come up. Here are a few examples.

• General Affairs / Back Office: Every morning, organize unanswered questions that have piled up in the internal inquiry channel by category
• HR: Weekly, identify candidates whose application responses have stalled
• Engineers: Every morning, prepare a draft retrospective memo based on the logs of incidents and issues closed the previous day
• Marketing: Weekly, compile mentions and reactions related to your company's products and campaigns

If you have tasks where "you open a tool and check it yourself every time," those are candidates for Cowork scheduled tasks.

Summary

• Cowork enables a seamless flow of "try it in chat → lock it in as-is if it works well"
• Just type /schedule mid-conversation and it converts the current prompt into a recurring scheduled task
• Tasks completed entirely with connectors run in the cloud, so you don't need to worry about your PC's status
• It's applicable to any job role — not just sales — as long as there are "recurring verification tasks"

I think many people use Claude's chat but feel like they "don't know where to start" with Cowork. The recommended approach is to first pick one verification task you do daily or weekly, try it out in conversation, and then /schedule it.
As an added benefit, you no longer need to keep "Did I handle that thing?" in the back of your mind,
and since results are delivered via Slack notifications, you can check them during your commute, changing how you prepare in the morning.
Please give it a try if you haven't used it yet.