Email & inbox

Why does an email address say Bounced, and how do I clear it?

The address could not receive mail, so automated email to it is paused. Click the X on the Bounced badge to clear it once you know it works.

It means an email to that address could not be delivered because the address does not exist or no longer accepts mail. Coastline stops sending automated email to it (sequences, automations and broadcasts) until you clear the flag. Emails you write yourself still go out.

Where you see it

  • On the contact, next to the address. Hover the Bounced badge to see the date it bounced.
  • When you enroll the contact in a sequence from the contact page.
  • In a broadcast's review list, in the Status column.

What happens when an address bounces

  • Any sequence you were running to that address stops, and the contact's Activity tab says which sequence stopped and why.
  • Later sequence steps, automations and broadcasts skip the address.

Coastline only flags an address when the receiving mail server says it does not exist or has been shut down. A full mailbox or a temporary problem does not count.

Clear the flag

If the address was simply misspelled, edit the contact's email instead. The corrected address is not flagged.

Clear the flag only when you know the address works again, for example because the customer confirmed it.

  • On the contact: click the X on the Bounced badge.
  • When enrolling from the contact page: click Clear bounce and enroll.
  • In a broadcast: click the X on the Bounced badge in the review list. The contact moves back to Will receive.
  • When enrolling from a sequence: in the Enroll a contact list, click the X on the Bounced badge before you enroll. A contact still flagged when you click Enroll is skipped.

The contact's Activity tab records who cleared the flag. If the address bounces again, Coastline flags it again.

For more on how sequences stop, see email sequences. For the other reasons a broadcast leaves someone out, see why contacts are skipped from a broadcast.

Was this article helpful?

Still need help?

Submit a ticket and a human will get back to you.

Contact support