Let the platform do the work

Determining the Best Method to Send Confirmation Emails

Overview

You can automatically send confirmation emails in Sugar Market through both nurtures and auto-responders through a form submission rule. This article describes the difference between the two and how to choose the best method for your needs.

Additional Actions vs. Immediate Response

If you want to take additional actions based on the email send, then a nurture is your best choice. Adding a prospect to a nurture provides the most flexibility since it can trigger several actions based on the email send, such as resending the email if it is not opened within a defined period of time.

If you want the email to be sent immediately after the form submission, using an auto-responder is the best choice. Emails sent from nurtures can take up to fifteen minutes to be triggered from a form submission. When using an auto-responder, you can also define an action to add the contact to a nurture, but you will not be able to create conditions on the auto-responder to track opens and clicks.

Confirmation Emails for Multiple Form Submissions

Auto-responders can be triggered multiple times, so if a contact submits your form more than once, they will receive the triggered email after each form submission. You can configure your nurture to do the same with Nurture Builder 2.0, but if you are using the legacy Nurture Builder, you can only send an email to a contact once, even if the contact submitted a form multiple times. 

Examples

The following examples demonstrate different use cases for sending confirmation emails:

Use Case Recommended Method
Send a confirmation email to contacts who submitted your webinar registration form to provide them a link to the webinar. Auto-responder
Send emails introducing the event, a reminder, and a recording of the webinar to attendees as a follow-up. Nurture
Send a response to a support request. Auto-responder
Send a response to a contact's request to download your white paper. Auto-responder or Nurture (not legacy)