Draft Prospect Replies in Slack That Answer the Actual Question

To draft a prospect reply in Slack, ask Mio to read the linked conversation, identify the specific question, and write a response using your approved service information or examples. Review the draft against that question before sending it. 'Interested' tells you to pay attention; it does not tell you what to say.

For an agency, this is the moment after outreach gets a response and before a sales call exists. It is a different job from building an outbound campaign. The prospect may want a sample, a price boundary or an explanation of how you work. A polished invitation to a call can still leave that request unanswered.

Read the request before choosing the next step

An interested reply often contains two signals: willingness to continue and a condition for continuing. Preserve both. 'Sounds relevant, can you share an example?' is not the same as 'Can we talk on Thursday?'

Write one plain sentence above the draft: 'The prospect wants ___ so they can judge ___.' If the second part is unclear, leave it uncertain. Do not turn a short reply into a confident account of the buyer's budget, urgency or decision process.

• They ask for an example: find a relevant, approved example or explain what you still need to get. Do not invent a customer result.
• They ask about scope or price: use the current approved boundary. If the answer depends on an unknown, ask that question rather than fabricate a quote.
• They ask for a meeting: propose the next scheduling step. Do not claim availability you have not checked.
• They decline: respect the response. An AI-written objection handler is not a reason to ignore a clear no.

Give the draft three sources of context

First, provide the original outreach and the latest reply. Your earlier message may have promised a sample, named a service or suggested a particular outcome. The response should honor that context. If a Slack notification only contains an excerpt, open the original conversation before treating it as complete.

Second, identify the company material that can support the answer: a current service description, an approved sample, a public demonstration or a confirmed commercial term. A prospect's website can help explain what they do. It cannot establish their private priorities or prove they have a problem you can fix.

Third, specify where the reply will go. A short LinkedIn exchange and an email with supporting material need different lengths and formatting. Include the intended recipient and tell Mio which information belongs only in the internal discussion.

When the relationship spans several conversations, start by reconstructing the email and Slack context. Do not make the writing step compensate for a missing history.

Ask Mio for a reply and separate review notes

Mio's agency workflow includes preparing context and drafting follow-ups in Slack. Start with one actual conversation you are authorized to use. Link the relevant Slack thread and approved material, or supply an authorized excerpt if the original source is not accessible.

A practical request is: @Mio read this prospect conversation and the approved service note. What are they asking us to provide? Draft a short email reply that answers that request first. Use only supported claims. Put source links and missing facts in separate internal review notes, not in the customer copy. If a source is unavailable, tell me what is missing. Do not send anything.

The output should have two clearly separated parts: copy you can review as the proposed reply, and notes explaining what needs checking. Keep internal speculation, pricing discussions and restricted links out of the customer-facing block. Read the original source when a claim matters; a fluent draft is not its own evidence.

A worked example: they want the report, not the pitch

This example is fictional. A prospect replies to an agency's outreach: 'Can you show what the weekly report would cover? We care about qualified enquiries, not just impressions.' The agency's approved service note says it reports visits and enquiries, but the client supplies qualification status. No approved customer report is available to share.

A weak draft would say: 'We help companies like yours turn traffic into revenue. Are you free for a quick call?' It sounds plausible, but it neither explains the report nor acknowledges the missing sample.

A more useful draft: 'Yes. The proposed report would separate visits, enquiries and enquiries your team marks qualified. Its core columns would be source, visits, enquiries, qualified enquiries and qualification still pending. We would need your qualification labels rather than infer quality from a form submission. I don't have an approved client report to share, so this is the proposed structure, not a customer example. Is that the distinction you want the report to show?'

That reply gives the prospect something concrete to evaluate. It also leaves one honest dependency visible. A meeting can be a later option; it should not replace the answer the prospect requested.

The internal notes would point to the service note, flag the absence of a shareable sample and ask the account owner to confirm the reporting scope. Those notes are for the sender. They do not belong underneath the email signature.

Choose drafting deliberately, even when sending is possible

Reply drafting is not unique to Mio. Slack describes follow-up drafts based on thread action items. An n8n reply workflow retrieves the conversation, classifies interest and includes an automated sending branch. Those are different operating choices. This guide's starting point is a reviewed draft, not a new automation that speaks to every lead.

Before sending, compare the draft with the latest message in the original channel. Has someone already replied? Does the draft provide the requested item, or only promise something else? Is every price, date and example actually approved? The sender owns those decisions. A 'do not send' instruction defines the task; it is not a substitute for managing the connected tool's permissions.

Test whether the drafting job is useful

Try the workflow on a small set of real replies. Record the request, whether the first draft answered it, factual corrections and time spent gathering context plus editing. A draft that arrives quickly but needs a new argument has not removed the work you care about.

Track later outcomes separately: reviewed, sent, answered, meeting booked. Do not count a generated reply as a conversion. If the prospect does agree to a call, move to the sales-call preparation workflow rather than expanding the reply into a full account briefing.

Pick one reply waiting in your queue. Ask Mio for a draft in Slack, then check whether it gives the prospect what they actually asked for.