Skip to content

Documentation

Email

Who you can email, how it gets there, and how people say no.

One rule runs through all of it, and there's no setting that turns it off:

Kicklace only emails somebody who asked, or who got in touch first. Somebody who joined a list gets what that list is for. Somebody who bought, signed up, wrote in or replied can be written to about that. Nobody else gets list email, whether they were imported, bought or only seen by the tag.

Where email is written

There's no separate Email page. An email is written where it goes out:

  • On your Lifecycle map. Each stage's sequence holds the emails people get when they reach it. The Lifecycle has the map and its rules.
  • In Mail. Write to anybody, one to one, the way you would from your own mail program.
  • From a person's record. Email writes to that one person.
  • To a list. A list's page sends one email to everybody on it.

Lists and the words people agreed to

A list is a reason to write to somebody, like Product updates or The waitlist. Every sign-up keeps the exact sentence the person agreed to, word for word, with the day and their IP address. That record is the proof, and it stays even after somebody leaves the list.

People join a list through a form on your site that Kicklace hears, a form Kicklace hosts for you (Your website and its forms), a Join button in one of your emails, or an import where you type the sentence they agreed to (Moving from another CRM). A sign-up without the sentence is refused, however it arrives.

Every list email says why the person is getting it and carries an unsubscribe link that's theirs alone, plus the header that puts an unsubscribe button in their own mail app. It also carries your postal address, which the law asks for. Set it once under Settings → Styles; a list email won't go without it.

Leaving a list is one click, and a page of their own lets them leave any of your lists. Nothing puts them back but their own yes: an import, a teammate or Ask can't, and signing up again sends them an email. They're back once they press the link in it. The same goes for anybody who marked one of your emails as spam.

Your map's three kinds of email

Each sequence on your map sends one kind:

  • Account emails, like a failed payment or a trial ending. They go unless the address bounced or the person complained.
  • Tips and check-ins. They carry Stop these emails, one click.
  • List emails, only to people on the list, with the list's own unsubscribe.

Reaching a stage never puts anybody on a list. An email can carry a Join button for one of your lists instead, and they tick its sentence themselves.

One email to a whole list

From a list's page: write it, preview it as real people on the list, then send now or pick a time. It goes to whoever is on the list when it sends, so somebody who leaves before then doesn't get it. A time is in your own workspace's day and goes out within the hour after.

Each copy lands on the person's record, and afterwards the email's own page shows what happened: delivered, opened, clicked, bounced, and who left the list since. Only owners and admins send to a list.

One to one

Mail writes to anybody. Type a name to find somebody already here, or any address. Somebody new is kept as a contact, in Mail and in search but not on your map, until they do something a customer does. Only an address that bounced, or somebody who marked you as spam, is still turned away.

Replies

Replies go to your own email address until you set up replies on your own domain. After that they come back into Kicklace, on the person who wrote. Replies and your inbox has the setup.

Kicklace never answers anything by itself. A reply is written down and you're told; what happens next is yours.

Sending from your own address

Until you add your domain, Kicklace sends from its own address with your name in front of it. Settings → Sending walks you through your own, in four steps:

  1. Domain. Your domain, the DNS records to add, and Check DNS, which says what it found in plain words.
  2. Defaults. The name and address your email comes from, the reply-to, and a test to yourself.
  3. Replies. A subdomain that takes replies, like reply.your-domain.com.
  4. Inbox. An address anybody can write to, like help@your-domain.com.

From then on your email comes from you. Kicklace checks your domain again every day and tells you if it stops working.

If you already send with Resend, you can skip the DNS: connect your own account and pick a domain you verified there. Your own Resend account says how.

How much you can send

Through Kicklace's sender, 50 emails a day until your own domain is verified, then 500. Through your own Resend account there's no limit of ours. An email to a list that would go past what's left today is refused before it starts, and says so. The count starts again at midnight UTC, and a test never counts.

Bounces and complaints

When an address bounces for good, or somebody marks your email as spam, Kicklace takes them off every list in your workspace, notes it on their record, and tells you. Nothing is sent to that address again. A full mailbox or a server having a bad day is noted and nothing else.

Only a new yes from the person clears a complaint. A hard bounce never clears, because the address itself doesn't work.

What never happens

  • No cold email. There's no way to email a list you bought.
  • No email because an AI asked. Ask Kicklace and Claude can write a draft. Sending is always a person pressing send. Ask Kicklace has the rest.
  • No email people can't leave.

From your own code

Your servers can write to one person through Kicklace too, with the same rule: only somebody who has been in touch. The API reference has POST /api/v1/messages.

Guides

What to write, email by email: a welcome email, a failed payment email, a trial ending email and a win-back email.