Feature · Built

Structured agent actions

The agent acts through typed tool calls that the backend validates before anything happens. A model that produces bad arguments is ignored, not obeyed.

Tool calls, not keyword matching, for handoff, leads and CTAs.

The tools#

Tool	What it does
`request_handoff(reason)`	Brings a person from the team into the conversation and notifies them.
`capture_contact(email, name, role, company)`	Saves the visitor's details as a lead, only with what they actually gave.
`show_cta(id)`	Shows one of the project's configured call-to-action cards, such as Book a demo.
`log_gap(question)`	Records a question the knowledge base doesn't cover, for the review queue.
`link_page(url)`	Attaches a Read more link to the page the answer came from.

InteractiveStructured actions

Example turns

Can someone talk me through enterprise pricing?

Bringing in the team now. Your work email, in case you step away?

request_handoff(reason="enterprise pricing")

Conversation → waiting. Push to every online teammate with access. First to tap Assign to me takes it.

Pick a visitor message to see which actions the agent takes.

Validated on the server#

Every call is parsed against a schema. Emails must be valid, CTA ids must exist in the project config, and page links must belong to retrieved facts. Invalid calls are dropped and logged, and the agent can take at most one of each action per turn.