Works inside the tools you already have open

Open the ticket. The reply’s already there.  Draftly drafts customer support replies inside Jira Service Management, Intercom and Gmail.

It reads the whole ticket first. Every comment, every internal note, whatever language your customer wrote in. Then it drafts the reply in your voice. You read it and send it.

7 days free · 50 drafts · no card

English Deutsch Español Français Português Italiano Nederlands Polski 日本語 한국어 中文 Русский العربية Türkçe हिन्दी English Deutsch Español Français Português Italiano Nederlands Polski 日本語 한국어 中文 Русский العربية Türkçe हिन्दी

It’s already in the tab you’re in.

Three tools, no fourth one. Open any conversation and the Draftly button is already sitting on it. Click it and the panel opens where you already are.

Reads the thread through InboxSDK and drops the quoted chain nobody needs. The draft goes into the reply box you already opened.

mail.google.com/mail/u/0/#inbox
Draftly Assistant
DraftlyDrafts 12/50
PromptsManage
Empathetic ResponseQuick SummaryTechnical ExplanationInternal Note
Draft reply

Your reply will appear here…

CopyInsert in EnglishInsert in Portuguese
Custom prompt
e.g. give a range not a fixed date, and mention the backlog…
EnglishGenerate reply

It’s not the typing. It’s the reading.

Before you type a single word you scroll back through the thread, work out what your colleague promised on Tuesday, check whether the refund was ever approved, and remember the one thing you’re not supposed to say about delivery dates.

Then you write four sentences.

Draftly does the first part. Every ticket, before you open it.

“Can’t I just paste it into ChatGPT?”

You can, and it will answer whatever you paste. In practice that means the last message, because pasting forty of them isn’t realistic.

So it won’t see the internal note. It won’t know the priority, or what your colleague already promised. Then you paste the answer back by hand.

Draftly reads the ticket where it lives and writes into the box you already had open.

The whole thread

Every comment, oldest first. On Jira it clicks through the collapsed older ones itself, so nothing is missing by the time it starts writing.

The internal note

The one that says don't give them a date this week. It shapes the reply and never appears in it.

The ticket around it

Priority, status, request type, assignee, linked subtasks. The metadata a chatbot in another tab has no way to see.

The language they wrote in

Taken from the customer's own messages, not from the six agent replies in English that usually sit above them.

Here’s the same ticket, answered twice.

An example, not a measurement. On the left is what gets written when there’s no time to go back through the history. On the right, the same ticket with all of it already read.

Written without the ticket open

“We’re looking into it and will update you shortly.”

Answers nothingShe replies again
Written with the whole ticket read

“Order #12345 is packed and flagged for priority dispatch. I won’t promise a date while we’re clearing a backlog. You’ll get tracking the moment it ships.”

Read the whole threadObeyed the internal noteWritten in Portuguese

Both take the same time to send. Only one ends the conversation.

You press send. Always.

The draft lands in the composer you already had open. Jira’s comment editor, Intercom’s reply box, Gmail’s. It waits there. Nothing goes out while you’re at lunch. Nothing goes out at all until someone reads it and decides it’s right.

Replies Draftly has ever sent on its own: 0

Internal notes stay internal

A comment marked internal shapes what the draft says and never appears in what the customer reads.

Your conversations aren't training data

The ticket goes to our servers and on to Google Gemini to produce the draft, then it's discarded. Not stored, not used to train models.

It writes the way your team writes.

How formal you are. How long your replies run. How you sign off. What you never say to a customer. Set those in settings whenever you want, and every draft after that is held to them.

Four prompts are ready on day one. Save your own for the replies your team writes over and over.

Empathetic Response Quick Summary Technical Explanation Internal Note your own

She wrote in Portuguese. You don’t speak Portuguese.

You read the whole conversation in English. Your reply goes back in Portuguese, with your name, your team and your company name translated to match, instead of left in English the way a machine would leave them.

Reading a conversation never uses a draft

  • English
  • Deutsch
  • Español
  • Français
  • Português
  • Italiano
  • Nederlands
  • Polski
  • 日本語
  • 한국어
  • 中文
  • Русский
  • العربية
  • Türkçe
  • हिन्दी

Two minutes
from here to your first draft.

01

Add it to your browser

Chrome, with Firefox and Safari on the way. Pin it once. It wakes up on its own when you open a ticket.

02

Sign in

Google or an email address. 7 days free and 50 drafts, no card. There is no setup wizard to sit through.

03

Open a ticket you owe a reply to

The Draftly button is already on it. Click it, read what comes back, and send it or don't. You've lost a minute either way.

Add to Chrome Start free trial Coming to Firefox Safari

Plans.

Starter is 150 drafts a month, which is about seven a working day. Every account begins with 7 days and 50 drafts and no card. Cancel whenever, and there are 30 days to change your mind after any charge.

Straight answers.

You have tickets open right now.

Install it, sign in, and try it on a ticket you were going to answer anyway. If the draft is no good, you’ve lost a minute.

7 days free · 50 drafts · no card