Email & team setup

Connect your support email

Verify your sender domain, forward incoming mail, and test a complete conversation.

You can keep your existing customer-facing address, such as [email protected]. OutcomeArc receives forwarded mail and sends replies using your verified domain.

An owner or administrator with access to the inbox can set this up. You’ll also need access to the mailbox’s forwarding settings and your domain’s DNS.

Verify the sending address

  1. Open Settings → Inboxes, choose the inbox, and open Custom sender.
  2. Enter the customer-facing address and From name. Add Reply-To or Auto-BCC only if your workflow needs them.
  3. Connect the domain and copy the exact DKIM TXT and Return-Path CNAME records shown.
  4. Add those records at your DNS host, then return to OutcomeArc and check verification.

Both records need to verify before sending is enabled. Keep existing DMARC records in place. If verification is still pending, compare the record names and values carefully and allow time for DNS changes to appear.

Forward incoming email

Copy the private forwarding address shown in setup. In your email provider, forward new messages from your support mailbox to that address.

Your forwarding destination can use OutcomeArc’s branded inbound domain. Copy the complete saved address, including its domain and random suffix. Changing the domain yourself will not create a working destination. Your customers continue to write to your own support address.

For Gmail or Google Workspace, add it under Settings → See all settings → Forwarding and POP/IMAP. If Google sends a confirmation message, use the forwarding confirmation shown in OutcomeArc to approve it, then return to Gmail and turn forwarding on. Adding the address alone doesn’t enable forwarding.

For other providers, use their mailbox forwarding settings. Each inbox has its own private destination. Copy the exact address for the selected inbox, including the + suffix. Preserve original To/CC and message headers where possible for message history and threading, but those headers do not route mail to other inboxes. Never substitute another inbox’s private destination.

Keep the original mailbox available for administration, but have teammates reply from OutcomeArc so the conversation history stays together.

Add aliases

Add same-domain aliases in Custom sender when multiple addresses should reach this inbox. Forward each alias too. Replies can use the original alias the customer wrote to.

Each address belongs to only one OutcomeArc inbox. If a different team or product needs its own settings, create a separate inbox rather than sharing an alias.

Mail addressed to multiple connected inboxes appears in each only when each mailbox forwards it to its own private destination. If only Support forwards, only Support receives a copy—even if Billing is in To or CC. Copies have separate status, assignment, unread state, private notes and handling workflows. Repeated forwards through aliases to the same inbox are deduplicated when enough original-message evidence is preserved; altered or missing evidence can prevent detection. Gmail forwarding confirmations stay with the matching requesting mailbox and are never broadcast.

Test both directions

  1. Send a new message to the support address from an external account.
  2. Confirm it appears in the intended OutcomeArc inbox and run Check inbound.
  3. Reply from OutcomeArc and confirm delivery.
  4. Reply again from the external account and check that it returns to the same conversation.

Repeat these checks for every inbox and alias. Being included in another inbox’s To/CC line is not proof that this mailbox’s forwarding works.

OutcomeArc uses its included email transport. Connecting email doesn’t require custom SMTP or Google/Microsoft OAuth.

Browse all topics →

Still need a hand? Ask our team.