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
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
example · the steps are this template's real steps
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.
The 5 Outreach Message steps in order, each with the instruction your AI receives there as Outreach Message stores it.
A sent message built on one researched hook, with the outcome and the next action logged on the task.
Capture the prospect and the offer before researching.
Record:
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.
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:
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.
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:
Save the full message as a task note with task_notes_add. The Send Review step reads this note.
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:
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
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:
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.
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
Outreach Message holds at Send Review until an explicit approval is given, recorded with the account that gave it.
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
reject → back to Draft
gates the engine checks without you
Outreach Message runs in a ConvOps workspace and attaches to the task type, so new work of that type starts on it. Outreach Message saves each step's output as a task note in ConvOps, and the next Outreach Message step reads it back. Outreach Message needs no repository, so a chat client such as ChatGPT or Claude can run it. Connect a client , then install Outreach Message from the catalog .
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.
new chat
workflow_step_update · Outreach Messagemore example prompts
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.
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.
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.
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.
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.