Skip to content
EN
Open app

For AI assistants: this page as plain markdown is at https://docs.voicelogica.ai/raw/workflow-nodes/managed-agent.md, and https://docs.voicelogica.ai/llms.txt lists the docs by topic, one file each, small enough to read whole. Read those rather than this HTML page.

Managed AI Agent

2 min read
Copy as Markdown
View as MarkdownOpen the raw .md file.md

Managed AI Agent is an autonomous loop after the work is known — usually On Call End. It is not AI Response to Caller. It will not talk on the line.

File the ticket, update the CRM, write the follow-up — a short tool loop with a cost cap. One HTTP call is still Connect To External Service. One completion is AI Response Generation.

TaskREQUIRED
What the loop must finish. Seeded so a fresh card is not empty.
Built-in tools / API tools / MCP
What it may call. Runtime expects at least one tool.
Models
Primary (seeded). Optional escalation on the same provider.
Limits
Max iterations (default 15, 0 = no iteration cap) and max cost (USD, max 0.5). Stuck detection bails if the same tool+args fire twice.
Knowledge
Optional files + rerank. Same idea as the agent knowledge attach.

Dry run is on the node — use it while you test. Ports: Task completed, Task failed.

First setup — after hang-up, create a ticket

Section titled “First setup — after hang-up, create a ticket”
  1. Connect the CRM on Integrations if the loop will write there.

  2. On Call End → Managed AI Agent. Task: open a ticket from the call summary. Add the HubSpot (or API) tool it needs.

  3. Leave limits at the seed. Save & go live, attach, hang up one call. Check the CRM — if nothing landed, no tool was added, HubSpot is disconnected, or dry run is on.

  • Needs setup — empty Task.
  • Loop stops early — cost / iteration cap, or stuck detection.
  • Mid-call silence — this node is on During Call.
Why use the Managed AI Agent node instead of chaining API and Email nodes?

If the steps are always the same, chain the nodes. Use Managed AI Agent when the set of writes depends on what happened on the call, and you accept a loop with a cost and iteration cap.