Outreach Message AI workflow template: Outreach on a real hook, logged.

The ConvOps Outreach Message template makes your AI send personalized outreach: capture the prospect and offer, research one specific, current hook, draft a short message with one clear ask, check it before sending, then log the outcome. A sent message cannot be recalled, so the run waits for your approval at Send Review. Reject it and it redrafts.

5 steps · 1 approval · 1 loop back

Outreach Message · example runyour AI client
  1. 01Prospect Intake
  2. 02Research
  3. 03Draft
  4. 04Send Reviewwaits for approval
  5. 05Log Outcomeclosing note
task created · workflow attached

example · the steps are this template's real steps

in short

What does the Outreach Message template do?

For founders and sales reps writing cold emails or LinkedIn messages who want each one grounded in research, not a template.

Outreach Message is stored in ConvOps as five steps, and your AI client receives them one at a time. A Outreach Message run holds at Send Review until an explicit approval is given.

  • Write a cold email tailored to one prospect's role and trigger
  • Draft a LinkedIn outreach message grounded in real research
  • Reach out to a lead and record the outcome for follow-up
step by step

How does the Outreach Message workflow run?

The 5 Outreach Message steps in order, each with the instruction your AI receives there as Outreach Message stores it.

Prospect Intake
Research
Draft
Send Reviewapproval
Log Outcomeclosing note

A sent message built on one researched hook, with the outcome and the next action logged on the task.

  1. 01

    Prospect Intake

    the agent works

    Capture the prospect and the offer before researching.

    Record:

    • Prospect: name, role, company, and contact channel
    • Your offer: what you are reaching out about, in one sentence
    • Desired outcome: a reply, a meeting, a demo
    • Any prior contact with this prospect or account

    If this prospect came from a Prospect Research workflow, pull their entry from that list. If key details are missing, ask the operator.

    Save the prospect and offer as a task note with task_notes_add. The next step (Research) reads this note.

  2. 02

    Research

    the agent works

    Read the task notes with task_notes_list: the note from the Prospect Intake step contains the prospect and offer. Work from it.

    Research the prospect and account to find a genuine, specific hook. What good looks like:

    • One concrete, current detail you can reference: a recent post, a hire, a funding round, a product change, a stated pain
    • Why that detail connects to your offer
    • The right angle for this specific person, not a generic pitch

    A relevant hook beats a clever line. If you find nothing specific, say so rather than inventing it.

    Save the research hook and angle as a task note with task_notes_add. The Draft step reads this note.

  3. 03

    Draft

    the agent works

    Read the task notes with task_notes_list: the Research note holds the hook and angle, and the Prospect Intake note holds the offer and desired outcome. Work from them.

    Write the message. What good looks like:

    • Opens on the specific hook, not "I hope this finds you well"
    • Connects the hook to the offer in a sentence or two
    • One clear, low-friction ask matching the desired outcome
    • Short: respect the reader's time
    • The right tone and length for the channel (email vs LinkedIn)

    Save the full message as a task note with task_notes_add. The Send Review step reads this note.

  4. 04

    Send Review

    waits for your approval

    Read the task notes with task_notes_list: the note from the Draft step contains the message. Work from it.

    Check the message before sending:

    • Right name, role, and company: no merge-field mistakes
    • The hook is accurate and the claim is true
    • The ask is clear and matches the desired outcome
    • Any link works

    Ask the operator to approve the message for sending. This is a checkpoint: sending is irreversible, so the AI cannot advance until you approve. If you reject, the workflow returns to Draft.

    rejected → back to Draft

  5. 05

    Log Outcome

    closes with a note

    The message is approved and sent. Record the outcome so the next person (or a follow-up workflow) has the full picture.

    Save a task note with task_notes_add capturing:

    • Who was contacted, on which channel, and the date
    • The message that was sent
    • The result so far: replied, no reply, bounced, meeting booked
    • The next action and when, if any

    This note is the audit trail for this outreach and the named input for a Meeting Follow-Up workflow if the prospect responds. Close out the task.

reach for it when

  • Each message should rest on something specific about the recipient.
  • You want a record of who was contacted, when, and with what result.
  • A wrong name or a false hook would cost you the account.

something else fits when

  • The same message is going to a large list, which is a sequencer's job.
  • The prospect already replied: Meeting Follow-Up.
  • There is no real hook to find.
example · logistics sales

An intro to a dispatch lead

The hook is a job post for three dispatch coordinators. The draft runs 80 words with one ask, Send Review confirms the role and company, and the rep approves the send.

Send Review approval

where approval is required

Where do you approve in Outreach Message?

Outreach Message holds at Send Review until an explicit approval is given, recorded with the account that gave it.

step 4

Send Review

Nothing in a sent message can be corrected later. The AI checks name, role, company, the hook's accuracy, the ask and any link. You approve or send it back to Draft.

what you review

  • Right name, role, and company: no merge-field mistakes
  • The hook is accurate and the claim is true
  • The ask is clear and matches the desired outcome
  • Any link works

reject → back to Draft

gates the engine checks without you

  • Log Outcome closes Outreach Message only when your AI leaves a closing note, saved on the task.
what you need

What do you need to run Outreach Message?

make it yours

How do you customize Outreach Message?

Once installed, Outreach Message is a workflow in your workspace. Ask your AI to change Outreach Message in plain words; the edit lands on the one step that needs it.

ChatGPTexample

new chat

In Draft, keep every message under 90 words.
workflow_step_update · Outreach Message
Done. Outreach Message in your workspace now has the change, and every new run follows it.

more example prompts

  • "In Draft, keep every message under 90 words."
  • "In Log Outcome, add a follow-up task three business days after sending."
  • "For LinkedIn, draft a connection note under 300 characters."
the difference

Outreach Message: without a workflow vs with it

  • A generic template goes out with the wrong first name and zero relevance to the prospect
  • The send happens before anyone checks the claim, the link, or the ask
  • Nobody remembers whether this prospect was already contacted or what the reply was
  • The Outreach Message process lives in a prompt, and each run follows it a little differently
  • The AI drives a Research step first, so the message lands on something specific about that account
  • The AI pauses at a send-review checkpoint so you sign off before the message goes out
  • The AI logs the outcome as a note, so the audit trail of who was contacted and what happened is already there
  • Your AI receives the 5 stored steps one at a time, and the run holds at Send Review until an explicit approval is given
questions

Outreach Message template FAQ

What is the ConvOps Outreach Message template?

The ConvOps Outreach Message template makes your AI send personalized outreach: capture the prospect and offer, research one specific, current hook, draft a short message with one clear ask, check it before sending, then log the outcome. A sent message cannot be recalled, so the run waits for your approval at Send Review. Reject it and it redrafts.

What if the AI finds no specific hook?

The ConvOps Research step tells your AI to state that it found none rather than invent one, because a relevant hook beats a clever line. A good hook is one concrete, current detail, such as a recent post, a hire, a funding round or a product change, plus why it connects to your offer. Send Review then checks the hook is accurate.

What does Log Outcome record?

The ConvOps Log Outcome step saves who was contacted, on which channel and when, the message sent, the result so far (replied, no reply, bounced, meeting booked) and the next action. It is the audit trail for this outreach and the named input for a Meeting Follow-Up workflow if the prospect responds.

Can it pull prospects from a research list?

Yes. In ConvOps, the Prospect Intake step pulls the prospect's entry from a Prospect Research list when the prospect came from one, along with your offer in one sentence and the outcome you want: a reply, a meeting or a demo. If key details are missing, your AI asks you before researching. Both templates ship in the Sales Outreach kit.

What does Send Review check?

The ConvOps Send Review step checks the name, role and company are right with no merge-field mistakes, the hook is accurate and the claim true, the ask is clear and matches the desired outcome, and any link works. Sending is irreversible, so the run holds until an explicit approval is given. Reject it and the run returns to Draft.