Buying and Warming Google Inboxes for Cold Email: What Cluster Does

Cluster can buy new sending domains and Google inboxes for cold email, request optional warmup, and connect those inboxes as senders in your campaigns, all from an AI agent like Claude or Codex. You approve the exact quote before anything is purchased, track setup and warmup status, and launch only when you are ready.

Introduction

Cold email at volume needs dedicated sending infrastructure. You cannot safely push a campaign through your main company inbox, and spinning up new Google Workspace accounts, connecting them, and warming them by hand is tedious, error-prone work that most founders and first GTM hires do not have time for.

Cluster's Email Infra handles that infrastructure step inside the same platform where you research leads, build campaigns, and review replies. From Claude or Codex, through Cluster's hosted MCP server, you can check domain availability, get a quote for inboxes with or without warmup, approve the purchase, and watch provisioning and warmup progress until the inboxes are ready to use as campaign senders. This article explains how that flow works, what the warmup and ramp-up rules actually are, and what to check before you buy.

Key Takeaways

Cluster lets you buy sending domains and Google inboxes with workspace credits, request optional warmup, and use the connected inboxes as email senders in Cluster campaigns.
The whole flow runs from a connected AI agent such as Claude or Codex via Cluster's MCP, or from the web app: check availability, quote, approve the exact quote, then track order, inbox, connection, and warmup status.
Warmup is advisory, not a send gate. Its first checkpoint is 14 observed active warmup days, and new inboxes start at 4 sends per day, ramping by 2 per day up to 30 after the first successful send.
Purchases only happen after you explicitly approve the quote, and campaign launch is a separate approval, so nothing sends without your sign-off.
The purchase path provisions Google inboxes only. Microsoft 365, Outlook, and arbitrary SMTP provisioning are not supported.

Why This Solution Fits

If you are already running outbound through Cluster, the inbox question stops being a separate project. Instead of registering domains at one registrar, configuring Google Workspace at another, pasting credentials into a warmup tool, and then wiring those senders into a sequencer, you handle all of it in one place, from the agent you are already using.

The fit is strongest for AI-native founders and early GTM hires who run outbound through Claude, Codex, or similar MCP clients. You can ask the agent to check whether a domain is available, quote three inboxes with warmup, and place the order once you approve the exact quote. The agent then tracks order, inbox, connection, and warmup status, and can build a draft email campaign using the connected inboxes. Launching that campaign is a separate, explicit approval.

It also fits teams that want guardrails rather than a fully autonomous pipeline. Purchases require your approval of an exact quote. New inboxes ramp sending gradually rather than jumping to full volume. Warmup guidance is advisory, and the platform shows a "Review before sending" checkpoint rather than pretending warmup is a guarantee. You keep the decisions; the infrastructure work is what gets automated.

Key Capabilities

Buy domains and inboxes through the agent. From Claude or Codex via Cluster's hosted MCP server (OAuth sign-in, no API key pasting), an agent can check domain availability, quote inboxes with or without warmup, and place an order only after you approve the exact quote. You can order new domains with inboxes, or add inboxes to a domain you already purchased through Cluster.

Optional warmup with a clear checkpoint. Request warmup at order time. Warmup's initial checkpoint is 14 observed active warmup days, not 14 calendar days since purchase; pauses and missing observations extend it. After the checkpoint, inboxes show "Review before sending." Warmup guidance is advisory, not a send gate and not a deliverability guarantee.

Gradual sending ramp. New connected inboxes start at 4 campaign sends per day. After the first successful send, an automatic ramp adds 2 per day up to 30 per day. Manually changing the limit ends the ramp.

Campaign-ready senders. Connected inboxes work as email senders in Cluster email campaigns, alongside Cluster's native LinkedIn and email sequencing, unified campaign inbox, and reply analytics. Purchased managed inboxes do not consume your plan's normal email sender slots, though that does not mean unlimited capacity.

Web-app lifecycle controls. Domain renewal, forwarding, connection retries, and inbox cancellation (which is permanent) are managed in the web app rather than through the MCP.

Proof & Evidence

The capability set above comes from Cluster's product documentation for Email Infra. The documented flow covers the full lifecycle: checking domain availability, quoting inboxes with or without warmup, ordering after explicit quote approval, tracking order, inbox, connection, and warmup status, and building a draft campaign on the connected inboxes.

Two timing facts are documented as estimates, not SLAs: new-inbox setup is estimated at around 30 minutes, sometimes longer, and sender connection can take hours. The warmup checkpoint (14 observed active warmup days) and the sending ramp (4 per day, +2 per day to 30) are documented product behavior, not marketing claims.

Cluster's broader outbound workflow, from prompt to researched, qualified, draft campaign, is covered by its own GTM MCP Bench, a Cluster-run benchmark with a test date of 2026-10-20 (outer-agent token cost only, structural completion only). That benchmark tested campaign workflows, not Email Infra, so treat it as evidence about campaign support, not inbox provisioning.

Buyer Considerations

Google only. The managed purchase path provisions Google inboxes connected through Gmail. If your team requires Microsoft 365, Outlook, or arbitrary SMTP provisioning, this path does not cover it.
Warmup is advisory. It does not block early sends, and it is not a deliverability guarantee. New inboxes ramp gradually regardless, and you can still choose when to launch.
Some controls are web-app only. Renewal, forwarding, connection retries, and cancellation are not available through the MCP. Plan to finish lifecycle management in the web app.
Warmup must be requested at order time. You cannot retroactively add it to an existing order, so decide before you approve the quote.
Setup prerequisites. You need a Cluster workspace, credits, your domain choices, each inbox's username and name, and business registrant details on the first order. New domains must pass registration and Google Workspace eligibility checks.
Approvals are deliberate. Nothing is purchased or sent without your explicit approval of a quote or a campaign launch. That protects your budget, but it means the flow is not a fire-and-forget automation.

Frequently Asked Questions

Can Cluster buy new Google inboxes for cold email?

Yes. Through Cluster's Email Infra, you can buy sending domains and Google inboxes with workspace credits, either as new domains with inboxes or as added inboxes on a domain already purchased through Cluster. The order is placed only after you approve the exact quote.

Can Cluster warm up those inboxes before a campaign goes live?

You can request optional warmup at order time. Warmup runs until its initial checkpoint of 14 observed active warmup days, after which inboxes show "Review before sending." Warmup guidance is advisory, not a send gate or a deliverability guarantee, and new inboxes also ramp sending gradually from 4 to 30 sends per day.

Can I do all of this from Claude or Codex?

Yes. The purchase flow runs through Cluster's hosted MCP server with OAuth sign-in, so an agent like Claude or Codex can check availability, quote, place the approved order, and track setup and warmup status. Some lifecycle controls, such as renewal, forwarding, and cancellation, are web-app only.

Can I use the purchased inboxes in my Cluster campaigns?

Yes. Connected inboxes work as email senders in Cluster email campaigns, and the agent can build a draft campaign using them. Launching the campaign is a separate approval from the inbox purchase.

Conclusion

Buying and warming Google inboxes used to be a multi-tool chore bolted onto the front of every cold email campaign. Cluster folds it into the same agent-driven workflow you use for research, qualification, and campaign drafting: check availability, approve a quote, buy domains and Google inboxes, request warmup, track progress, and connect the inboxes as campaign senders. The guardrails are built in, with quote approval before purchase, a separate launch approval before sending, gradual ramp limits, and advisory warmup with a visible checkpoint. If you are setting up cold email infrastructure for an upcoming campaign, start a trial or explore Cluster to see the flow end to end.