How to organize ISP email management: inboxes, aliases, and deliverability

Email aliases in Splynx are here. In this post, we’ll walk you through how to organize your ISP’s email communication: route incoming messages to the right team, send from department-specific addresses, and keep everything compliant with modern deliverability requirements. We’ll also explain why we dedicated the time to building this frequently requested feature.

Inboxes: route incoming email to the right team

Before thinking about sending, start with receiving. When a customer emails your ISP, that message needs to reach the right person, not sit in a shared pile.

Splynx inboxes let you connect multiple email addresses and route incoming messages to specific teams. Each inbox maps to an IMAP mailbox and can be assigned to a group of agents. When an email arrives at support@yourisp.com, it lands in the Support group’s queue. An email to billing@yourisp.com goes to Finance.

You can set up auto-assignment rules so tickets created from incoming emails are distributed among agents in that group. No manual sorting, no messages falling through the cracks.

This is where the foundation of your communication structure lives. Set up your inboxes first, then layer outgoing aliases on top.

Set up inboxes in the documentation →

Email aliases: send from the right address

This is the feature ISPs have been asking for. Instead of every outgoing email coming from a single address, you create aliases that match your departments:

• admin@yourisp.com for general communication
• sales@yourisp.com for lead follow-ups and outreach
• support@yourisp.com for ticket replies and WhatsApp notifications
• billing@yourisp.com for invoices, payment reminders, and billing alerts

Each alias is configured under Config → Main → Email with a sender name, sender email, and a category that controls which automatic notifications it handles:

When Splynx sends an invoice, it looks up the Finance alias and uses billing@yourisp.com as the sender. When a ticket auto-reply goes out, it uses the Support alias. Each department gets its own sender identity without any manual work per message.

For multi-brand ISPs, aliases can be linked to specific partners. Partner A’s customers see emails from Partner A’s address. Partner B gets their own.

Configure email aliases in the documentation →

“Send from” picker: choose the right alias every time

Automatic notifications pick the correct alias based on category. But when your team sends manual emails, they need to choose.

A “Send from” picker now appears when agents:

• Reply to a support ticket
• Send a message to a lead
• Run a mass email campaign

The picker shows available aliases as sender@email.com (Category), so agents see exactly which identity they’re using and can switch with one click.

When an incoming email arrives on a specific alias, Splynx remembers it. All replies from your team go out through that same address automatically. The customer sees one consistent sender throughout the entire conversation.

Learn more about email messages in support →

Deliverability: stay out of the spam folder

Separate aliases help your sender reputation, but there’s more to deliverability. Since February 2026, Gmail and Yahoo require bulk senders to support one-click unsubscribe and authenticate with SPF, DKIM, and DMARC.

Splynx handles the first part automatically. Every outgoing customer email now includes List-Unsubscribe and List-Unsubscribe-Post headers (RFC 2369 + RFC 8058). Gmail and Yahoo show a native “Unsubscribe” button next to your sender name, so subscribers opt out cleanly instead of hitting the spam button.

For SPF, DKIM, and DMARC, you configure DNS records on your sending domain. The documentation includes setup instructions and a verification checklist.

Set up email deliverability (SPF, DKIM, DMARC) →

Putting it all together

Here’s what a fully configured ISP email setup looks like:

Incoming and outgoing work together. A customer emails support@yourisp.com. The message creates a ticket in the Support group. An agent replies, and the response goes out from support@yourisp.com automatically.

You can track which alias sent each email in Administration → Logs → Email, where a Sender column shows the mailbox used for every message.

Getting started

The setup takes three steps:

1. Connect your inboxes under Config → Helpdesk → Inboxes. One per department, each assigned to a group. Documentation →
2. Create your aliases under Config → Main → Email. Match them to the same addresses and assign categories. Documentation →
3. Publish DNS records (SPF, DKIM, DMARC) for each sending domain. Verification guide →

If your ISP already sends email through Splynx, your existing SMTP settings are migrated into the new structure automatically. Nothing breaks on upgrade. For those new to Splynx, feel free to book a demo online.