Email

Email on Arino One is a first-class channel: it shares the same contact record and the same inbox as WhatsApp, SMS, RCS and every other channel, so a support thread that starts on WhatsApp and continues by email stays one conversation with one history. Setting it up means authenticating a sending domain and deciding how email fits into your routing and campaign strategy.

Why authentication matters first

Before any email leaves the platform, the receiving domain needs proof that you are allowed to send as your brand. Three DNS records do this job together: SPF lists the servers permitted to send on your domain's behalf, DKIM cryptographically signs each message so it can't be tampered with in transit, and DMARC tells receiving mail servers what to do when a message fails either check. Skipping any one of them doesn't just risk a warning banner — major providers like Gmail and Outlook increasingly reject or spam-folder unauthenticated bulk mail outright, and that damage bleeds into your general brand reputation, not just this one send.

Setting up the sending domain

1. Choose a dedicated sending subdomain. Something like mail.yourbrand.com or send.yourbrand.com rather than your root domain. This isolates the reputation of transactional and marketing email from your day-to-day corporate mail, so a bad campaign never affects whether your CEO's emails land in someone's inbox.
2. Publish the SPF include. The console generates a TXT record naming Arino's sending infrastructure as authorized. Add it to your DNS provider under the chosen subdomain.
3. Publish the DKIM CNAME records. These point your subdomain at signing keys hosted by the platform, letting every outbound message carry a valid signature.
4. Publish a DMARC record. Start conservative, at p=none, which only asks receivers to report failures rather than block them. Watch the aggregate reports for a week or two, then tighten to p=quarantine and eventually p=reject once you're confident every legitimate sending source is covered.
5. Verify in the console. Once records propagate — usually minutes, occasionally a few hours — the console detects them and marks the domain verified.
6. Warm up volume. Don't jump straight to full send volume on a brand-new domain. Ramp gradually over one to two weeks so mailbox providers build a positive reputation signal before they see your full traffic level.

Deliverability discipline

Authentication gets you in the door; ongoing hygiene keeps you there. Keep bounce rates low by validating addresses at capture and pruning hard bounces immediately — repeated sends to dead addresses are one of the fastest ways to tank sender reputation. Honour unsubscribe requests immediately and never re-add an unsubscribed address to a list. Never import a purchased or scraped list; recipients who never opted in generate spam complaints at a rate that damages deliverability for every other campaign running from the same domain, including transactional receipts and password resets.

Email alongside other channels

Because email lives in the same inbox as messaging channels, routing and team assignment work the same way: an incoming reply lands in the shared inbox, can be assigned to a team or agent, and shows the full cross-channel history for that contact. This makes it straightforward to use email for what it's good at — long-form content, attachments, formal confirmations — while keeping WhatsApp or SMS for time-sensitive nudges, without losing the thread between them.

Costs

Domain setup and verification are part of the standard onboarding; there's no separate fee to configure email itself. Once live, email message volume is metered the same way other channel traffic is — see the billing-and-plans article for current pass-through rates. The flat monthly connection fee covers keeping the channel connected and managed; it does not cover the message volume itself.

Steps at a glance

1. Choose a sending subdomainUse a dedicated subdomain such as mail.yourbrand.com to isolate reputation from your corporate domain.
2. Publish SPF and DKIMAdd the SPF include and DKIM CNAME records provided in the console to your DNS zone.
3. Set a DMARC policyPublish a DMARC record, starting at p=none and tightening to quarantine or reject once reports are clean.
4. Verify and warm upVerify the domain in the console, then ramp send volume gradually over one to two weeks.

Frequently asked