CRM Email Sender Setup: Domain, Identity & Reply Checks

What should you verify before sending CRM email?

Verify the sending provider and domain, the From identity, the Reply-to destination and the recipient's intended communication. Send to a controlled address and inspect the received message and reply path. In Chirply, provider connections and branded sender identities are configured separately; optional sending pools add another reply-routing layer.

Check the provider, identity and reply path

A provider connection identifies the service handling delivery. A branded sender supplies the From address and name the recipient sees. Reply routing determines where the answer goes. Review each layer separately so a successful provider connection does not become an assumption that every sender and reply path is ready.

Use the provider's current domain-verification instructions for the exact records it requires. Copy the values from that provider's account rather than borrowing another business's DNS example. Keep an ownership record of who can manage the domain and the connected service.

The worksheet records configuration decisions and test results. It is suitable for sender names, domains and responsible roles, while secrets stay in the supported connection flow. Provider delivery status and inbox placement are different observations; record the actual result of your controlled test.

Connect and verify a branded sender

Set up the identity used by the real message path, including any pool that path selects.

1. Open Settings → Integrations → Email providers & identities. Select the supported provider connection you intend to use, such as Mailgun or Resend.
2. Enter the connection name, verified sending domain and required provider credential through the product's connection form. Choose Connect and verify provider.
3. Use Add branded sender to configure the From address, visible From name and Reply-to. Review which connection sends and which receives replies.
4. If using a pool, open Settings → Email pools & warmup and inspect its member addresses and Replies go to setting. A pool reply destination overrides its members' individual reply destinations.
5. Prepare a short message to a controlled recipient using the intended sending path. Verify the selected identity and any merge fields before sending.
6. Inspect the received From details, links and reply destination. Reply from the controlled address and confirm the team can find and handle the response. Record both directions in the worksheet.

Treat pacing as a configured operating limit

Chirply's warmup settings can gradually increase a sender's daily allowance for pool rotation. The defaults are 10 on day one, adding 10 per day, and levelling off at 200 per day. Choose actual values for your operating plan and provider requirements; these defaults are not a deliverability guarantee.

The allowance and sent counts use UTC days. A pool selects among enabled members and skips those already at their allowance. The cap governs pool rotation, so inspect the actual send path when investigating a message sent outside the pool.

For an illustrative two-address team, give the pool a shared reply destination only when that inbox has an assigned owner. Test a reply from messages sent by both members. Document whether the receiving team sees one shared queue or separate conversations.

Use the returned result to choose the next fix

If connection verification fails, inspect the exact provider and domain result. If sending fails, confirm the selected sender is enabled and the provider returned an actionable response. If delivery succeeds but replies are absent, inspect Reply-to, the pool override and the receiving connection.

For inbox-placement issues, review authentication, recipient expectations, content and the provider's current guidance. Correct the specific finding and repeat a controlled test. Keep subscription scope and provider usage costs visible in the account's implementation record.

Common questions