Pango Neuro blog thumbnail showing two separate 3D chat bubbles to illustrate splitting ad tasks into separate chats

Why every new ad task should start in a new chat

An AI agent’s answers are shaped by the instructions and assumptions that pile up over a conversation. In ad operations, start a new chat to wall off context whenever the goal or the decision criteria change.

AI carries the last meeting into the room with it

Monday morning, you dug into last week’s ROAS drop. In the same chat, you cleaned up copy for a client report on Tuesday, then asked for a budget draft for a new campaign on Wednesday. But the AI keeps answering as if it’s still Monday — pinned to GA4 as the source, a week-over-week comparison, and the campaign exclusions you set that day.

The problem here isn’t that the AI suddenly got dumber. It’s that the assumptions you stacked up earlier in the conversation are still in play on the next task. That’s especially risky in ad operations. Mix up date ranges, ROAS sources, campaign objectives, or approval status even slightly, and you get answers that sound plausible but fall apart the moment you try to act on them.

Chat context is more like working memory

Most AI chats feed everything in the current conversation — your messages, the AI’s answers, files, and tool outputs — into the next answer. OpenAI notes that as a conversation gets longer or runs many turns, you have to account for the context window and token limits. Anthropic likewise describes the context window as the model’s working memory: what it can pull from when it generates a response.

The key point: more context isn’t always better. When you’re going deep on a single advertiser, a long thread helps. But the moment you switch to a new advertiser, a new time frame, or a new decision, that old thread turns into noise. Sometimes keeping only what’s relevant to the task at hand beats giving the AI more to chew on.

A new chat isn’t a totally blank slate, either. Depending on the product, stored memory, project guidelines, workspace guidelines, and Gem guidelines can still carry into new conversations. So in practice, this split is safer: keep your team’s standing rules in a Gem or in workspace guidelines, and spell out this task’s dates, objective, and decision criteria in the first message of the new chat.

Split by the decision, not the question

A simple rule like “same chat while the questions keep flowing, new chat when the question changes” doesn’t go far enough. In ad operations, it’s better to split by the decision than by the question. Keep narrowing down the root cause on the same campaign? Same chat. But when you move from analysis to drafting an action plan, or from report copy to reviewing a budget change, a new chat is the safer call.

What changedWhen you can stay in the same chatWhen you should open a new chat
ObjectiveNarrowing down the same performance drop, or polishing the same report copyMoving from diagnosis to a decision — a budget change, a creative swap, a client email
Time frameWidening from week-over-week to a monthly trend on the same basisSwitching to a different reference period — monthly reports, real-time incident checks, promo post-mortems
AdvertiserComparing other campaigns from the same advertiser under the same objectiveSwitching to a different brand, a different budget owner, or different reporting standards
Data sourceChanging only the segments within the same GA4 basisMoving the basis for the call from GA4 to ad platform dashboards or back-office revenue
Permission levelSticking to analysis onlyReviewing actions that touch the outside world — bids, budgets, campaign status, client comms

The contexts that are most dangerous to mix in ad operations

Context contamination doesn’t always blow up into a major incident. But in ad operations, where real spend and client relationships are on the line, a few contexts have to stay separate. It’s especially easy to miss when the AI takes a numeric threshold from an earlier conversation and applies it straight to the current task.

Mixed contextRisky answerSafe way to start
ROAS sourceTreating Meta Ads Manager ROAS and GA4 ROAS as interchangeable decision metricsSaying up front that, in this chat, reporting ROAS is measured on a GA4 basis only
Date rangeApplying last week’s incident-check conditions to this month’s budget reviewLocking the analysis window, the comparison window, and the events to exclude in the first message of a new chat
Campaign objectiveJudging awareness campaigns as if they were conversion campaigns, or the other way aroundHaving the AI summarize each campaign’s objective and optimization event before it starts the analysis
Approval statusTreating changes approved in an earlier conversation as if they were still live, valid action plansSpelling out whether this chat is for draft review, an approval request, or a pre-launch check
AttachmentsCarrying rules from an old file over to a new one and misreading what the columns meanNaming which files to use and which to ignore in this chat

How Neuro draws the line

In Neuro, opening a new chat means kicking off a new unit of work. It doesn’t throw away your team’s operating standards. Your workspace guidelines, connected ad platforms, and selected Gems stay in place as standing rules — only this task’s goals and decision criteria get declared fresh.

  1. Pick the objective first. Pin it to one of: diagnosis, reporting, action-plan review, approval request, or a how-it-works explanation.
  2. When the objective changes, open a new chat — especially when you move from analysis to execution or client comms.
  3. Choose the Gem that fits the task. Lock in its role: a weekly report Gem, a budget review Gem, a creative review Gem.
  4. In your first message, spell out the time frame, data source, comparison basis, exclusions, and the outputs you want.
  5. Don’t ask for conclusions right away. Have the AI summarize this chat’s assumptions first.
  6. When the analysis is done, carry only the summary you need into the next chat. Don’t copy-paste the whole thread.

When it’s fine to keep going in the same chat

The point isn’t to spin up as many new chats as possible. When you need to keep refining the tables, hypotheses, or calc rules the AI just produced — all within the same decision — the same chat is better. Cutting context there just runs up the cost of re-explaining everything.

  • Digging deeper into the root cause of a performance drop on the same campaign
  • Tightening or polishing report copy the AI wrote under the same criteria
  • Swapping only the segments while the time frame and data source stay the same
  • Asking for extra supporting tables for a hypothesis it just put forward
  • Shoring up the rationale on an approval card, or laying out the reasons for a rejection

The rule is simple. If the last answer needs to be raw material for the next one, stay in the same chat. If the last answer could bias the next one, open a new chat.

First-line examples for a new chat

The first line of a new chat doesn’t need to be long. It just needs to draw a clear boundary around the task. You can paste the lines below straight into Neuro and only swap in your own dates, advertiser, and campaign names.

ScenarioWeak startBetter start in Neuro
Weekly diagnosisHow did the ads do this week?This chat is for a weekly performance diagnosis covering 11–17 May 2026. Lead with ROAS from GA4 reports and show ad platform ROAS as a reference only. Before any conclusions, summarize the analysis assumptions for this chat first.
Budget reallocation reviewWhere should we shift budget?This chat is for a pre-launch review of budget changes. Over the last 14 days, separate campaigns that are over target CPA from candidates for a budget increase. Don’t make any actual changes — just pull together the evidence for an approval card.
Creative reviewWhich creatives should we swap?This chat is for picking new Meta creatives to swap in. Look at conversion campaigns only and leave out awareness campaign performance. Shortlist candidates by fatigue, CTR drop, CPA increase, and most recent edit date, in that order.
Client reportingWrite the report copy for meThis chat is for drafting the weekly report copy we’ll send the client. Don’t state causes as settled — separate what the data confirms from hypotheses that still need checking. Keep internal operating notes out of the copy.
New advertiser onboardingAnalyze this account for meThis chat is for the first diagnosis of a new advertiser account. Don’t reuse standards from other advertisers. First, check whether the campaign names, conversion tracking, UTMs, and key goal events are in a state the AI can actually read.

What belongs in your team rules

A good AI operations team isn’t the one writing long prompts every time. Standing standards live in Gems and workspace guidelines; the task context that changes every time goes in the first line of a new chat. Split it this way and the AI gets confused less often — and when teammates read the chat logs, it’s far easier to trace which decision was made under which criteria.

  • One chat, one decision.
  • Put the advertiser, time frame, and objective in the title of every new chat.
  • Keep standing team standards in Gems or workspace guidelines, not buried in the chat itself.
  • On the first reply, have the AI summarize this chat’s assumptions before it draws any conclusions.
  • When you’re unsure whether to keep going or start fresh, check whether the objective, time frame, data source, permission level, or audience has changed.
  • When you move to the next task, carry only the final summary, the confirmed criteria, and the open questions — not the whole conversation.

The quality of AI ad operations isn’t set by the model alone. It comes down first to operating habits — what you hold onto and what you start over. A new chat isn’t just good housekeeping; it’s a safety mechanism for your decisions.

Related posts

Sources

  • OpenAI API Docs: Conversation state

    Official OpenAI docs on managing the context window and token limits as conversations grow, noting that both input and output tokens count toward context usage.

  • Anthropic Claude Docs: Context windows

    Official Anthropic docs describing the context window as working memory the model can reference when generating responses, and explaining how conversation turns accumulate.

  • OpenAI Help Center: Memory FAQ

    Official OpenAI help article on how stored memory and references to chat history can carry into new conversations, and how users can manage their memory settings.

  • OpenAI API Docs: Prompting

    Docs on prompt management principles: put recurring instructions like role and tone in the system message, and put task-specific details and examples in user messages.