How to Use ChatGPT Dots for Cold Emails: The Always-On SDR Agent

TL;DR

• ChatGPT Dots, launched September 29, 2026, are always-on AI agents that keep working between conversations. Unlike a standard ChatGPT thread that forgets context when you close the tab, a dot runs on its own GPT-6 Astra, powered cloud computer, connects to 4,000+ apps, and can research, draft, and triage at any hour.
• Cold email is the perfect use case for an always-on agent. Dots can watch for signal events (hiring rounds, funding, tech changes), build research briefs, draft personalized first lines, and queue them for your approval, without ever sending a message without your sign-off.
• Custom Rules are your safety net. Set your dot to "Ask before taking action" for external messaging. The model cannot send an email unless you explicitly approve it. Dots also support "Take action when you say so" and "Hand off to you" for different outbound tasks.
• You still need the rest of the stack. A dot drafts and researches. Deliverability (SPF/DKIM/DMARC, warmup, inbox rotation), sequencing, and CRM sync happen outside the dot. Use a dedicated sending infrastructure and keep your dot focused on the research-to-draft pipeline.
• No standalone email address at launch. Your dot works through your connected personal email, Slack, Teams, and ChatGPT. It cannot have its own outbound mailbox yet, and it cannot initiate calls.

OpenAI launched Dots on September 29, 2026, and the B2B outbound world got something it never had before: an always-on SDR that lives inside ChatGPT. Unlike the old workflow, open ChatGPT, type "write me a cold email for [company]," copy the output, repeat, ChatGPT dots for cold emails are a fundamentally different capability. Your dot keeps researching targets, drafting sequences, and flagging decision points while you sleep, attend meetings, or work on other projects.

The rest of this guide covers what Dots can and cannot do for cold outreach, how to set up Custom Rules (the guardrails that prevent auto-sending), copy-paste prompt blocks for common outbound jobs, and the infrastructure pieces a dot cannot replace.

Why ChatGPT Dots for Cold Emails Change the Outbound Game

A dot is not a chatbot session. It is a persistent agent with its own cloud computer, its own browser, and the ability to work across the apps you connect. Powered by GPT-6 Astra, it can receive a high-level goal, "Monitor these 50 accounts, research any that show growth signals, and draft a cold email for each", and keep making progress between your conversations with it.

For cold email operators, this changes the workflow from batch and blast to continuous qualification. Before Dots, the limiting factor was human time: researching one account deeply enough to write a specific first line took 10, 15 minutes. Most teams either skipped the research or hired low-cost SDRs to do it. A dot collapses that timeline. It can watch 200 accounts overnight, surface the 12 that matter, and have drafts ready by morning.

This table alone explains why ChatGPT dots for cold emails is a different category than "write me a cold email" prompts. The old approach treated ChatGPT as a typing tool. The dot treats it as an operating system for outbound.

The system around the draft is ChatGPT Dots for outbound.

How to Set Up Your ChatGPT Dot for Outbound Email

You cannot create a dot on mobile. Use the ChatGPT desktop app on macOS or Windows, or ChatGPT on desktop web. The setup flow takes about five minutes.

Step 1: Create and Name Your Dot

Open the desktop app and follow the onboarding prompts. Your dot's default handle is @yourname-dot. Rename it to something that signals its role, @yourname-outreach, for example, so context stays aligned with your outbound goals. Choose an avatar or let the dot generate one.

Step 2: Connect the Channels and Apps It Needs

From the desktop app, connect messaging channels so your dot can reach you outside ChatGPT:

• Slack, your dot can post progress updates or flag drafts for review in a dedicated channel.
• Microsoft Teams, same capability.
• Personal email, your dot can read and draft from your connected inbox. At launch, a dot cannot have its own standalone email address.

Then connect the data sources your dot needs for research:

• HubSpot or your CRM (via the plugins list under Customize → Plugins)
• Notion / Google Drive / Confluence (for ICP docs and playbooks)
• Slack channels where your team shares signal intelligence

The current plugin ecosystem includes HubSpot, Canva, Shopify, Klaviyo, Slack, and Teams. OpenAI does not offer a first-party Google Ads or Meta Ads plugin at launch. The plugin list is accessible inside your dot's Customize → Plugins screen on desktop.

Step 3: Set Custom Rules for Using ChatGPT Dots for Cold Emails Safely

Before any research or drafting begins, open Settings → Personalization → Custom rules. This is the layer that prevents a dot from acting on its own initiative with external contacts.

For any workflow involving external email addresses, the correct default is Ask before taking action for sending messages. This aligns with OpenAI's own documentation: "Asking your dot to draft replies doesn't give it permission to send them" (OpenAI Dots Controls). Your dot has a built-in "Auto-review" layer that checks every external action against your rules, your instructions, and safety requirements before it can proceed.

How to Run a Cold Email Workflow with ChatGPT Dots for Cold Emails

Once your dot is configured, here is the operating loop for outbound. Each phase corresponds to a job the dot performs, with the level of autonomy you define.

Phase 1: Continuous Account Research (Read-Only)

Your dot monitors connected data sources for signal events. It works in the background and does not need a message from you to begin.

• Scans LinkedIn for hiring rounds, leadership changes, and funding announcements.
• Checks your CRM for accounts whose contract is expiring or whose usage spiked.
• Reads product-announcement feeds or tech-news RSS for tech-stack changes.
• Compiles a daily signal brief and surfaces the top five accounts by ICP fit and timing score.

This phase is read-only by default. OpenAI's own safety design limits research tools so they "can't send messages, change app content, or control your browser or computer" (OpenAI Safety, Security, and Privacy into Dots). No approval needed.

Phase 2: Research Brief and Relevance Hypothesis (Generates Content, Requires Review)

When your dot detects a strong signal stack on an account, it composes a research brief and a reason to reach out, what the Metaflow Outbound Automation agent calls a "relevance hypothesis." The brief includes:

• Why this account, this person, now, the trigger event and its relevance to your offer.
• Company context, recent product moves, funding, hiring, or press mentions.
• ICP fit score, how well the account matches your ideal customer profile.
• Personalization hooks, specific details for the first line (their blog post, their product update, their customer win).

The dot presents this in a file or Slack message for your review. You approve, edit the hypothesis, or reject the account. The dot does not advance to drafting without your blessing.

Phase 3: Drafting and QA (Requires Approval)

With an approved hypothesis, your dot composes the cold email. It applies:

• Your voice and tone guidelines (set in the initial conversation or custom rules).
• First-line personalization using the research hooks.
• A single call to action, soft, not pushy.
• Length constraints (typically 80, 120 words for the body).

The draft goes through the Auto-review layer, then lands in your approval queue. You can edit, reject, or approve.

Copy-Paste Prompt Blocks for Your Dot

Below are three prompt blocks you can paste into your dot's conversation to kick off specific outbound jobs. Each one includes the instruction, the autonomy level, and the expected output.

Prompt Block 1: Daily Account Scan

Goal: Scan my connected CRM and LinkedIn for accounts with fresh signal events.
Autonomy: Research without asking. Present a ranked list of the top 5 accounts by ICP fit and signal freshness.
Output format:
- Account name, contact name, title
- Signal events detected (hiring, funding, tech change, product launch)
- ICP fit score (0–1)
- One-sentence relevance hypothesis
- Indicate which accounts you recommend for drafting and why

This runs as a recurring scheduled task. Ask your dot to repeat it every weekday morning and post the results to a Slack channel.

Prompt Block 2: Personalized First-Line Generation

Goal: For each approved account brief, generate 3 personalized first lines.
Autonomy: Draft only. Do not compose the full email. Do not send anything.
Input: Account brief with signal events and contact name.
Constraint: Each first line must reference a specific, verifiable detail from the research — not a generic compliment.
Output:
- Option A: Signal-first opener
- Option B: Mutual-reference or referral opener (if applicable)
- Option C: Question or observation opener
- Flag which option you recommend and why

Prompt Block 3: Draft Quality Review

Goal: Score the cold email draft against a rubric before approval.
Autonomy: Read-only analysis. No changes without approval.
Rubric:
- Is the first line specific, not generic? (Pass/Fail)
- Is the body under 120 words? (Pass/Fail)
- Is there exactly one CTA? (Pass/Fail)
- Does the tone match the "{your_brand_voice}" guidelines? (Pass/Fail)
- Are there any trigger words likely to hit spam filters? (Pass/Fail)
Output: Pass/Fail per criterion with a rewritten suggestion for any Fail.

Deliverability Guardrails, What Your Dot Cannot Handle

A dot is an excellent researcher and drafter. It is not an email infrastructure. ChatGPT dots for cold emails handle the creative and analytical layers of outbound. The plumbing belongs elsewhere.

Metaflow's cold email hacks guide covers the infrastructure in depth, but here are the non-negotiables your dot cannot replace:

• Dedicated sending domain, never send cold email from your primary domain. The Instantly 2026 benchmark report, analyzing billions of cold emails, found platform-wide average reply rates at 3.43%, down from 8.5% in 2019. Sending from a primary domain puts your transactional email at risk.
• SPF, DKIM, and DMARC, Google and Yahoo require these for any sender dispatching 5,000+ emails per day. Your dot cannot configure DNS.
• 30, 50 emails per mailbox per day, volume caps live in your sequencer, not in ChatGPT.
• Reply triage, your dot can read inbound replies and classify them (positive, negative, out-of-office, meeting booked). But the actual send infrastructure, inbox rotation, and warmup schedules belong to dedicated cold email tools.

As FastCompany reported (citing Will Allred, cofounder of an AI email coach), prospectors who sacrifice personalization for speed see 13× lower reply rates (source). A dot helps you avoid that tradeoff by doing the personalization work at machine speed, but it cannot replace the sending stack.

A Dot that must not send is the point of the Dot decision.

What Dots Cannot Do (Yet) for Cold Email

Honest about the gaps. Dots are six days old at the time of writing. Here is what the launch version does not support:

• Standalone email address. Your dot works through your connected email. It cannot have its own outreach@yourcompany.com mailbox.
• Phone calls. Your dot cannot initiate calls at launch. SMS is planned but not yet available.
• First-party Google Ads or Meta Ads plugins. The current plugin list includes HubSpot, Canva, Shopify, Klaviyo, Slack, and Teams, but no Google or Meta ad platform plugin.
• Autonomous sending. This is by design, not a gap. Custom Rules prevent it. OpenAI's safety architecture ensures "actions that could affect your accounts or share information go through Auto-review" (OpenAI Dots Safety).

The channel you do not automate in a browser is Dots for LinkedIn.

Guardrails and Safety, Never Auto-Send

The most common question about ChatGPT dots for cold emails is whether the dot can email a prospect without you knowing. The answer is no, provided you set Custom Rules correctly.

The safety stack has three layers:

1. GPT-6 Astra alignment. The model is trained to refuse harmful requests and to pause when a requested action falls outside your instructions. OpenAI red-teamed dots against changing instructions, ambiguous requests, and attempts to push past permission boundaries (OpenAI Safety Post).
2. Auto-review. Every external action (sending a message, changing a CRM record, posting to Slack) passes through an automated review that checks it against your Custom Rules, your instructions, and safety requirements. If the review flags a concern, the action is paused and you see a warning.
3. Your Custom Rules. "Ask before taking action" for sending messages means the dot literally cannot execute the send. It prepares the output, shows it to you, and waits for an explicit approval.

This three-layer approach mirrors the governance structure in Metaflow's marketing agent guardrails framework: model alignment, automated checks, and human-in-the-loop approval. Applied to cold email, it gives you the speed of an AI SDR without the risk of an unsupervised send.

Never-auto-send is a block rule: allow, approve, and block.

What may send is outbound automation. The Metaflow plugin's own prompt is a draft that does not send.

FAQ

Is cold email still effective in 2026?

Yes, but only with personalization at scale. The Gartner poll showed 55% of organizations were in pilot or production with generative AI by fall 2025 (source), and a third of those adopters were in sales and marketing. Buyers expect relevant, researched outreach. A dot helps you deliver personalization at scale, but the sending infrastructure and deliverability practices still determine whether the email lands in the primary inbox.

Can ChatGPT dots auto-send cold emails?

Not if Custom Rules are set correctly. The default behavior requires your approval before any external message is sent. OpenAI's Auto-review layer also intercepts actions that fall outside your instructions. If your goal is to prevent accidental sends, set a Custom Rule: "Ask before taking action" for any action involving email addresses that are not your own.

What is the 30/30/50 rule for cold emails?

The 30/30/50 rule refers to the percentage split of email body: 30% personalization, 30% value proposition, 50% social proof or case study. It is a copywriting heuristic, not a deliverability requirement. Dots can follow this ratio if you include it in your tone and structure instructions.

What are the best tools for cold emailing to pair with Dots?

Dots handle research and drafting. For the sending stack, pair with dedicated cold email tools for domain warmup, inbox rotation, SPF/DKIM/DMARC configuration, and reply triage. For the playbook layer, signal selection, hypothesis scoring, and outbound QA, platforms like Metaflow Outbound Automation complement the dot's drafting capability with governed, approval-first outbound workflows.

The Bottom Line

ChatGPT dots for cold emails are the first always-on AI SDRs that most teams can access without building custom agent infrastructure. They handle the research, personalization, drafting, and triage layers that historically consumed most of an SDR's time. But they are a creative and analytical layer, not an entire outbound stack.

The winning configuration combines three layers:

1. The dot, always-on research, drafting, and triage inside ChatGPT.
2. The sending infrastructure, warmed domains, SPF/DKIM/DMARC, inbox rotation, and sequencer tools that handle delivery.
3. The governed playbook layer, signal selection, relevance scoring, outbound QA, and approval workflows that turn drafts into pipeline.

This is the same three-layer architecture we built at Metaflow: the AI-powered GTM workflows framework, where agents handle the cognitive load and humans own the decisions that matter. Dots are a major step forward for the first layer. They do not eliminate the need for the other two.