Documentation

Filing the emails you send yourself

You write to a customer from Gmail, Outlook or Apple Mail — wherever your mail already lives. Put one address in BCC and that email lands on the customer's record in Kicklace, as sent by you. Nothing is connected, no account is linked, and nothing about your mailbox changes.

You write to a customer from Gmail, Outlook, Apple Mail — wherever your mail already lives. Put one address in BCC and the email lands on that customer's record in Kicklace, as sent by you. Nothing is connected, no account is linked, and nothing about your mailbox changes.

Written 2026-09-08 for #208. The full Gmail integration (#178) is a separate thing and waits on Google's own verification; this needs nothing from anybody.

Where to find the address

Settings → Sending → Replies → File the emails you send yourself. It looks like this:

log+ws_k3f9a2m8.4c1b7e9a0d2f@reply.your-domain.com

It belongs to the workspace, not to you, so it is the same address for everyone on the team and it does not change. Copy it once and let your mail client remember it.

It only exists once the reply subdomain is verified — the same subdomain that takes replies, set up a few lines above it on the same screen. Until then the screen says so and shows no address, because an address that would bounce is worse than no address at all.

If your workspace takes mail on its own domain rather than on a subdomain (#227, docs/support-inbox.md), the address is on that domain instead — log+…@your-domain.com — and works in exactly the same way. It is found by its signature, not by the domain it is on, so nothing about this page changes.

Putting it in

Gmail. Press Bcc on the compose window and paste it. To have it there every time: Settings → See all settings → General → Create contact for auto-complete, or simply save it as a contact named "Kicklace" — Gmail will offer it as soon as you type "kick". There is no per-account auto-BCC in Gmail itself; Google Workspace administrators can set one for the whole domain under Apps → Google Workspace → Gmail → Compliance → Content compliance, which BCCs every outgoing message.

Outlook. Paste it into the Bcc box (Options → Bcc if the box is not showing). For every message: File → Manage Rules & Alerts → New Rule → Apply rule on messages I send → next with no condition → Cc the message to people or public group — Outlook's rules have no Bcc action, so this puts the address on the visible Cc line, which works the same way here but the customer can see it.

Apple Mail, Thunderbird, HEY, anything else. Bcc, Cc and To all work. Bcc is the one nobody else sees.

What lands

One row on the customer's timeline, reading Sent with your name on it, exactly like an email sent from Kicklace's own composer: the subject, the words of the message, and the day. The customer's Last activity moves forward, and any automation that waits on an email going out hears it, so "three days after we write, remind me" works whether the email left from Kicklace or from your laptop.

An address Kicklace has never seen becomes a person with an email and nothing else — on no list, with no consent record, so nothing may be sent to them for it.

If you wrote to several people at once, the email is filed on each of them.

What does not happen

Nothing is ever sent back. Kicklace does not reply, acknowledge, or forward.
Nobody is put on a list. Filing an email is not permission to email anybody.
Nobody is notified. You wrote to a customer and Kicklace wrote it down; that is not news.
Nothing is deleted or changed on the record beyond the new row and the activity date.

What is refused

Every refusal shows on Settings → Your website → Your website's heartbeat, in plain words, so nothing is lost quietly.

What arrived	What happens
The sender is not a member of the workspace	Refused: Not a member here, so nothing was filed. The address is on the outside of every email you send, so anybody could find it — only a member's own address may file mail.
The email was addressed to nobody but Kicklace	Refused: Nobody was on that email but Kicklace, so there was nobody to file it on.
More than 25 people were on the email	The first 25 are filed and the heartbeat says the rest were not. A mailing that size belongs in a broadcast, which carries a list's consent.
More than a hundred new people have arrived by mail today	The rest of the email waits for tomorrow. The cap is on people Kicklace has never seen; customers already here always land.
The address's signature does not hold	Ignored. Every address is signed with the deployment's own secret, so a guessed one files nothing.

The same delivery arriving twice — a retry, a replayed webhook — is filed once.

How it works, for anybody who asks

Kicklace already receives mail on your reply subdomain (#170). The BCC address is a second address on that same subdomain, log+<workspace id>.<signature>@<reply domain>, signed with HMAC-SHA256 under the deployment's secret, so it can be published on the outside of an email without anybody being able to forge one for another workspace.

A BCC'd address is in the SMTP envelope and not in the message's headers — that is what makes a blind copy blind. Resend's received-email payload carries the envelope in received_for, "the recipient addresses the email was forwarded for, taken from the for clause of the message's Received headers" (API reference, webhook), which is where the address turns up. The people are read off To, and off Cc when the email was addressed only to us.