A customer signed up for a guide but is still waiting for it? A welcome automation delivers the agreed content after a new email signup. It does not send to an entire existing list or welcome everyone imported from a file.
Prepare the form and sender
You need a DropUI form that records email consent for the correct contact base, and an email sender configured for that same base. The first welcome does not require purchase history.
Test the form on the website. Seeing the person in Contacts does not prove that a new signup with consent occurred.
Configure the welcome
Choose Welcome after signup, then the store or contact base. Complete the recipient and message steps using the automation setup guide.
In DEMO STORE, the message leads to a skincare selection guide. Match what the form promised: if someone requested a guide, an unrelated promotion does not fulfil that request.
In Sending, set the delay to 0–1440 minutes after signup. Zero adds no intentional delay; queue and sending requirements still apply.
Enable it before new signups
Check the settings and use Save and enable. New email consent from a DropUI form after activation can qualify. Manual additions, file imports and another submission by an already subscribed person do not generate another welcome.
A new signup after an earlier opt-out can be a separate event. Do not manually restore consent just to force a message.
Example customer message
Anna signs up for a skincare guide. The welcome email takes her directly to that guide. A delay of 0 minutes adds no waiting period, although the sending queue still applies.
Investigate a missing welcome
Open activity history. Compare activation time, signup source, contact base and current consent. Also check the sender and available allowance.
A second email after no purchase has additional requirements. That step needs store purchase data even when the first welcome can work without it.

