Last verified: October 26, 2026
What You Can Now Do
Context Memo customers can now create outbound research jobs that distribute memos to job boards and external platforms, with a pre-send validation check that enforces publish gates before dispatch. Until now, getting a memo onto an external surface meant doing it by hand, one platform at a time, with no systematic check that the memo met your own publishing standards first. The outbound research job turns that into a configured, repeatable send. The decision it changes: you stop deciding whether you have time to distribute a memo this week, and start deciding which destinations a given memo should reach.
Where It Is in Context Memo
Outbound research jobs live in the memo distribution area, alongside your existing publishing and integration settings. On the job configuration screen you'll find the destination selection, the Direct link only toggle that controls publication mode, and the pre-send check results, which surface any publish gate a memo fails before dispatch is allowed to proceed.
How to Use It
- Create an outbound research job from the distribution area and select the memo or memos you want to send. The job appears in your list with its destinations and current status.
- Choose your destinations. Pick the job boards and external platforms the job should dispatch to. Each destination is recorded on the job so you can see exactly where a memo went.
- Set the publication mode. Turn on Direct link only when you want the destination to carry a link back to the memo on your domain rather than a copy of the content. Leave it off when the destination should receive the memo itself. This is the setting that determines whether the authority and the bot traffic stay with your domain.
- Run the pre-send check. The job validates each memo against your existing publish gates. Anything that fails is listed with the gate it missed, and dispatch is blocked until it passes. Nothing goes out below your standard.
- Fix any flagged memos and re-run the check. Correct the memo, re-validate, and the job clears for dispatch.
- Dispatch the job and review the result per destination. You'll see which sends completed and which did not.
Why We Built It
Distribution was the step customers kept doing manually and kept doing inconsistently. A memo would be written, reviewed, and published on-domain, then sit there while someone found an afternoon to push it to external platforms, and by the time they did, nobody was checking it still met the publish gates the team had agreed on. That cost two things: time that marketing teams do not have, and the occasional memo going out to an external surface in a state the team would not have approved. Automating the send and putting the gate check in front of dispatch removes both.
What It Does Not Do Yet
The pre-send check validates against publish gates you have already defined in Context Memo. It does not create gates for you, and it does not evaluate whether a given destination is a good fit for a given memo. Destination selection is still a judgment call you make per job.
Direct link only is a per-job setting, not a per-destination one. If you want some destinations to receive the memo content and others to receive a link, create separate jobs for each mode.
Dispatch results tell you what sent successfully. They are not a citation signal. Whether a memo published to an external platform gets read by AI models and cited in answers still shows up where it always has: in your scan results and your bot crawl log. Treat outbound jobs as distribution plumbing, and keep reading citation outcomes in the scan and crawl data. If a destination produces no crawls and no movement in scanned answers over several cycles, drop it from the job and redirect the effort.
One operating note worth stating plainly. Outbound distribution is additive to own-domain publishing, not a substitute for it. The memo on your domain is what carries the authority, the schema, and the citation credit. External platforms extend reach to readers and crawlers who would not otherwise find the page. Configure your jobs with that order of operations in mind: publish on-domain first, then distribute.
