What Email Supports
- Verified sending domains.
- Default from name and local part.
- Reply-to and support mailbox settings.
- Inbound receiving through a Woes forwarding address or a verified sending domain.
- Operator replies from the shared inbox.
- Notification email delivery.
- CSAT and NPS survey emails.
Configure Email
1
Open Settings → Channels → Email
Review current domain state and email defaults.
2
Add a domain
Add the domain Woes should send from.
3
Verify DNS
Complete the DNS records shown in Woes and wait for the domain to become verified.
4
Set routing defaults
Configure the local part, sender name, reply-to, and support mailbox.
5
Send a test
Use a real verified-domain test email before relying on production support flows.
DNS Records To Expect
Woes shows the exact DNS values for your domain, but the records usually fall into these groups:
Use a subdomain such as
support.example.com when the root domain already has
MX records for Google Workspace, Microsoft 365, or another inbox provider.
Inbound Email
Email support accepts messages after you choose an answering agent and set up an intake path. You can forward mail to your Woes forwarding address, or verify a domain so customers can write to your own support address. After setup, send a real email to the configured support address and confirm it appears in Inbox as an email conversation. Then reply from Woes and confirm the customer receives the response from the expected sender.Inbound Behavior And Diagnostics
Woes routes inbound email by the verified support address. Messages that cannot be matched to one workspace are skipped instead of guessed. Retries from mail providers should not create duplicate customer messages. If an email does not appear in Woes, check:- Email support is enabled.
- An answering agent is selected.
- The forwarding address or custom support address is correct.
- The sending domain is verified when you expect Woes to reply from your domain.
- The message is not empty, automated-only, or sent only through
Cc/Bcc.