If you keep asking JeremyAI for the same kind of help in separate chats, give that job its own worker. A worker is an assistant built for one recurring job, with its own instructions and its own chat history. You describe what you want in a sentence, JeremyAI sets it up, and you add a schedule if you want it to run on its own.
Watch the walkthrough
Can't see the video? Open the walkthrough here (4:49).
In the video, we build a sales call prep assistant, schedule it for 9 AM every day, and run it on a sample list of today's calls. No integrations are connected.
Why it matters
Every time you start a fresh chat for a repeat job, you re-explain what you want and how you want it. A worker remembers the job for you. You get the same useful format every time, with all past runs in one place, and short prompts are enough.
Build a worker when:
You ask for the same type of output every week (call prep, ad reviews, content ideas).
You re-explain the same context each time ("remember, my offer is...").
You want one place to see all the past work for that job.
For one-off questions, a normal chat is fine. Workers shine for repeat jobs.
Step 1: Create the worker by describing it
In the sidebar, open the Work section and click Workers.
Click + Create worker. The Create a new Worker dialog opens.
Choose Configure by Chat.
Under Describe your Worker, write what it should do. The video uses: An assistant that preps me for every sales call each morning: who they are, what they've bought, and what to ask.
Click Create Worker. JeremyAI builds the worker and gives it a name, like Sales Call Prep Assistant.
Prefer to set everything yourself? Choose Configure Manually instead.
Step 2: Connect tools now, or skip
When the worker is created, its card may recommend tools to connect. For a call prep worker, that's Slack and Gmail. Click Connect Integrations → to connect them now, or click Skip for now to start without them. You can connect them later if you want the worker to pull in data from those tools.
Without integrations, you give the worker its information directly, by pasting it in or attaching a file. That's what the video does.
Step 3: Add a schedule yourself
A new worker doesn't schedule itself. It runs when you chat with it. Open the worker's Triggers tab and you'll see No triggers configured. To have it run automatically:
Click + Create new and choose Scheduled Trigger. The steps run 1 Setup > 2 Schedule > 3 Execute.
Setup: under Worker Selection, pick your worker in the Worker field. Enter a Task Name (the video uses Morning call prep) and, if you like, a Description (Optional), such as "Prep me for today's sales calls every weekday morning". Click Next: Set Schedule & Timing.
Schedule: choose when it runs. The video picks Daily at 9 AM.
Execute: in the Worker Instructions box, write what it should do each time, like "Run my call prep for today." Need to change the timing? Click Back to Schedule.
Click Create Scheduled Task. You'll see Trigger created successfully, and the trigger appears in the list.
Not sure yet? Skip this step. You can add a schedule any time, and pause or delete it from the same tab.
Step 4: Run it and check the result
Click Start Chat with your worker selected.
Click +, then Add Files and Images, and attach your file. (The same menu also offers Integrations and Web Search.) The video uses a sample spreadsheet called Todays Sales Calls.csv with four made-up prospects.
Send: Run my call prep for today. My calls are in the attached file.
The worker returns call prep for every call on the list, with notes for each prospect, and can save it as a document you can open later.
Tip: a simple file works best. One row per call, with columns like time, name, company, what they need and any notes.
Write a great one-sentence description
A good description answers three things: what job, for whom or what, and what you want back.
Weak: "A sales helper."
Strong: "An assistant that preps me for every sales call each morning: who they are, what they've bought, and what to ask."
Descriptions to copy
All of these work without integrations, because you paste in or attach what they need.
Coaches and consultants
An assistant that turns call notes I paste in into a client recap email with action items and the next session date.
A content assistant that turns each coaching call summary I give it into 3 social posts in my voice.
Agencies
An assistant that reviews ad results I attach and writes a plain-English weekly summary with one recommendation.
A proposal assistant that drafts a one-page proposal from my discovery call notes.
Sales teams
An assistant that preps me for each of today's sales calls from a list I attach: who they are, what to focus on, and what to ask.
An objection coach that suggests answers to objections I paste in, using my offer and pricing.
E-commerce
An assistant that writes product descriptions and 3 ad hooks for each new product I describe.
A customer reply assistant that drafts friendly answers to customer emails I paste in.
Prompts to use with your worker
It already knows its job, so short prompts work:
Run my call prep for today. My calls are in the attached file.
Prep me for my 2pm call with Sarah, owner of a 3-location gym.
Here are today's call notes. Write the recap email.
Here are this week's ad numbers. Write the summary.
What good output looks like
A good worker gives you the same useful format every time, without you re-explaining. For call prep, that means a section per call with the details from your file and specific questions to ask. If you keep adding the same instructions to your prompts, put them in the worker's instructions instead.
Variations
Start from your Knowledge Base: upload your offer doc and FAQs first, so your worker answers with your real details.
Connect tools later: once it works with files, connect the tools it recommended so it can pull information in itself.
One worker per job: a call prep worker and a content worker work better than one worker that does everything.
Common mistakes and fixes
Description too vague: add what you want back (a list, an email, a summary) and who it's for.
Asking it to do everything: split it into separate workers for separate jobs.
Expecting it to run on its own: workers don't schedule themselves. Add a Scheduled Trigger in the worker's Triggers tab.
Generic answers: the worker only knows what you give it. Attach your file or paste in the details, or connect the tool that holds them.
Output format drifts: update the worker's instructions with the exact format you want.