Adding an Account
An account is the mailbox mail is sent through, with the credentials to reach it.
Where to find it
Architect Panel → Integration & Connections:
- E-mail Accounts — the accounts mail is sent and received through
Architect Panel → Activity:
- E-mail Log — every message sent, with its result
Architect Panel → Layout & Pages:
- E-mail Templates — templates that send through it
What an account holds
- A from address and a from name.
- The connection details for its type.
The from name is what people see
In most mail clients the name is prominent and the address is not shown at all until somebody looks. So the name is doing the work of telling a recipient who this is from.
Use the organisation's name as people know it, not an internal one. "Notifications" from an unfamiliar system is deleted; the same message from a recognised organisation is opened.
Use an address you collect from
People reply. An address nobody monitors discards those replies silently, and the sender concludes they were ignored.
Several accounts, deliberately
Different purposes often want different addresses — transactional mail from one, campaigns from another, alerts from a third. That is worth doing for two reasons: recipients get a sensible from address, and a deliverability problem with one does not affect the others.
Keep the number small enough that each has an owner.
Organisational credentials, always
Never a person's mailbox or password. It breaks when they leave or change their password, and it attributes the platform's mail to them.
The domain configuration matters more than anything here
Receiving servers check whether your domain authorises this sender. Without that, your mail is treated as suspicious regardless of how correctly the account is configured.
That is the single biggest factor in whether your mail arrives, and it is configured at your domain rather than in the platform. Confirm it before concluding you have a sending problem — it is the cause more often than anything on this screen.
Test to several providers
Send to accounts at the mail providers your recipients actually use, and check whether the message landed in the inbox rather than merely being accepted. Corporate filters and consumer spam folders behave differently, and a send that "worked" to your own mailbox proves little.
Watch for credential expiry
Modern providers expire credentials and tokens. An expired one stops all mail through that account at once — usually noticed when somebody asks why a customer never got something. Diary any expiry you know about.
Worked example
An organisation runs two accounts: one for transactional mail from a monitored support address, one for campaigns. Both use organisational credentials, both from names use the trading name customers recognise. Domain authorisation was confirmed before launch, and test sends to four providers all reached the inbox.
Recommendations
- Use a from name people recognise.
- Send from an address you collect from.
- Confirm domain authorisation before blaming the account.
- Test to real providers, and check the inbox not just the send.