Commands
Signal Outreach is button-driven, not chat-driven. You interact with it by clicking on signal posts in your signals channel. The button on each signal post is the main entry point; a short reply in the post's thread tells you what happened.
Draft Outreach Emails on a Signal Post
Every signal that posts to the signals channel carries a "Draft Outreach Emails" button. Click it and Signal Outreach starts the drafting pipeline for every contact at the flagged firm who is matched to that signal.
[ Draft Outreach Emails ] button on a signal post
Within a few seconds, a thread reply confirms that drafts are queued and tells you how many contacts are in scope. The actual drafts then appear in your own Gmail Drafts folder as they finish writing and clearing compliance. A second thread reply summarises the result when the batch is done.
If you do not have outbound-draft permission, the thread reply explains that and points you to the staff settings page. Nothing is queued in that case.
Re-Click If You Are Unsure
If the thread is silent for more than a minute or two after you click, it is safe to click the button again. The drafts are queued the moment you click; a re-click after a missed acknowledgment will not duplicate them, but it will surface a new confirmation reply so you know the job is in flight.
Where the Drafts Go
The drafts land in the Gmail Drafts folder of the person who clicked the button. Two different wholesalers can click the same signal: each one gets their own drafts in their own mailbox. Nothing is shared and nothing is staged in a common inbox.
Each draft is addressed to one advisor. Same firm, multiple matched contacts, multiple drafts. Each one uses a different opening angle so the recipients do not see five copies of the same email if they compare notes.
Approval Buttons
Signal Outreach does not post Slack approval cards. The approval surface is your Gmail Drafts folder.
The flow is intentionally simple:
| Step | What happens |
|---|---|
| Click "Draft Outreach Emails" on the signal post | The drafting pipeline starts for every matched contact |
| Read the thread reply | Confirms the job is queued and counts the contacts in scope |
| Open Gmail Drafts | Each draft appears as it finishes; the signature is already stamped |
| Read, edit, send | You decide whether to send each draft, in what order, and with what edits |
| Discard in Gmail | If a draft is not worth sending, delete it from Drafts; nothing else is needed |
There is no "Approve" button in Slack because there is nothing to approve in Slack: the draft is yours from the moment it lands in your Drafts folder.
Compliance Status on Sensitive Drafts
If a draft could not fully clear the compliance rules within three rewrite attempts, it still lands in your Drafts folder so you do not lose the work. The subject line is left clean. The compliance status for that draft is recorded for your compliance team's review queue; the email itself is held to the same drafts-only rule as any other. If you are unsure why a particular draft reads the way it does, your compliance lead can pull the rule hits from the review queue.