Lead Capture Email Verification

Lead capture campaigns can optionally verify a visitor email before the lead is stored, alerts are sent, webhooks fire, or campaign email rules run.

Modes

EMAIL_REPLY_YES confirms mailbox/control-path access. It does not prove legal identity.

Reply YES With 10x Defaults

EMAIL_REPLY_YES can use the 10x-managed verification sender and template. To use the managed default, enable verification on a LEAD_CAPTURE campaign with:

{
  "leadVerification": {
    "mode": "EMAIL_REPLY_YES"
  }
}

The campaign response keeps senderId and templateId as null. 10x sends the verification email through its managed SES sender, and replies still go to the platform-managed reply domain.

Custom Sender Setup

Use a custom sender/template only when you want the verification email to come from your own verified domain or use your own copy.

1. Verify the sending domain in the email platform.
2. Create a sender profile with purpose LEAD_VERIFICATION.
3. Wait until the sender profile and identity are READY.
4. Create an ACTIVE email template.
5. Enable verification on a LEAD_CAPTURE campaign with both senderId and templateId, plus optional ttlMinutes.

For EMAIL_REPLY_YES, senderId and templateId must be supplied together. Omit both to use the 10x-managed default.

Reply YES Template Contract

Reply YES templates are regular 10x email templates sent through SES. Do not create SES-native templates.

Required body variables:

Supported variables:

Example text body:

Reply {{replyKeyword}} to this email within {{expiresInMinutes}} minutes to confirm your request.

Campaign: {{campaignId}}
Page: {{pageUrl}}

Platform Reply Domain

Reply YES uses a platform-managed reply domain such as reply.10x.in or a stage-specific equivalent. Each pending lead receives a tokenized Reply-To address like:

verify+<token>@reply.10x.in

The token maps the inbound SES reply back to the pending lead. The submitted lead is only finalized when the reply contains a clear affirmative first line such as YES, YES., YES!, YES please, or Y.

Coupon Fulfillment After Verification

Verified lead capture can also gate campaign coupon fulfillment. In that flow, the lead is captured after EMAIL_OTP or EMAIL_REPLY_YES succeeds, normal lead side effects continue, and only email rules marked requiresCoupon: true wait for a customer coupon webhook.

See Campaign Email Automation Through 10xDotIn for the coupon webhook request, response, signature, cache, and retry contract.