> ## Documentation Index
> Fetch the complete documentation index at: https://docs.arcuserp.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Email Configuration
> Use Email Configuration settings to control sender identity, reply routing, branding, customer notification toggles, custom sending domain setup, and test-send verification.
Email Configuration controls customer-facing messages. Test sender identity,
reply routing, branding, and notification toggles before relying on them for
quotes, invoices, orders, receipts, refunds, statements, and reminders.
## Open Email Configuration
1. Open **Settings**.
2. Choose **Entity Settings**.
3. Open the **Documents and Email** group.
4. Choose **Email Configuration**.
## Email Identity
Email Identity controls the header and branding customers see when Arcus sends
messages for the entity.
Set:
* **From Email**: the sender address customers see when the sending domain supports it.
* **Reply-To Email**: where customer replies should go.
* **Company Name**: the display name used in outgoing email.
* **Support Email**: the support contact shown in email copy and templates.
* **Email Logo**: the logo shown at the top of customer-facing emails.
* **Footer Text**: the footer included at the bottom of outgoing emails.
Use a monitored Reply-To address. If replies go to an unmonitored mailbox,
customers may answer an invoice, quote, or shipment notice without anyone seeing
it.
## Postmark Health
The health badge checks whether Arcus can reach the configured email sender. If
the badge shows a problem, test sends and customer messages may fail or fall
back depending on configuration.
If Postmark is unreachable:
1. Retry the health check.
2. Confirm the entity has an email connector configured.
3. Confirm the sending domain is verified when using a custom domain.
4. Send a test email after the health check is healthy.
5. Review the Email Log if a real customer message was expected.
## Notification Preferences
Notification toggles decide which customer events automatically create outgoing
emails. Disabled events can still appear in the communication history as skipped
or not sent, depending on the workflow.
Arcus groups notification toggles by type:
* **Transactional emails**: order confirmations, shipment notices, delivery notices, invoices, payment receipts, refund receipts, quotes, and backorder updates.
* **Lifecycle emails**: account welcome and credit memo lifecycle messages.
* **Reminders**: payment reminders, card-expiring notices, and credit memo expiration reminders.
* **Digests**: monthly AR statements. These default off and should be enabled intentionally.
**Do not disable transactional emails casually**
Turning off invoices, receipts, shipment notices, or refund receipts can create
customer support gaps. Confirm the team has another process before disabling
them.
## Custom Sending Domain
A custom sending domain lets customer-facing email use your own domain. Arcus
recommends a subdomain such as `mail.yourcompany.com` so you do not disturb the
root domain that already handles normal employee mail.
Typical setup:
1. Enter the sending domain.
2. Register the domain.
3. Add the DNS records shown by Arcus at your DNS provider.
4. Verify the domain after DNS has propagated.
5. Send a test email and confirm From, Reply-To, logo, and footer.
If verification is pending, emails may still use the platform sender or may not
send from the custom domain yet.
## Send A Test Email
Use **Verify Configuration** after saving changes.
1. Save Email Configuration.
2. Enter a test recipient.
3. Click **Send Test**.
4. Confirm the message arrives.
5. Confirm the From address, Reply-To address, logo, footer, and company name.
6. If the test does not arrive, review Postmark health, the custom domain status, and Email Log.
Use a mailbox outside your company domain during setup. That catches sender,
reply, and domain-authentication problems that internal mailboxes may hide.
## Delivery Troubleshooting
When a customer says they did not receive an email:
1. Confirm the notification toggle for that message type is enabled.
2. Confirm the related email template is active when the template supports enablement.
3. Confirm the customer email address is correct.
4. Check whether the customer unsubscribed from optional emails.
5. Review the Email Log for sent, skipped, failed, bounced, or delivered status.
6. If delivery shows success but the mailbox cannot find it, have the customer's email admin check quarantine, filtering, and tenant rules.
## Common Blocks
* **Test email fails**: check Postmark health, custom domain verification, and sender configuration.
* **Replies go to the wrong team**: update Reply-To Email and Support Email.
* **Logo looks blurry**: upload a sharper logo and send a test email.
* **Customers still get a disabled message type**: confirm whether the email is transactional, whether a template is active, and whether another workflow is sending a different message.
* **Monthly statements are not sending**: statement emails default off. Enable the digest toggle and confirm the statement workflow is active.
* **Custom domain stays pending**: DNS may not have propagated, or the record may be added at the wrong host.
## Related Articles
Preview, edit, test, reset, enable, and disable customer-facing email templates.
Review delivery status, resend messages, and troubleshoot customer email history.
Understand how email configuration fits with PDF text, numbering, templates, and quote settings.
Understand customer preference links, unsubscribe behavior, resubscribe, and transactional email limits.