Inboxes for PlusVibe

PlusVibe is newer than the sequencers most cold email teams started on, which means the people reading this are usually in one of two situations: weighing it up against a tool they already pay for, or already decided and now working out what to run it on.

We are not the right people to tell you which sequencer to buy — we are a technology partner on the infrastructure side, and we sell inboxes and domains, not seats. What we can tell you precisely is the part that decides whether any sequencer performs: what the mailboxes underneath it are, how hard you can push them, and what to do when one stops behaving. A good sequencer on poor infrastructure loses to a mediocre sequencer on good infrastructure every time, because the mailbox is what the receiving server is actually judging.

Nearly every failed mailbox connection is a mailbox that is not finished rather than a sequencer that is broken. Four things to have settled:

• Real mailboxes on a licensed tenant. Every inbox we deliver is an official Google Workspace, Microsoft 365 or Azure mailbox, not a relay, an alias or a shared SMTP service. You hold the admin, so you can rotate credentials without asking us.
• Authentication already published. SPF, DKIM, DMARC and forwarding are configured before handover. Worth confirming rather than trusting — the deliverability grader checks all of it plus blacklists and domain age in a single pass.
• Two-factor decided. On delivery day, either turn 2FA off on the receiving account before handover, or keep it on and grant restricted sub-account access to [email protected]. Orders where neither has happened take longer than the usual 48 to 72 hours.
• A connection method chosen. OAuth where the provider offers it, IMAP and SMTP otherwise. On Microsoft that choice has a consequence most people meet the hard way, below.

Written as what you are doing rather than as a click path: PlusVibe is young enough that its menus are still moving, and a page full of button labels goes stale in a quarter and makes everything around it look stale too. The sequence itself is the same on every sequencer worth using.

1. 1Connect by provider where you can. Use the Google path for Google Workspace mailboxes and the Microsoft path for Microsoft 365 and Azure. Authorising over OAuth means no password is stored, nothing breaks when one is rotated, and the app-password route is avoided entirely.
2. 2Know that SMTP AUTH is off by default on new Microsoft tenants. If you connect Microsoft mailboxes over IMAP/SMTP instead, authenticated SMTP has been disabled by default on tenants created in recent years — at the tenant level and again per mailbox. It fails looking exactly like a wrong password. Enable SMTP AUTH on the mailbox, or connect over OAuth and never meet it.
3. 3Bulk import rather than adding one at a time. Past a handful of mailboxes, adding accounts individually is an afternoon you will not get back. We hand over credentials in a form you can shape into an import file — or we do this step for you, which is the default.
4. 4Set display name and signature before the first send. A new sender whose first cold email has no display name and no signature is advertising exactly that. Both are per-account and both are worth doing across the fleet in one pass.
5. 5Set the daily cap deliberately, not by default. The default is not tuned to your mailboxes, and this is the setting that decides how long the fleet lasts.

The question people ask before switching is whether they have to start again. Mostly, no — but the line between what moves and what does not is worth knowing before you cancel anything.

The one that bites is the suppression list. It is the only item here whose loss is not an inconvenience but a compliance and reputation problem: everyone who unsubscribed from you is recorded in the old tool, and if that list does not make the trip you will mail them again. Export it before you cancel the old subscription, not after — access usually ends with the billing.

One number per mailbox per day, different per platform. The infrastructure calculator sizes fleets on these figures, so matching them in PlusVibe keeps your tool and your plan telling the same story:

Azure is the one worth reading twice, because it is the only row where the number you can send is something you choose rather than something you are given. The tenant costs the same with 25 mailboxes on it as with 100, so loading it lightly buys you three times the per-inbox pace for exactly the same money — and costs you the inboxes you did not put on it. Which way that trade falls depends on whether you are short of volume or short of budget.

Work the fleet out properly rather than guessing: the calculator sizes by target volume, and the inbox planner goes the other way, from the sends you need to the inboxes and domains that produce them.

Prewarmed inboxes arrive with sender history already built, so there is no 21-day wait before the first campaign. Fresh inboxes are warmed by us for 14 to 21 days before handover. Either way warmup does not stop at delivery — it keeps running at 30 emails per inbox per day underneath your campaigns for as long as you have the inboxes.

So the sequencer’s own warmup is not the safety net it would be on mailboxes you built yourself, and it is not free: warmup mail is real mail from the same mailbox, drawing on the same daily budget and the same reputation. Leave it off, or if you turn it on, count it inside the inbox limit rather than adding it on top.

Free, no account needed, and faster than diagnosing a quiet campaign a fortnight later:

• Deliverability grader — SPF, DKIM, DMARC, MX, eight blacklists and domain age in one pass, with a grade.
• DKIM checker — tells you not just whether a key is published but whether a selector is delegated to a provider that has published nothing, which is the most common silent DKIM failure on Microsoft tenants.
• SPF checker — including the recursive lookup count that quietly breaks SPF past ten.
• SURBL checker — the domain-level list that matters most for cold email, and the one most checkers skip.
• All the tools — thirty-odd of them, every one free and public.

One account’s reply rate falling while the rest hold, bounces climbing on a single domain, a drop in opens from one mailbox provider. At volume this is routine rather than alarming, and the response is the same each time: pause that account in PlusVibe so the campaign reroutes across the fleet, check whether the problem is the inbox or the domain with the blacklist checker, then message us.

Support is on WhatsApp at +1 904 736 2539, 24/7, and replacement inboxes are part of the package when deliverability drops. The reason to keep a few spare accounts rather than running the fleet at its exact ceiling is this: with headroom, a flagged inbox is an inconvenience; without it, it is a paused campaign.

Prewarmed inboxes include a free prewarmed .COM or .CO domain and send from the day they land: $8.00 per inbox per month on Google and Microsoft, falling to $7.00 on a two-month commit and $6.00 quarterly. Azure is billed per tenant rather than per inbox — $69 monthly, $60 on two months, $50 quarterly — and a tenant holds up to 100 inboxes on one domain, so at full capacity that is $0.69, $0.60 and $0.50 per inbox.

Fresh inboxes are built on your own branded domains and warmed for 14 to 21 days first, which is why they land at roughly a third of the price at volume: Google from $3.50 down to $2.00 per inbox per month by order size and cycle, Microsoft 365 from $3.00 to $2.00, and an Azure tenant flat at $50. Domains through us list at $20 and are currently $12; bring your own and there is no domain charge at all.

The full table is on the offer page, every price on the site is published as plain text at /price.md, and how it works covers everything between paying and your first send.

Can I move my existing inboxes to PlusVibe without rewarming them?

Yes. Sender reputation lives with the mailbox and the domain, not with the sequencer, so moving the same accounts to a different tool does not reset it. What does not carry across is the per-account history inside the old tool: sending caps, schedules, tags and suppression lists are the old tool’s data and have to be rebuilt or exported.

What daily limit should I set per inbox?

Fifteen a day on Google Workspace, eight on Microsoft 365, and two to six on Azure depending on how densely the tenant is loaded. These are below what each platform technically allows, on purpose: the number that matters is the one an inbox holds for months, not the one it survives for a fortnight.

Do you connect the inboxes to PlusVibe for me?

Yes, by default. We connect the mailboxes to your sending tool as part of the build. If you would rather do it yourself you get full admin access to every mailbox and the credentials to plug in.

Is WarmInboxes an official PlusVibe partner?

Yes. WarmInboxes is a PlusVibe Technology Partner, listed on plusvibe.ai. That is a partnership on the infrastructure side; we sell the inboxes and the domains, not PlusVibe seats.

Do I still need PlusVibe warmup if the inboxes are prewarmed?

No, and running it is not free. Every warmup email is a real send from the same mailbox competing for the same daily budget. Our warmup already runs at 30 emails per inbox per day underneath your campaigns and does not stop. If you enable the sequencer’s warmup too, count it inside the inbox limit rather than on top of it.

How fast do the inboxes arrive?

Within 48 to 72 hours of payment, prewarmed and fresh alike, with SPF, DKIM, DMARC and forwarding configured before you log in. Prewarmed means there is no warmup wait once they land, not that they are delivered the same day.