How to use the Cold Email Generator.
Personalization should explain a genuine reason for contact. Avoid invented familiarity, private facts or a generic compliment disguised as research.
Make the workflow fit your task.
Identify the recipient's relevant public need and the factual reason your offer may help. Write a short introduction, one concrete connection and a low-pressure next step without inventing familiarity or results.
- What you provide
- Relevant prospect facts and genuine offer.
- What you get
- Personalized first-contact draft with a clear request.
See the input and the result.
Illustrative input and output · a teaching example, not a live WebAct run
Example input
Example Catalog Services is contacting Example Studio after a public request for help comparing supplier files. Offer a small illustrative comparison; no prior relationship or customer results claimed.
Completed example
Subject: An example for your supplier-file comparison Hello, I saw Example Studio's public request for help comparing supplier files. Example Catalog Services prepares comparisons that show changed prices alongside their source rows. Would a short illustrative comparison help you assess whether that approach fits your catalog work? Best, Example Catalog Services
Load this input into the prompt, then copy it to WebAct to try the task. Your result may differ from the illustration.
Decisions and troubleshooting.
How much personalization belongs in a cold email?
Use the specific context that explains relevance. Unrelated personal details and generic praise can distract from the actual reason for contact.
Why does the email sound researched but say nothing specific?
Replace broad compliments with the supplied problem and a clear proposed action. Personalization should establish fit, not merely insert a name.
Try it with your own source.
Replace the example with your material in the task prompt. Keep the requirements you need, then copy the task into WebAct.
Customize and copy the task ↑