Email delivery
Email delivery provider model
Understand what AttuneMail manages, what your team configures, and how provider costs stay separate from customer-facing workflow design.
Updated 2026-08-235 min
Shared responsibility
| AttuneMail manages | Your team manages |
|---|---|
| Delivery integration, queueing, retries, and outcome processing | Your sending domain and DNS access |
| Provider credential protection and operational routing | Approved From addresses and reply handling |
| Bounce and complaint signal processing | Consent, audience policy, content, and campaign approval |
| Workspace usage and safety controls | Accurate business identity and lawful sending purpose |
Standard workspace setup
Regular workspace setup does not require customers to paste delivery-provider credentials. Add and authenticate your sending domain, create an approved sender, send a controlled test, and then schedule within the displayed readiness and warm-up limits.
Enterprise delivery requirements
Dedicated routing, contractual isolation, regional constraints, or an existing provider relationship require an implementation review. Treat them as architecture and operations decisions rather than exposing provider-specific settings to every campaign user.
- ✓Document volume, peak rate, recipient geography, and email categories
- ✓Separate transactional and lifecycle risk when appropriate
- ✓Define bounce, complaint, retry, and incident ownership
- ✓Test failover and reporting before production cutover