Skill: drafting and outreach

What this is

Drafting is the skill that saves the most hours and carries the most risk, for the same reason: the output goes to a real person. In Korps a worker can draft an email, a chat message, a document or a reply in the tone you set, and can send it through a connection you signed in to, but only once the send has been approved if you have marked it so. Reading and drafting are quiet; sending is the moment that matters.

Who it helps

Anyone who writes the same kinds of message often: replies to inquiries, follow-ups, candidate correspondence, supplier reminders, status updates to a team channel, first drafts of proposals and reports.

Examples

• Inbound reply. "Reply to this inquiry in our tone, answer the question, ask the two qualifying questions, propose a call." See the sales follow-up playbook.
• Candidate correspondence. "Draft an interview invitation with these two slots." See recruiting coordination.
• Reminder. "Draft a polite reminder for this overdue invoice, referencing the invoice number and the original due date."
• Team update. "Post a three-line summary of today's shipped work to the #ops channel." A channel post is still a send.
• First draft of a document. "Draft the proposal from the notes in the room, using our template."

How to get your voice

Give the worker a tone guide in the room: three sample messages you were happy with, five words you never use, and how you sign off. A worker with examples writes like you; a worker without them writes like a model.

Requirements and availability

• Available in Korps: drafting inside a task, sending through a connection, approvals that attach the draft to the Needs You item, and Activity naming the system used.
• Connections for sending: Gmail, Outlook, Slack and Microsoft Teams are Korps connections you sign in to once. Messaging by SMS or voice goes through a metered service such as Twilio on your own account.
• A runtime (Hermes Agent comes bundled) and a model on your account. Tone and judgement improve with a stronger model; see choosing a model.
• The free account is open now; the app that hosts workers opens at launch.

Limitations and approval points

• Sending is the approval point. Mark the sending connection "requires approval" for any worker that drafts to people outside your team, and keep it that way until you have read enough drafts to trust the pattern. Then relax it one case at a time, never all at once.
• A draft can be fluent and wrong. Names, dates, amounts and promises are the things to check before approving.
• Never let a worker make commitments you have not authorised: prices, discounts, deadlines, legal terms. Put that in the assignment and treat it as a review point.
• Messages sent under your name are yours. Activity will show that you approved each one, which is the point.