Skip to main content
A play packages an outreach strategy with target inputs and drafting instructions. Finders route candidates to a play; the Queue lets you approve and drain them. The Plays page shows available strategies, channels and editable cadence steps.

​
Match the reason for contact

Use the available Run form or CLI command for the play you choose. Not every play has both surfaces. Queue-only plays are invoked through drain. Voice and SMS motions have different target requirements from email. x-amplify-dm produces text for you to copy into X and send by hand. Mark sent records the touch; generating the draft does not send it.

​
Review before sending

A draft should connect the person’s real signal to a useful offer. Your product brief and founder facts supply the context; blank credentials or evidence should not be invented. Review lint flags, recipient identity and sender routing before approving. Institutional plays require institutional context. For example, sources-sought uses a specific notice and agency. design-partner-loi moves from conversation to a scoped pilot to a non-binding letter of intent, and rejects owner-operator buyer types before drafting.

​
Manage the conversation

Many plays attach a cadence: a value follow-up and a final breakup message, with timing editable from Plays. Run cadence advance to poll inbound and fire due steps. Recorded email replies stop live cadences for the prospect. You can stop a cadence manually and record why. Bad timing and other eligible stops may enter breakup-revive after the configured cold window; not-a-fit and do-not-contact remain excluded. LinkedIn replies can also stop email cadences through Mark LinkedIn reply or the reply webhook. Connection acceptance alone is not a reply.