Elaine is designed to integrate closely with a customer's own domain infrastructure. For email, this means using approved customer domains for sending and relevant link targets instead of presenting Elaine as an unrelated sender. The customer must explicitly authorize this integration by publishing or confirming the required DNS configuration.
Domain onboarding for a new tenant
- Customer and implementation teams identify the domains and subdomains intended for sending, tracking, links, and other relevant email functions.
- Elaine provides the DNS records required for the agreed setup.
- The customer or its DNS provider publishes these records for the desired domains. This step confirms that Elaine is allowed to use the domain configuration.
- The approved sending domains and relevant link-target domains are configured in Elaine so their permitted use can be governed.
- The configuration and domain readiness are verified before production sending begins.
A domain should not be used for production email merely because it exists in a campaign field. It must be approved, configured, and technically ready for the intended purpose.
Responsibilities
| Responsibility | Typical owner |
|---|---|
| Approve the use of customer domains and publish the requested DNS records | Customer domain or IT team |
| Provide the environment-specific records and configure approved sending and link-related domains in Elaine | Elaine implementation or operations team |
| Agree changes, verify readiness, and coordinate production activation | Shared responsibility |
Deliverability after onboarding
Correct domain setup establishes a necessary technical foundation, but it does not guarantee inbox placement. Consent, list quality, complaints, bounces, engagement, content, links, volume, cadence, and sudden sending-pattern changes continue to influence deliverability.
- Use permission-based contact acquisition and honor suppressions and unsubscribe decisions.
- Test sender information, reply path, content, links, rendering, and unsubscribe behavior.
- Monitor bounces, complaints, engagement, blocks, and unusual provider patterns.
- Coordinate new domains, large volume changes, and warm-up plans with the responsible teams.
Guiding principle: Elaine integrates as closely as possible with the customer's infrastructure. The customer retains control of its domains and must explicitly enable and confirm their use through the agreed DNS and onboarding process.