Coco
Register for Beta

Automate sales follow-ups with AI

Coco watches your active conversations and surfaces what needs a follow-up. It drafts the reply, queues next-steps, and closes the gaps before they cost you the deal. About 3-5 credits per draft, depending on context-pull depth. Every draft queues in your Gmail or CRM with your approval at the start; once you've approved the pattern, Coco can keep the follow-up flow running autonomously inside your rules. The work stops piling up. Conversations stop dying quietly in your inbox.

Try Coco for free → · 1,000 credits free · no card · ~2-min setup

Why follow-ups die, and why it costs

The math on dropped follow-ups is brutal, and most reps know it without ever sitting with the numbers.

20 active conversations in a given week is a healthy pipeline for an AE. Each one needs at least one timely touch: a reply to a question, a nudge on a quiet thread, a next-step proposal after a call, a check-in on a deal that's been silent for a few days. Twenty conversations, twenty touches, fifteen minutes each. Five hours of pure follow-up work on top of everything else the week demands.

What actually happens: you get to 6 or 7. The other 13 slide. Some come back to life on their own. Most don't. By the end of the quarter, the pipeline you thought you had is the pipeline that survived the follow-up bottleneck, not the pipeline that earned the close.

The fix isn't more discipline. Reps are disciplined. The fix is taking the work itself out of the inbox.

How Coco runs the follow-up workflow

Coco operates as a watcher across your email, CRM, and calendar. The landing page calls this the Follow-up queue: Ramp · draft reply ready · Mercury · nudge due today · Linear · meeting follow-up missing. The mechanics:

Trigger conditions. Coco flags a conversation for follow-up when one of three things happens: the prospect replies and you haven't responded inside your threshold, the prospect goes silent past your gap rule, or an event happens that demands a follow-up (meeting completes, deal stage changes, contract sent and no acknowledgment).

Context pull. Coco pulls the full thread, the deal context from HubSpot or Salesforce, any recent activity (call notes, meeting outcomes, CRM updates), and the contact's recent behavior. About 1-2 credits of the per-draft cost goes here.

Draft the reply. Coco writes the response in your voice, anchored to the actual conversation history, not a templated "just checking in." The draft references the specific thread, the specific previous touch, the specific next step. About 3-5 credits per draft all-in.

Queue for review. The draft lands in Gmail drafts with the reasoning attached: why this follow-up, what triggered it, what the suggested next-step is. You edit inline or approve.

Send on approval. Sends gate on your explicit approval at the start. Once you've approved the pattern a few times, you can let specific low-risk patterns auto-send inside guardrails. See how the approval-to-autonomous loop works for the trust model.

Reply drafting with context, not templates

The difference between a Coco-drafted follow-up and a templated one is what's referenced in the body.

A templated follow-up reads: "Hi [Name], just wanted to check in on our last conversation."

A Coco-drafted follow-up references the actual thread. "Hi Maya, back on the procurement question you raised last Thursday. Our standard MSA covers most of what you flagged; the indemnity language is the one open item. I can have our counsel turn it around by Wednesday if that's the blocker, or we can hop on 20 minutes to walk through alternatives."

The drafting cost is roughly the same: about 3-5 credits per draft. The credibility isn't. Replies that reference the actual conversation history land differently than generic check-ins.

For the harder cases (conversations silent for weeks that need a real re-engagement strategy, not just a follow-up) see how Coco reactivates stalled deals. Related workflow, different drafting approach.

Catching gaps before they cost

The harder problem isn't drafting the reply once you've decided to follow up. It's noticing that the follow-up needed to happen at all.

Coco's queue surfaces:

  • Replies you haven't responded to past your threshold (default 24 hours for active deals, configurable).
  • Conversations silent past your gap rule ("flag any active deal silent more than 4 days").
  • Missing post-meeting follow-ups. Coco watches your calendar; meetings that ended without a follow-up email landing in your sent folder within your threshold surface for review. For dedicated meeting prep and post-meeting work, see how Coco preps sales meetings.
  • Stage transitions that imply a next step. Deal moved to "negotiation" but no scheduled next call, contract sent but no acknowledgment, etc.

Each item shows the rationale ("Ramp: 4 days silent at the qualified stage, last activity was a pricing question 8d ago") so you can action it or skip with a reason.

Try Coco for free → · 1,000 credits free · no card · ~2-min setup

Autonomous follow-up rules

Most teams start with approve-each-draft. After a couple of weeks the patterns are obvious. Some of them (simple acknowledgment replies, scheduling confirmations, routine "got it, thanks" responses) don't need approval the second time. Others (anything with pricing, anything that affects deal stage, anything to a senior decision-maker) should keep their gate.

Coco lets you graduate specific patterns to autonomous execution inside the rules you set:

  • "Auto-draft and auto-send acknowledgments for any reply that doesn't include a question or a request."
  • "Auto-draft follow-ups for deals silent more than 4 days; queue for my approval; don't send."
  • "For any deal at stage 'proposal sent,' draft the nudge weekly until I approve a send or close it."

Each rule is editable, reversible, and logged. You see what Coco did, why it did it, what it spent. The goal isn't endless supervision; it's trusted execution inside boundaries you defined.

Why this beats a CRM task

A CRM task is a reminder. It tells you that you should follow up. It doesn't follow up.

Reminders are the right tool when the bottleneck is forgetting. The actual bottleneck is the time the work takes: pulling context, drafting the message, finding the right tone, sending it. CRM tasks pile up because each one demands 15 minutes of focused work to resolve. The reminder fires; the rep ignores it; the deal slips.

Coco produces the draft. Resolving the queue is reading and approving, not researching and writing. Five hours of work becomes 45 minutes of reading.

For the first-touch workflow, see how Coco drafts cold outreach. This page is the nth-touch.

Frequently asked questions

What triggers a follow-up?

Time since last touch, deal stage, your rules, and event triggers (replies you haven't responded to, missing post-meeting work, stage transitions). All of these are configurable per workflow.

Can Coco auto-send replies?

Only if you've approved an autonomous pattern for that specific type of reply. The default is approve-before-send. Auto-send is a graduated capability for low-risk patterns you've explicitly authorized.

What if the draft is wrong?

Edit it inline, send it back with a note, or skip the follow-up entirely with a reason. Coco learns the constraint and applies it to subsequent drafts in the same workflow.

Does it work across email and CRM?

Yes. Coco pulls context from both (email threads, deal history, call notes, activity logs) and queues drafts in the right place. Replies queue in Gmail drafts; CRM updates queue in HubSpot or Salesforce. Both gate on approval.

Will it remind me, or actually do it?

It produces the draft. A reminder tells you the work needs doing. Coco does the drafting and waits for your approval to send. The difference is whether the bottleneck is forgetting (reminders solve that) or time (Coco solves that).

Get started

Connect Gmail and your CRM. Hand Coco one threshold ("flag any active deal silent more than 4 days") and let it surface the queue this week. Read the drafts. Decide whether the queue is the work you'd otherwise miss.

Try Coco for free → · 1,000 credits free · no card · ~2-min setup

Or book a walkthrough → if you'd rather see the follow-up queue run live first.