> ## Documentation Index
> Fetch the complete documentation index at: https://sendmux.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Cold email outreach and GTM from your own inboxes

> Qubrics is an email layer that routes cold outreach through inboxes you own. Add sending accounts, set per-account caps, and run your GTM motion from an AI tool.

Qubrics is an email layer that routes cold outreach through sending accounts you already own. You add each inbox, set its sender details and its per-hour and per-day caps, then create one sending key. Qubrics picks an eligible account for every message and holds anything over that account's current cap.

That makes it the send rail underneath a GTM motion. Your tools pick the targets and write the copy. Qubrics decides which inbox carries each message and how fast.

> [!NOTE]
>
> You need a Qubrics team, at least one inbox you can supply SMTP credentials
> for or a Gmail or Outlook account you can authorise, and a prospect list you
> may lawfully contact.

> [!WARNING]
>
> Managed Amazon SES is for transactional email only. Use your own provider for
> marketing, newsletters, or bulk promotional sends.

## Do you need a domain for cold email?

No. You do not add or verify a domain in Qubrics when you send through your own accounts. Each account already authenticates for its own domain at its own provider, so Qubrics hands the message to that provider and the provider signs it.

| What you want to do | Domain needed in Qubrics |
| - | - |
| Send through your own accounts | No |
| Send through the managed SES from Qubrics | Yes |
| Receive mail or host mailboxes in Qubrics | Yes |

> [!NOTE]
>
> One failure mode is worth knowing. If the managed account is the only eligible
> provider for a send and the sender domain is not verified, Qubrics rejects the
> message and records it in [Logs](https://sendmux.ai/docs/monitoring/dashboard-logs.md#delivery-logs)
> rather than returning a bounce.

## Set up cold outreach in Qubrics

**1. Add your cold email accounts**

Open **Accounts** and select **Add Account**, then choose **Custom SMTP**,
**Gmail**, or **Outlook / Microsoft 365**. Run **Test Connection** on SMTP
accounts before you route real traffic through them.

Any inbox provider that gives you SMTP credentials works as a Custom SMTP
account, including Mission Inbox, ScaledMail, Zapmail, and others. There is
no vendor-specific connector for these. You supply the host, port, username,
and password, and Qubrics treats the account like any other.

![The Qubrics Add Account panel showing Custom SMTP, Gmail and Outlook connection types](https://mintcdn.com/sendmux/_GvW9aB1nNqc9iLf/images/integrations/email-marketing/sendmux-add-sending-account.png?fit=max\&auto=format\&n=_GvW9aB1nNqc9iLf\&q=85\&s=a1c989d6100c7ec57eb246114f53bb86)

Choose the connection type when you add a sending account.

Running a pool of inboxes? Use **Import Accounts** with the CSV template
instead of adding them one at a time. See
[Import accounts from a file](https://sendmux.ai/docs/sending/accounts#import-accounts-from-a-file).

![The Qubrics Accounts table listing several SMTP sending accounts with their delivery group, throughput caps and status](https://mintcdn.com/sendmux/Xt7AUMWml4nn5KBC/images/use-cases/cold-email-accounts-list.png?fit=max\&auto=format\&n=Xt7AUMWml4nn5KBC\&q=85\&s=da863218769afc4a7651c312ea325ec0)

A pool of inboxes, each with its own delivery group and per-minute, per-hour and per-day caps.

Then set the per-account details that make a pool behave like separate
senders:

| Setting | What to set it to |
| - | - |
| **From email** and **From name** | The persona that owns this inbox. |
| **Reply-To** | Where replies should land. |
| **Quotas** | Per-second, minute, hour, or day caps. `0` means unlimited, and a range such as `5-10` is accepted. |
| **Distribution percentage** | `0` to `100`, default `100`. Weights traffic when several accounts are eligible. |

![Advanced settings for one Qubrics sending account showing From Email, From Name, Reply-To, quotas, distribution percentage and delivery group](https://mintcdn.com/sendmux/Xt7AUMWml4nn5KBC/images/use-cases/cold-email-account-advanced.png?fit=max\&auto=format\&n=Xt7AUMWml4nn5KBC\&q=85\&s=3c399a28acd3b505e681491127ad55a0)

Advanced settings hold the sender identity, the caps and the routing weight for one account.

Full reference:
[Add your own account](https://sendmux.ai/docs/sending/accounts#add-your-own-account) and
[Advanced settings](https://sendmux.ai/docs/sending/accounts#advanced-settings).

**2. Pick how you will send**

Your sending route decides which credential you need, so choose before you
create anything.

| Route | Credential |
| - | - |
| SMTP, from an outreach tool or script | A sending key |
| HTTP, from your own code | A sending key |
| An AI client over hosted MCP | None. You authorise a connected app instead |

Sending through more than one route is fine. Create a key for the routes
that need one and authorise MCP separately.

**3. Create a sending key, for SMTP and HTTP**

Skip this step if you only plan to send over hosted MCP.

Open **API Keys**, select **Create API Key**, and choose the **Sending key**
type. Pick whether the key routes through all providers, selected providers,
or a delivery group.

![The Qubrics Create API Key dialog with Infrastructure Key, Sending Key and Mailbox Key options, with Sending Key selected](https://mintcdn.com/sendmux/Xt7AUMWml4nn5KBC/images/use-cases/cold-email-sending-key.png?fit=max\&auto=format\&n=Xt7AUMWml4nn5KBC\&q=85\&s=79390cc1ec5cee2dd36bfa33db5416a3)

Choose Sending Key. It covers the API, the CLI, MCP and AI agents.

Copy the `smx_mbx_` value straight into your secrets manager. It is shown
once. See [Create a key](https://sendmux.ai/docs/account/api-keys.md#create-a-key) and
[Key types](https://sendmux.ai/docs/account/api-keys.md#key-types).

Then send:

* **SMTP.** Host `smtp.qubrics.com`, port `587` with STARTTLS, password is
  your sending key. See [Sending by SMTP](https://sendmux.ai/docs/sending/smtp.md).
* **HTTP.** `POST` to the Sending API. See
  [Sending by HTTP](https://sendmux.ai/docs/sending/http.md).

**4. Or connect an AI client over MCP**

Hosted MCP authorises a connected app and issues its own short-lived tokens.
It does not use a sending key, and connected apps never create `smx_mbx_`
secrets. See [Connected apps](https://sendmux.ai/docs/account/api-keys.md#connected-apps) and the next
section.

> [!WARNING]
>
> Contact only people you have a lawful basis to email. Say who you are, keep
> the message relevant to the recipient, honour every suppression record, and
> give people a clear way to stop hearing from you.

## Run your GTM motion from an AI tool

Connect Qubrics to Claude or another MCP client and your agent can send through the same accounts, with the same caps, without you pasting a key into it.

**1. Add the server**

Add `https://mcp.qubrics.com/mcp` in your client. Per-client instructions are
in [Hosted OAuth
clients](https://sendmux.ai/docs/ai-integrations/mcp/clients#hosted-oauth-clients).

**2. Authorise the connection**

Qubrics asks you to pick a team, then which product lines the app may use.

**3. Check the tools appear**

Confirm the sending tools are listed. See [Verify the
connection](https://sendmux.ai/docs/ai-integrations/mcp/clients#verify-the-connection).

> [!WARNING]
>
> **Grant Sending API only.** Every product line is ticked when the
> authorisation screen opens. Untick **Mailbox API** and **Management API** so
> **Sending API** is the only one left. A Sending-only grant never asks you to
> choose mailboxes, and you do not need to create one. Add **Mailbox API** later
> if you also want the agent to read replies.

![The Qubrics authorise connected app screen with Mailbox API and Management API unticked and Sending API ticked](https://mintcdn.com/sendmux/9EML6-L2IAWgIXVX/images/use-cases/cold-email-mcp-consent-sending-only.png?fit=max\&auto=format\&n=9EML6-L2IAWgIXVX\&q=85\&s=73d81807cccb21bde70e605006389b88)

Under Product lines, leave Sending API ticked and clear the other two.

For what each surface covers and how long tokens last, see [MCP](https://sendmux.ai/docs/ai-integrations/mcp).

## What each part does

Keeping the boundary clear saves a lot of debugging later.

| Your GTM stack | Qubrics |
| - | - |
| Prospect list, segments, and enrichment | Eligible account selection |
| Message copy and personalisation | Sender details applied per account |
| Send schedule and follow-up timing | Per-second, minute, hour, and day caps |
| Reply reading and CRM updates | Delivery log, bounce and complaint events |

## Choose fixed caps or ranges

Use a fixed cap when you want one predictable ceiling per account. Use a range when you would rather the ceiling move inside boundaries you set. Qubrics picks a value when account information refreshes and holds that cap until the next refresh.

A range varies the ceiling. It does not add a delay between individual messages, and it does not guarantee inbox placement. Targeting, authenticated sender domains, message quality, and account history all still decide what happens after Qubrics hands the message over.

## Spread sends across several inboxes

Distribution percentage weights traffic between accounts that are eligible for the same send. Delivery groups go further and keep a stream of traffic on a chosen subset of accounts. The key you authenticate with decides which applies. See [How routing works](https://sendmux.ai/docs/sending/accounts/delivery-groups.md#how-routing-works).

> [!TIP]
>
> Put each campaign, or each customer, on its own delivery group. One inbox
> going bad then affects that group and nothing else.

## Add replies later

Replies land wherever the **Reply-To** on each account points, which by default is the inbox provider you own. Nothing in Qubrics is required for that.

You only need a Qubrics domain and mailbox when you want replies inside Qubrics, so an agent can read and act on them. That is also when the **Mailbox API** grant becomes worth adding to your MCP connection. See [Domain management](https://sendmux.ai/docs/domains.md) and [Mailboxes](https://sendmux.ai/docs/mailboxes).

## Check before your first campaign

* Every account tested and active.
* From, Reply-To, and caps reviewed on each account, not just the first one.
* Sending key stored in a secrets manager and scoped to the right providers, if
  you send over SMTP or HTTP.
* MCP grant limited to Sending API, unless you deliberately want mailbox access.
* Prospect sourcing, suppression, and opt-out handling settled.
* The opening message and every follow-up read end to end.

Start small. Read the logs, watch bounces and complaints, then raise volume.

## Common questions

> [accordion] Do I need a verified domain to send cold email?
>
> No, not when you send through your own accounts. Each account authenticates
> at its own provider. A verified domain in Qubrics is needed only for the
> managed account, or to receive mail.

> [accordion] Which inbox providers work with Qubrics?
>
> Any provider that gives you SMTP credentials, plus Gmail and Outlook or
> Microsoft 365 through the connected-account flow. Cold email inbox providers
> such as Mission Inbox, ScaledMail, and Zapmail connect as Custom SMTP
> accounts.

> [accordion] Do I need a mailbox to use MCP for sending?
>
> No. A Sending-only grant does not ask you to choose a mailbox, and you do not
> need to create one. Add the Mailbox API product line only when you want an
> agent to read replies.

> [accordion] How many sending accounts can I add?
>
> New Free teams include one account you add or connect yourself. The managed
> account does not count towards that. See [Account
> limits](https://sendmux.ai/docs/sending/accounts#account-limits) and [Team
> limits](https://sendmux.ai/docs/account/team-limits.md) for capacity requests.

> [accordion] Can I use the free managed account for cold outreach?
>
> No. Managed Amazon SES is for transactional email only. Cold outreach,
> marketing, and bulk promotional sending must go through accounts you own.

> [accordion] How do I see what was delivered?
>
> Open **Logs**. You can filter by status, account, and recipient, and export
> the result. See [Filter logs](https://sendmux.ai/docs/monitoring/dashboard-logs.md#filter-logs).

## Related guides

> [card] [Sending accounts](https://sendmux.ai/docs/sending/accounts)
>
> Add accounts and set sender defaults, caps, and routing.

> [card] [API keys](https://sendmux.ai/docs/account/api-keys.md)
>
> Create, scope, rotate, and revoke the key your outreach tool uses.

> [card] [MCP clients](https://sendmux.ai/docs/ai-integrations/mcp/clients)
>
> Connect Claude and other AI clients to your sending accounts.

> [card] [Deliverability](https://sendmux.ai/docs/monitoring/deliverability.md)
>
> Watch bounce rates, complaint rates, and account health.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.