OpenAI's Help Center report on getting started with your dot says a Dot is an always-on agent for Pro subscribers and Business Premium workspaces. ChatGPT's dots guide says you give it a goal and it keeps going between conversations. I do not run a marketing team that way, because a goal with no named owner is how a draft leaves on a Friday. I run two desks instead. A recurring assignment only holds when the connected account, the refusal, and the responsible reader are already inside the first memo.
ChatGPT Work and Dots for a marketing team is the ultimate guide I wish I could hand a lead on day one. Work is where you finish one memo with the real account in the thread. A Dot is the job that drafts that memo again next Monday. If you only have Work, someone on the team retypes the brief every week and the numbers get smoother and less true. If you only have a Dot, nobody ever designed the first memo you would actually sign. Design once, then repeat. Send and spend stay with a person on both desks.
This is not a product-versus-product argument. I am not asking you to pick a winner. I am asking you to stop putting the whole department inside one thread.
TL;DR
- ChatGPT Work and Dots for a marketing team is two desks, not one bot.
- Work finishes the first memo. The Dot repeats the draft.
- Design once, then repeat. Do not redesign the job every Monday.
- Send, publish, and spend stay with a named person.
- Prompts, the job list, and skills are the next pages, not this one.
- I would rather a draft sit unread than leave on a Friday.
Why ChatGPT Work and Dots for a marketing team is two desks
I have watched a growth marketer do this in one afternoon. They open Work, pull a real Search Console table, and write a refresh brief they would edit. Then they close the laptop. Next Monday they open a blank chat and ask for "the SEO plan" again, and the numbers are smoother and fake. Work did its job. The team had no second desk to keep it.
A Dot is that second desk. It does not invent the job. It holds the job you already liked. ChatGPT Work and Dots for a marketing team fails when the Dot is asked to be the strategist and the publisher and the media buyer. It succeeds when Work is the place you decide the artifact, and the Dot is the place that artifact shows up again with the same source and the same refusal.
OpenAI's own DevDay demo is the picture I use. A Dot drafts a Slack reply and waits. A person is still in the thread. Marketing is the same picture with a different object: a title, a sequence file, an ads note. The video is below. Watch who is still allowed to say yes.
The Work versus Chat post is about the mode inside one session. Read it if your team is still pasting CSVs into Chat. Do not read it as the team design. The team design is here. Marketing plugins for ChatGPT Work is how the first memo gets live data. Without that, Work finishes a story. With it, Work finishes a brief you can hand to a Dot.
I keep the first memo small on purpose. One URL. One segment. One proposed test. A marketing team that designs a "full growth system" in Work on Thursday will not recognize the draft the Dot brings back. The Dot is faithful to a sloppy assignment. That is not a bug I want to paper over.
How ChatGPT Work and Dots for a marketing team split a week
Thursday or Friday is Work. You sit with the person who owns the channel. You pull the source. You write the brief until you would send it to yourself. You name the refusal out loud: the Dot may draft, and it may not publish, send, or spend. Then you stop. You do not schedule five more jobs because the first memo felt good.
Monday is the Dot. It runs the same job. You read the draft against the source, not against your mood. You accept, edit, or kill it. You do not open Work again unless the job itself is wrong. Reopening Work every Monday means you never left the first desk.
| Desk | When | What finishes | What waits |
|---|---|---|---|
| Work | The day you design | One memo with a real source | The next Monday |
| Dot | The morning it recurs | The same draft, same source | Your edit |
| A person | After the draft | Publish, send, or spend | Nothing automatic |
The table is the week. ChatGPT Work and Dots for a marketing team does not need a new meeting. It needs the meeting you already have to start from a draft instead of a blank prompt.
A Monday for ChatGPT Work and Dots for a marketing team
Here is the handoff I would write on a card. "Work, Friday: read Search Console for this property and draft a refresh brief for one URL. Dot, Monday: repeat that brief. Do not change the URL. Alex reads it before anyone publishes." That card is the operating system. If you cannot name Alex, you do not have a team design. You have a tool.
The how to use page is the Monday in more detail. The job list is how you pick the second card after two Mondays have been worth editing. I do not want this guide to become those pages. I want a lead to see the split once, then go to the page that matches the desk they are standing at.
A growth marketer who skips Work and writes the Dot job from a template will get a confident brief with no owner. Design once, then repeat only works when the first design was one you would sign. If you would not sign the Friday memo, do not automate it. Kill it in Work, where it is still one document and not a habit.
What the team still has to do by hand
Both desks stop at the same wall. I will not move that wall because a team is busy. The Dot drafts the sequence. A person sends it. Work can queue an ads note. A person approves the spend. A strong content draft is still not a URL in production. Custom Rules are where that wait is stored, so a sharp prompt cannot talk the Dot into "just this once."
| Ask from the team | Desk that prepares it | Who still acts |
|---|---|---|
| Refresh one URL | Work designs, Dot repeats | The person who publishes |
| A sequence file | Dot, after the first sequence was one you would send | The person who sends |
| An ads change | Work or Dot reads the account | The person who spends |
| A Slack update | Dot drafts, as in the DevDay clip | The person who posts |
If your team wants the side effect to happen while everyone is asleep, that is a different system, and it still should wait for a named approval. ChatGPT Work and Dots for a marketing team is not that system. Pretending it is how a bid moves or a sequence leaves on a Friday.
Agencies do this per client. One Work thread and one Dot per brand. I have seen a shared login move a draft from the right brand to the wrong one faster than anyone notices. The split does not fix a shared login. Your access rules do.
Where this guide stops and the other pages start
Three pages pick up the work this one names and does not finish.
The setup walkthrough is the install. Send a teammate there if they have never created a Dot. Do not send them this guide for the clicks.
The prompts library is the wording. The skills list is the instruction you keep after the wording worked once. A prompt is one ask in Work. A skill is what the Dot calls when the ask becomes a habit. I want that promotion to be a decision, not an accident.
The Dots guide is still the map of what a Dot may change. If this page and that guide ever disagree on send or spend, the guide wins. I wrote the boundary there so a team guide could not quietly widen it.
A growth marketer who saves this as a notion doc and never assigns the Friday memo will have an ultimate guide and an empty Monday. The sentence on the card is the part that matters. The rest is how I think about the two desks so the sentence stays honest.
What compounds is a workflow with the Friday decision still in context, and an agent that drafts from it instead of from a fresh prompt. Discovery happened in Work. Execution is the Monday draft. A marketing team that splits those and then glues them back together with copy-paste will feel busy and learn nothing.
Metaflow is where I keep that handoff. Work can finish the memo against a connected account. The Dot can repeat the draft. The skills are the instructions. A person still says yes before anything is sent, published, or spent. ChatGPT Work and Dots for a marketing team is the split. It is not a permission slip.
Frequently Asked Questions
Should a marketing team use ChatGPT Work or a Dot?
Both, on different days. Use Work to finish the first memo you would actually sign. Use a Dot to draft that memo again on a schedule. ChatGPT Work and Dots for a marketing team is that pair. Picking one and throwing away the other is how you either retype every Monday or automate a brief nobody designed.
What does a marketing team still do by hand?
Send, publish, and spend. I do not hand those to either desk. Metaflow's rule is the same on the Dot and on any agent that can touch an account: the draft can be ready, and a named person still acts. A busy Friday is not a reason to skip that name.
How do Work and a Dot hand off a weekly job?
You write one card. Work does it once, with the source open. The Dot repeats it. A person reads it before it ships. If the Friday memo was sloppy, fix it in Work before the Dot learns the sloppy version. Design once, then repeat only after you would sign the first design.
Is this the same as ChatGPT Work versus Dots?
No. A versus piece asks you to choose a mode for one session. This guide asks a team to keep both desks and to keep send and spend off both of them. Metaflow's Work versus Chat post is the session choice. Come back here for the week.
Where do prompts, jobs, and skills fit for the team?
A prompt is how you say the job once in Work. A skill is the instruction you keep. The job list is how you pick the next card. Metaflow split those onto their own pages so this guide could stay the split, not a second copy of each of them. Start with one card. Add a skill only after the Monday draft is one you would edit.
