Why use it
Use it when the wording can vary safely but still needs your business voice and facts.
Working example
Working example: service follow-up draft. The sandbox run uses dummy text only. It shows the active node and the saved output after completion.
Manual trigger → Generate Content → End

The node reads a controlled service request, drafts a concise next-step message, and saves it to the `service_followup` workflow variable.
Picture this
After a site visit, a roofing company generates a concise follow-up email based on the inspection notes and recommended next step.
Set it up
- Tell the model its role, audience, tone, and the facts it may use.
- Ask it to return only the content you will send.
- Save the output to a named variable.
- Review it in a test workflow before passing the variable into Email or SMS.
What comes next
After this block, use an Email or SMS that uses the generated variable.
Avoid this when…
Avoid it for legal, compliance, pricing, or safety wording that must remain exact.
Before you publish or activate: verify the current builder labels in Votel and test with dummy data. This independent guide describes the purpose and a safe setup approach; it does not replace Votel’s current product documentation or compliance advice.