Sending & Deliverability
Your sender address
Every account gets a working sender the moment you sign up: {yourcompany}.send.konvox.io, on Konvox’s own shared, pre-verified sending domain. No setup required to send your first email.
You have three options for where campaign emails actually send from:
| Type | What it is | Requires setup |
|---|---|---|
| Shared Konvox domain | {yourcompany}.send.konvox.io (the default) | None - works immediately |
| Your own mailbox | Connect a real Google Workspace or Microsoft 365 mailbox you already have | Google/Microsoft OAuth connect |
| Managed mailbox | Konvox sets up and hosts a mailbox for you (done-for-you) | Request it; ops fulfills it |
A custom sending domain (your own domain, not a Konvox subdomain, without connecting an existing mailbox) is available as a Custom-plan add-on - see Billing & Plans.
The email verification requirement (and why it exists)
This is the single most common reason a campaign looks stuck. Read this section if a contact’s enrollment shows “awaiting email verification.”
This requirement only applies if you’re sending from the shared Konvox domain. Here’s why it exists: every customer on the shared domain sends from the same underlying Mailgun infrastructure. If bad or fake addresses on one customer’s list bounce heavily, it can damage deliverability for every customer sharing that domain - including you. So Konvox requires a contact’s email to be verified as real and deliverable before it’s allowed to send through the shared pipe.
If you connected your own Google/Microsoft mailbox, or you’re on a managed/custom domain, this requirement doesn’t apply at all - you’re sending through your own infrastructure, not the shared one, so there’s nothing to protect other customers from.
Verification happens two ways:
- Automatically the first time you reveal a contact through Lead Finder.
- Manually - if a campaign enrollment is held on “awaiting email verification,” the Targets tab shows a one-click Verify now button right next to the reason. Click it, and if the address checks out, the hold clears and the next scheduled send goes out normally.
Verification uses Mailgun’s own validation API (with a fallback provider), costs 1 credit, and is cached for 30 days so you’re not re-charged for re-checking the same address repeatedly.
Warmup
New sender identities ramp up gradually instead of sending at full volume from day one - roughly (warmup day + 1) × 5 emails on day one, increasing daily up to your plan’s cap. This is automatic and can’t be turned off; it protects your sender reputation from looking like a spam blast on day one.
Deliverability basics Konvox already handles
- SPF, DKIM, and DMARC are configured on the shared sending domain.
- Bounce and spam-complaint webhooks feed back into the system automatically - a hard-bounced or complained contact is marked and excluded from future sends.
- Unsubscribe links are automatically appended to every outbound email and are fully functional (a real, working opt-out, not decoration).
LinkedIn accounts
Connect a LinkedIn account under Connections. Two connection methods exist:
- Browser extension (recommended) - the Konvox Relay Chrome extension runs LinkedIn actions from your own logged-in browser session. No proxy needed, and it’s the most durable method against LinkedIn’s own bot detection.
- Credentials-based - Konvox logs in on your behalf server-side. Works, but is more exposed to anti-automation measures.
Each plan includes a set number of LinkedIn accounts (see Billing & Plans); Scale allows purchasing extra seats beyond the included count.