Skip to main content
Filler messages let your AI assistant speak scripted phrases while synchronous webhook tools execute. Instead of silence during a database lookup or API call, callers hear natural phrases like “Let me look that up for you” at configurable intervals. In this guide, you will learn:
  • How filler messages work and when to use them
  • How to configure message types and timing
  • How to set them up via the API and Mission Control Portal

Video tutorial


Overview

When an AI assistant calls a synchronous webhook tool, it waits for the response before speaking again. If your backend takes several seconds to respond, the caller hears silence — creating an awkward experience. Filler messages solve this by playing scripted phrases at the start of the request and at timed intervals while the assistant waits. Messages are scripted per tool, not generated by the LLM — you control the exact wording, timing, and brand voice.
Filler messages work with synchronous webhook tools and MCP tool calls only. Async webhooks return immediately and don’t produce dead air. If your backend consistently takes more than a few seconds, consider async tools as an alternative.

Filler message types

There are two types of filler messages, each triggered at a different point during the webhook call. You can configure multiple request_response_delayed messages at different delay thresholds to keep the caller engaged during longer operations.

Configuration

API schema

Add a filler_messages array to your webhook tool configuration:

Key fields

Mission Control Portal

You can also configure filler messages through the Portal:
  1. Navigate to AI > Assistants
  2. Select your assistant and edit a webhook tool
  3. Set the tool to Sync mode
  4. Open the Filler Messages tab
  5. Add your messages and timing thresholds
Filler Messages configuration in Mission Control Portal

Example: tiered filler messages

This example shows a billing lookup tool with three filler messages that escalate in reassurance as the wait grows:
What the caller hears:

Use cases

  • Customer support: Query billing or CRM systems mid-call without silence
  • AI receptionists: Book appointments via webhook while keeping the caller engaged
  • Voice agents calling external LLMs: Fill silence while a third-party LLM or RAG pipeline processes a request
  • Appointment scheduling: Check availability across calendar systems with natural wait phrases

Filler messages vs. async tools

Both features address the same problem — slow backend responses — but take different approaches. Use filler messages when your backend is reasonably fast and you want simple, predictable caller reassurance. Use async tools when backends are slow or you want the assistant to have a free-flowing conversation while waiting.