How to use the Referral Request Email Generator.
Make the requested introduction easy to assess and easy to decline. Explain the relevant fit without suggesting an obligation.
Make the workflow fit your task.
Explain the type of person or team who would benefit and make the requested introduction easy to assess. Offer a short factual description the recipient may forward, leaving room to decline without pressure.
- What you provide
- Relationship context and requested introduction.
- What you get
- Low-pressure referral request draft.
See the input and the result.
Illustrative input and output · a teaching example, not a live WebAct run
Example input
Ask a satisfied catalog-comparison client for an optional introduction to another team with the same supplier-update problem. Supply a short forwardable description and avoid promises of results.
Completed example
If you know a team that regularly reviews supplier catalog updates, would you feel comfortable introducing us? No pressure if an introduction would not be appropriate. You can forward this description if useful: Example Catalog Services prepares comparisons of supplier files, showing changed values alongside their source rows so a team can review an update before importing it.
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.
Should a referral request assume the client endorses every service?
Ask only for an introduction they feel comfortable making. Keep the description within the work they actually know.
Why does the request feel like an obligation?
Remove guilt or implied reciprocity and make the choice explicit. A satisfied customer can still prefer not to introduce contacts.
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 ↑