AI Response Generation
AI Response Generation runs a model and returns text (and optional structured fields) to later nodes. It does not speak. Speech is AI Response to Caller.
Why this node
Section titled “Why this node”Summarize the call for an email. Classify intent before Multiple Choice. Draft a note for HubSpot. Put it on On Call End or On API Call, not on a live During graph unless you accept the wait.
What you configure
Section titled “What you configure”Tabs: Prompt, Model, Variables.
{{node_X.name}}.Ports: Response generated, Generation failed, No wait.
First setup — summary into email
Section titled “First setup — summary into email”-
On Call End → AI Response Generation. Prompt: write a short summary from Call Parameters.
-
Send Email on Response generated. Body inserts that node’s output.
-
Save & go live, attach, hang up. Read the mail — if it is empty, the prompt was too thin or you inserted the wrong node.
What “broken” looks like
Section titled “What “broken” looks like”- Needs setup — empty prompt (or shorter than two characters).
- Caller hears a pause — this node is on During Call.
- They expected the agent to say the text — use AI Response to Caller.
Troubleshooting
Section titled “Troubleshooting”Why are there two AI nodes?
To Caller = live audio (or Start context). Generation = text for Email / HubSpot / Code. Same model family, different job.