Yes. Brilo AI Custom Scripts let developers extend Brilo AI voice agent behavior by calling external systems, mapping call data to your CRM, and running business logic at call time. Custom Scripts can be implemented as webhook calls or API actions that the Brilo AI voice agent invokes during a call flow to read or write records, trigger automations, or fetch verification data. Developers typically use your webhook endpoint or API to receive structured call events, return JSON responses that update the conversation, and rely on Brilo AI routing and guardrails to preserve safe behavior. Custom Scripts support integrations, webhooks, CRM updates, and controlled human handoffs when configured.

Can developers build custom integrations with Brilo AI voice agent? — Yes. Custom Scripts let your developers connect to internal APIs and CRMs in real time.

Can I call my API from a Brilo AI voice agent? — Yes. Brilo AI can invoke your webhook endpoint to exchange structured data during a call.

How do Custom Scripts connect Brilo AI to my CRM? — Brilo AI can send call context to your CRM via webhook or API and use the returned data to route or personalize the call.

Enterprises ask about Custom Scripts because their workflows require logic or data that pre-built connectors don’t cover. Banking, insurance, and healthcare teams often need to validate account or patient details, trigger downstream workflows, or block sensitive actions behind business rules. Procurement and engineering want to know whether Brilo AI voice agent can integrate with internal APIs, support authentication patterns, and maintain safe escalation paths for regulated sectors.

When enabled, Brilo AI calls your Custom Script endpoint during a configured point in the call flow and waits for a structured JSON response that influences the next step. The typical flow: the Brilo AI voice agent sends a call event (caller ID, intent, slot values), your service returns validation or an action directive, and Brilo AI continues the conversation based on that response. You configure where in each voice flow a Custom Script runs, how long Brilo AI will wait, and which fields are exchanged.

In Brilo AI, Custom Scripts is a user-configured webhook action that the voice agent invokes to fetch or update external data during a call.

In Brilo AI, call context is the set of variables (call metadata, extracted slots, CRM IDs) that Brilo AI sends to your Custom Script.

In Brilo AI, an action directive is the structured response your Custom Script returns to tell the voice agent how to proceed (for example: route to agent, play a message, or update a record).

For implementation patterns and routing examples, see the Brilo AI call center overview: Brilo AI call center overview.

Related technical terms: webhook, API, SDK, CRM integration, routing rules, call logging, human handoff.

Brilo AI enforces workflow-level guardrails to prevent Custom Scripts from causing unsafe or indefinite call behavior. Typical guardrails include timeouts, maximum retry counts, and preconfigured fallback responses. Brilo AI voice agent will not proceed past a critical escalation point if the Custom Script fails or returns an invalid directive; instead it uses your configured fallback (repeat prompt, transfer to a live agent, or end call).

In Brilo AI, a timeout is the maximum time the voice agent will wait for a Custom Script response before executing the fallback path.

Brilo AI discourages embedding sensitive decisioning (for example, final credit approvals or medical diagnoses) solely inside Custom Scripts without human review and requires explicit escalation paths for high-risk cases.

Do not use Custom Scripts to circumvent compliance controls or to store unencrypted PHI unless your architecture and legal counsel confirm appropriate controls. Design Custom Scripts so they return only the data necessary for the call flow and rely on Brilo AI routing rules for escalation.

Healthcare example:

A hospital configures a Custom Script to verify a patient’s appointment and retrieve visit instructions. During triage, Brilo AI voice agent sends patient ID and receives appointment status; if the script returns a no-show flag, the agent prompts rescheduling and can route to a nurse if needed.

Banking / Financial services example:

A bank uses a Custom Script to check a caller’s account balance and fraud status. The Brilo AI voice agent requests account confirmation, your API returns masked balance and a risk flag, and Brilo AI either provides the balance or routes the caller to fraud operations for live review.

Insurance example:

An insurer implements a Custom Script to validate policy eligibility. The voice agent sends claim number and coverage intent; the script returns eligibility and next-step instructions, and Brilo AI either proceeds with claim intake or transfers to an agent for complex cases.

All examples assume your organization provides the external endpoint and secures responses according to your compliance policies.

Brilo AI voice agent workflows can hand off to a human at any configured point. When a Custom Script returns an escalation directive (for example, {"action": "escalate", "queue": "fraud_ops"}), Brilo AI follows the routing rules to warm-transfer or place the caller in a queue. You can also configure silent agent notifications or CRM tickets to ensure the receiving agent has the call context and last Custom Script response. Handoffs include call metadata (intent, last prompts, script outputs) so agents see the same state the voice agent had.

If a Custom Script times out or returns an error, Brilo AI follows the fallback you configured: retry, use a canned response, or escalate to a live agent for human intervention.

Custom Scripts let regulated teams maintain control over sensitive decisioning while still automating routine interactions. By connecting Brilo AI voice agent to internal APIs and CRMs, organizations can reduce agent handle time for verification tasks, improve first-contact resolution for standard requests, and ensure consistent adherence to business rules. Realistic outcomes include fewer manual lookups, faster validated responses for callers, and clearer escalation signals to human teams—without removing your existing compliance or approval workflows.

Can Custom Scripts access sensitive customer data?

Custom Scripts can return sensitive fields if your endpoint and Brilo AI configuration permit it, but you should minimize data returned and follow your internal security and compliance policies. Use masked values whenever possible and ensure transport uses TLS.

What happens if my Custom Script fails during a live call?

If a Custom Script times out or returns an error, Brilo AI follows the fallback you configured (retry, play a default message, or transfer to a human agent). Configure conservative fallbacks for high-risk flows.

Do I need an SDK to build Custom Scripts?

No. Custom Scripts are typically standard HTTPS webhook endpoints that accept JSON and return JSON. An SDK can simplify development, but Brilo AI works with any secure HTTP endpoint that follows the expected schema.

Can Custom Scripts modify CRM records?

Yes, Custom Scripts can instruct your backend to update CRM records; Brilo AI itself does not directly write to your CRM unless you design the endpoint to perform that update or use a configured connector.

How long will Brilo AI wait for a Custom Script response?

Timeouts are configured at the flow or script level. Design your service to respond quickly and include clear error handling; configure Brilo AI fallbacks for slow or failed responses.