Before you change anything, see what the system is already telling you. Two places show whether your drips are sending. Each sequence's stats, under Squeeze Forms & SMS then Sequences, show how many emails have gone out and how leads are responding. If that count is not moving, the sequence is not sending to anyone. A lead's timeline, which you open from any lead in your CRM, shows whether that one person received an email and whether they are still enrolled or paused. Between the two, you can tell whether the problem is the whole sequence or just one lead. The checks below explain why. For the full email toolset, see SiteStakes email.

This is the most common cause by far. SiteStakes sends drips through your own email provider, and it will not send anything until one is connected. So check your provider connection first, under Integrations then Email. If the page says no email provider is configured, nothing will send until you connect Brevo, SendGrid, Mailgun, Postmark, or SMTP. Walk through it in setting up your email provider.

If a provider is connected but your emails are still not delivering, the provider is probably rejecting them. The usual reason is that your sender is not verified. Each provider asks you to verify a From address, or to authenticate your whole sending domain. You do that by adding SPF and DKIM records at your DNS host. Until that is done, your provider may refuse the message, or drop it into spam. The steps are in setting up your email provider.

A sequence only sends when its status is Active. Open it and check. If it is still a Draft, switch it on. Also note that drip sequences are a Grow and Pro feature, so on the Basic plan they will not run, and upgrading turns them on. More on building and activating sequences is in creating email drip sequences.

A sequence can be live and still send nothing if no leads are enrolled in it. Leads join through a form's automation, the start a drip action. If that automation is turned off, or the form people fill out is not the one wired to the sequence, the automation is not firing, so no one enrolls and no emails send. Check the automation on the form that should feed the sequence, then submit a test to confirm new leads enroll. You will see the sequence's enrolled count rise.

Drips do not send the instant a lead enrolls. Each scheduled email waits in a send queue, and a background process works through that queue every few minutes. Two things decide when an email is due: the delay you set on the step, and the sequence's send schedule. If the sequence uses a fixed time, a smart window, quiet hours, or a specific timezone, an email can sit stuck in the queue until that window opens. Check the step's delay and the schedule settings, and give it a little time before assuming it is broken.

If most emails send but one lead stopped getting them, look at that lead. Nurturing sequences pause automatically when someone replies or engages, so they stop receiving emails until the pause window ends. That is working as intended. Separately, if a lead's address has bounced or marked an email as spam, SiteStakes adds it to a suppression list and skips it on future sends to protect your sending reputation. Open the lead to see whether they are paused. A suppressed address simply stops receiving.

If a sequence's stats show almost nothing going out even though leads are enrolled, the problem is usually on the provider side. The usual culprits are an API key that was rotated or revoked, a provider account that is out of funds or has hit a sending limit, or a sending reputation that dropped after a high bounce rate or spam complaints. Sign in to your provider, confirm the account is in good standing, and confirm the API key SiteStakes has on file is still valid. Work through these checks in order, and you will almost always find why your drip emails are not sending — and the fix.