How Quin drafts Copper replies for you

A call ends with a clear reason to follow up by email, and the follow-up itself usually waits, not because it's hard to write, but because it's one more thing competing with everything else that needs doing right after a call.

What slows down a post-call follow-up email

• It's a separate task from the call itself, even though the content for it already exists in what was discussed.
• Starting from a blank draft takes longer than it should, especially when the details are still fresh but not yet written down.
• It competes with logging the call in Copper in the first place, so one or both get delayed.
• The longer it waits, the more generic it tends to get.

How Quin drafts it directly from the conversation

Quin can draft a follow-up email based on a Copper contact's meeting notes, pulling directly from what was discussed rather than starting from scratch.

Picture a call that ends with a client wanting a recap of three specific points covered. Instead of writing that email from memory later, Quin drafts it from the meeting notes already logged in Copper, ready to review and send in the same sitting.

Best practices for getting the most out of it

• Review the draft before sending, since it's a starting point, not a finished email.
• Ask for it right after the call, while the context is freshest.
• Use it for recaps and follow-ups specifically, where the content is already covered in the notes.
• Adjust tone as needed for the specific contact, since a draft won't always match every relationship perfectly.

Setting it up

Connect Copper under Settings, then Integrations, so meeting notes become a starting point for a reply instead of a separate task.