Follow up on quiet threads with a single Gmail label.

You send a proposal on Tuesday and tell yourself you’ll nudge them on Friday if they go quiet. By Friday, it’s buried under eighty newer emails. With comail, you tag the conversation co:follow-up right when you send it. Your agent watches the live thread, checks whether they’ve replied, and—only if you’re still waiting—drops a tailored follow-up straight into your Gmail Drafts.

Takes a minute to apply. No credit card required.

follow-up1 thread labeled co:follow-up

You → Maya Lin <maya@northstar.co> · Tue 4:18 PM

Q2 design & build proposal — Northstar

  • Labeled co:follow-up in Sent — agent notified immediately
  • Email mentions “after Thursday’s leadership sync” → check set for Friday
  • Re-checked Friday 9:30 AM — still 0 replies in thread

get_threadstill waiting

Gmail Drafts · threaded reply to maya@northstar.co

Re: Q2 design & build proposal — Northstar

“Hi Maya — hope Thursday’s leadership sync went well. Wanted to see if any questions came up on the Q2 scope or timeline before we lock in the April start date.”

create_draftdrafts only · you hit send

Label the thread when you send it. If Maya hasn’t written back by Friday, a follow-up that references what you actually discussed is waiting in Gmail Drafts.

The problem

Deals stall in the gap between “sent” and “replied.”

Most tools for following up make you forward emails to a third-party bot address, set up rigid mail-merge timers, or hand an AI assistant your entire inbox.

01

Forwarding and BCC bots split the thread

Forwarding an email to an external bot address gives the bot a frozen snapshot. When the client replies to your real thread two days later, the forwarded copy never sees it—and the bot drafts an awkward nudge to someone who already answered.

02

Fixed timers don’t read what you wrote

A dumb 72-hour reminder doesn’t know you wrote “no rush until after your board meeting next Tuesday.” And when a reminder resurfaces the thread at 5 PM on Friday, you still have to re-read the conversation and write the follow-up yourself.

03

Full-inbox bots don’t know who not to nudge

Pointing an unconstrained agent at your Sent folder and asking “who owes me a reply?” exposes every private thread in your mailbox—and risks pestering an investor, candidate, or customer who shouldn’t be rushed.

How it works

Tag the thread in Gmail. Let your agent watch the clock.

  1. Create a drafts-only follow-up agent

    Create an agent named follow-up in comail. It starts in allow-list mode with sending, trashing, and inbox changes turned off—so it can only read threads labeled co:follow-up and save replies to your Gmail Drafts.

  2. Label any conversation you want tracked

    Apply co:follow-up in Gmail on your laptop or phone—even to a message you just sent. Calling create_notification_url with include_sent: true notifies your agent the moment the label goes on.

  3. Read the thread and schedule the check

    Your agent calls get_thread to read the exchange. If you promised a specific day (“I’ll check back Friday”), it schedules its check for then; otherwise it uses your default cadence, like three business days out.

  4. Re-read the live thread before drafting

    When the timer fires, the agent calls get_thread again. If the other person replied in the meantime, it removes co:follow-up and stands down. If the thread is still quiet, it saves a reply in Gmail Drafts for you to review and send.

follow-up — claude

> Watch co:follow-up (including Sent). Check back in 3 business days—or when the email says—and draft one nudge if they haven’t replied.

comail · create_notification_url (include_sent: true)

Listening for newly shared threads · renews hourly

notification mailbox: mbx_7f3a91 · message: msg_4d90a2

comail · get_thread (thread_id: "thr_4d90a2")

To: Maya Lin <maya@northstar.co> · “Q2 design & build proposal”

“…happy to walk through it after Thursday’s leadership sync.”

Mentions Thursday’s sync. Scheduling check for Friday 9:30 AM.

Friday 9:30 AM scheduled check · 2 threads due

comail · get_thread (thread_id: "thr_4d90a2")

1 message · no reply from maya@northstar.co

comail · create_draft (thread_id: "thr_4d90a2", body: "Hi Maya — hope Thursday’s leadership sync went well…")

draft_id: "d-8814" · saved in Gmail Drafts

comail · get_thread (thread_id: "thr_3b19c0")

2 messages · reply from sam@acmecorp.com on Wed 11:04 AM

Sam already replied on Wednesday. Clearing follow-up label.

comail · unlabel_thread (thread_id: "thr_3b19c0", label_ids: ["Label_9041"])

ok

Because the agent re-reads the live Gmail thread when the timer fires, it skips anyone who already wrote back and only drafts a reply when the thread is still quiet.

Permissions

Share the conversation. Keep the Send button.

Your follow-up agent only sees the threads you hand it and can never send an email on its own or touch the rest of your inbox.

Client follow-through

follow-up

An allow-list agent that sees nothing unless you label it co:follow-up. It can read those threads, save reply drafts, and remove its own label when done—nothing else.

follow-up permissions
view allow co:follow-up
view deny default
send deny drafts only
attachments deny filenames only
archive deny —
spam deny —
trash deny —

In Gmail

You stay in control of every thread.

Call off a follow-up in one click. If a client answers you on Slack or over the phone, pull co:follow-up off the thread in Gmail. Because comail checks live labels on every request, the thread disappears from the agent’s scope immediately—when its timer fires, get_thread returns “not found” and nothing is drafted.

Your edits lock the draft. If the agent prepares a follow-up and you tweak the wording in Gmail, comail marks the draft as yours and refuses any further agent edits so your changes are never overwritten.

Want a second agent to review and send? When you’re ready to let routine check-ins go out automatically, pair follow-up with a dedicated reviewer agent using pull-request email review.

FAQ

Common questions.

Does my agent need its own email address or forwarding rule?

No. The agent connects to your existing Gmail mailbox through comail and creates reply drafts directly inside the original conversation. Your recipients only ever see your email address, and the full thread history stays intact.

Where does the follow-up timer run?

In your agent’s runtime. comail handles the Gmail side—scoped thread access, live notifications when you apply co:follow-up, and saving drafts—while your agent (in OpenClaw, Claude Code, a cron job, or your own worker) keeps track of when to check back.

Does it work on a thread I just started in Sent?

Yes. Pass include_sent: true when calling create_notification_url. When you send an outbound email and label it co:follow-up, comail notifies your agent right away even before any incoming reply exists.

How does the agent take a thread off its list once it’s done?

Even with general label and archive permissions turned off, an allow-list agent is always allowed to remove its own co:follow-up label with unlabel_thread. Once the recipient replies or the follow-up draft is saved, the agent can drop its label so it won’t check that thread again.

Request access

We’re onboarding beta users in small batches. Tell us what you want your agent to handle; specific use cases go to the front of the line.

Clients / harnesses (optional)

Select all that apply.

We’ll only email you about the beta. No card, no newsletter.