You connected the address you want your cold outreach to come from, you gave it the outreach role, and the queued campaign emails still show a different address. Nothing is broken with your mailbox. KM Hub keeps two separate lists, and cold campaigns read the second one.
The two lists
- Settings > Email Senders is the set of addresses your workspace is allowed to send as. Newsletters and broadcasts read the roles you set here.
- Sending inboxes, on the Cold Campaigns page, is the rotation pool that cold campaigns actually send from.
Tagging an address outreach in Email Senders does not add it to the sending inboxes pool. If that pool is empty, cold sends fall back to your default identity, which is usually the address on your verified domain. That is the address you are seeing on the queue.
Put your address in the pool
- Open Cold Campaigns.
- Expand Sending inboxes.
- Under Mailboxes you have already connected, find your address and click Use for outreach.
There is no password to type again. The mailbox keeps its own address and credentials.
It starts slow on purpose
A newly added inbox goes in warming: it starts at 5 emails a day and ramps its quota up toward the target automatically, so the address builds a reputation before it goes to volume. That is not a fault, and turning it off is how addresses land in spam.
One thing that will look inconsistent
Replies to people who wrote to you still go from the address they wrote to, not from your outreach address. That is deliberate: an answer should come back from the address on the original message. Only cold campaign mail follows the outreach role.
Check before you release the queue
After you adopt the mailbox, refresh the campaign and look at the Emails tab. The queue shows the address that will actually be used, so what you read there is what leaves.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article