Set up a free custom support email with Cloudflare
Receive mail at your own support address and reply from OutcomeArc without buying a separate mailbox.
You can use [email protected] in OutcomeArc without buying a separate Google Workspace or Microsoft 365 mailbox. Cloudflare Email Routing forwards incoming messages to OutcomeArc for free. Your team reads and replies in OutcomeArc, and customers see your authenticated support address. This does not create a separate mailbox or webmail login. You still need a domain you own and an OutcomeArc account.
Before you start
If your domain already receives email, keep your current mail provider. MX records tell other mail servers where to deliver mail for the whole domain, not just one address. Replacing Google Workspace, Microsoft 365, or another provider’s MX records with Cloudflare’s can stop delivery to existing mailboxes, even ones you don’t use for support. Instead, forward only the support address from your existing provider. If your DNS administrator sets up routing on a separate subdomain, the address changes too: for example, [email protected] instead of [email protected].
This setup is best for a domain that doesn’t already receive mail. You’ll need access to its Cloudflare DNS settings, owner or administrator access to the OutcomeArc inbox, and a different email account to send a test. The domain can stay registered at your current registrar; it just needs to use Cloudflare DNS. If you’re moving DNS, have your administrator make sure your website and other existing records are carried over.
1. Connect your support address and enable routing
- In OutcomeArc, open Settings → Inboxes, select your inbox, then open Custom sender → Support address.
- Enter the address customers will write to, such as
[email protected], and your team’s From name. Select Connect domain. - Open Incoming mail and choose Cloudflare Email Routing to follow the steps in the app.
- In the Cloudflare dashboard, open Compute → Email Service → Email Routing, select Onboard Domain, and choose your domain. Review the routing DNS records before confirming. See Cloudflare’s routing instructions if you need help getting your domain ready.
2. Add the private forwarding destination
In OutcomeArc’s Add your destination step, select Copy address. In Cloudflare, open Email Routing’s Destination Addresses, paste the complete address, and submit it. Don’t change anything after the + sign or @. This address is unique to this inbox. Keep it private; customers should write to your support address instead.
3. Verify the destination
Cloudflare sends a verification email to the address you just added. In OutcomeArc, select Open inbox for verification, choose All conversations, and look for Cloudflare’s “Please verify your email address” message. Only use a message you requested, and check that the link goes to Cloudflare before selecting Verify email address. Don’t share the verification link. Then return to Cloudflare and confirm that the destination shows Verified. OutcomeArc does not verify it automatically.
If the message is missing, clear any inbox filters, check Spam, and compare the address character for character. You can resend the verification email from Cloudflare’s Destination Addresses. If you already verified this exact destination, Cloudflare may show it as verified without sending a new message.
4. Create the routing rule
In Cloudflare’s Email Routing, select your domain, then open Routing Rules → Create routing rule. For Email pattern, enter the part before the @ (for example, support) and select your domain. Choose Send to an email, select the verified OutcomeArc destination, and save. Make sure the rule shows as active. If you use aliases, create a rule for each one; different OutcomeArc inboxes need their own private destinations. See Cloudflare’s rules and addresses reference for help.
5. Test receiving and replying
- Send a new email from a different account to
[email protected], not to the private forwarding address. Try including a small attachment. - Open it in OutcomeArc and select Check inbound in Custom sender → Incoming mail. Cloudflare’s destination verification email does not count as a delivery test.
- In Sending & replies, add the exact DKIM TXT and Return-Path CNAME records OutcomeArc shows, then select Check DNS. Keep any existing DMARC policy in place. You can send only after both records verify.
- Reply from OutcomeArc. In the external account, confirm that the reply came from your support address. Reply to it from that account and check that the message appears in the same OutcomeArc conversation. Run Check inbound again to check reply threading.
Cloudflare’s MX records handle incoming delivery. Its SPF and DKIM records apply to routing; they don’t replace OutcomeArc’s sender authentication. Keep OutcomeArc’s DKIM TXT at its own selector and set its Return-Path CNAME to DNS only (not proxied) at the host shown in the app. If you already have an SPF record at the same DNS name where Cloudflare needs one, ask your DNS administrator to combine the required entries into one SPF record rather than creating a duplicate.
If something isn’t working
| What you see | What to check |
|---|---|
| Destination is still pending | Resend the verification email and use the latest one you requested. A rule won’t work until its destination is verified. |
| Verified destination, but no mail | Check that the rule is active, uses the right address and destination, and that Cloudflare reports the required MX records. DNS changes can take time. Send a fresh message after the records take effect. |
| Small messages arrive, but large ones don’t | Cloudflare rejects incoming messages over 25 MiB. This is the size of the whole encoded email, including headers, body, and attachments. The files themselves need to be smaller; try fewer or smaller files, or use a secure sharing link. |
| Mail arrives but replies won’t send | In Sending & replies, check both sender DNS records. Incoming routing can work before your sender is verified. |
| Replies start a new conversation | Reply directly to the test message instead of writing a new email with the same subject. Make sure any custom Reply-To address also routes to this inbox. |