Skip to main content

Overview

The LLM path is the fastest way to send a voice notification. You provide a message string and Echo generates a contextual call script on the fly using your business context (business_name, business_summary, industry) and the message you provide. No agent definition required. No variables. Just a customer ID and a message.

Sending an LLM-path Notification

Response

Request Fields


Using collect_feedback

When collect_feedback: true, the generated call script includes a feedback prompt at the end of the conversation. The AI will ask the caller to take an action — confirm, cancel, reschedule, or similar — depending on the message content.
The caller’s response is captured in the webhook payload under call_result.

Using context

The context field is for runtime nuance you don’t want hardcoded into the message. Use it to pass background information that shapes how the AI conducts the conversation:
context is invisible to the caller — it’s instructions for the AI, not dialogue. Keep it factual and concise.

Controlling Call Duration

Use max_duration_seconds to cap how long the call can run. This is useful for:
  • Cost control — billing is per minute, so shorter limits reduce exposure
  • User experience — preventing runaway conversations on simple notifications
  • Compliance — some use cases require call length limits
The call ends automatically once the limit is reached, regardless of conversation state.

What Echo Generates

When you use the LLM path, Echo combines:
  • Your business_name, business_summary, and industry from signup
  • The customer’s first_name and last_name
  • Your message and optional context
…into a contextual call script that the AI uses to conduct the conversation. The script is generated fresh for each call — you won’t see it directly, but it reflects your business identity.

LLM Path vs Agent Path

For full control over the conversation, structured output extraction, and consistent brand voice across thousands of calls, use the Agent approach.