Skip to main content
Global settings define the default behavior for your entire flow agent. These defaults apply across all nodes unless overridden at the node level.

Overview

Global settings are organized into these categories:

System Prompt

The system prompt defines the agent’s identity, behavior, and constraints. It applies across all conversation nodes unless a node has its own prompt that overrides it.
System prompt is required. Your flow cannot be saved without it.
The default value is You are a helpful assistant that will answer users questions. The system prompt supports system variables and custom variables only. Extracted variables (collected during conversation) are not available here.

Enhanced Turn Taking

Toggle to enable better numeral capturing and backchannel detection for more natural conversations. Default: Off

Prompt Enhancer

Controls automatic prompt enhancements applied to your system prompt.

Example

→ See Writing Effective Prompts for full guidance on structuring prompts and using variables.

Voice Settings

Select a voice from Hamsa’s voice library. The selected voice is the default for all nodes; individual nodes can override it. Voice configuration works the same way as in single-prompt agents.

Expressiveness

Controls the emotional range and variation of the voice. Range: 0.0–2.0 Default: 1.0

Voice Dictionaries

Attach pronunciation dictionaries for specialized terms (brand names, technical jargon, foreign words). Dictionaries are managed in the Voices section and selected here.

STT Model

Select the speech-to-text model for transcription. → See Voice Settings for full details on browsing, filtering, previewing, and selecting voices.

LLM Settings

Configure the default language model for your flow. Individual nodes can override the model and temperature.

Provider and Model

Default: Gemini 3.1 Flash Lite

Temperature

Controls response variability. Range: 0.0–1.0 Default: 0.2
GPT-5 family models (GPT-5, GPT-5-Mini, GPT-5-Nano) require temperature = 1.0. This is enforced automatically when you select a GPT-5 model.

Node-Level Overrides

Model and temperature can be overridden per conversation node. This lets you use a more capable model for complex reasoning nodes and a lighter model for simple confirmations.

Noise Cancellation

Removes background noise from the caller’s audio. Model:
  • Disabled — No noise cancellation
  • Telephony Optimized — Optimized for phone call audio
  • General Use Cases — Broader noise cancellation
Granularity (when enabled):
  • Per Conversation — Apply once for the entire call
  • Per Turn — Apply to each speaking turn separately
Additional options:
  • Auto Gain Control — Normalize audio volume levels
  • Send Denoised to STT — Send the cleaned audio to the speech-to-text engine
Do not enable both Noise Cancellation and Background Noise — they conflict and create audio artifacts.

Knowledge Base

Attach knowledge sources that your agent can query during the conversation using Retrieval-Augmented Generation (RAG). When a user asks a question, relevant content is retrieved from the knowledge base and provided to the LLM as context. Knowledge base items are created and managed in the Knowledge Base section and then attached to your agent here. → See Knowledge Base for full details on creating and managing knowledge items.

MCP Tools

Model Context Protocol (MCP) tools attached here are available to all conversation nodes in the flow — any node can invoke them without per-node configuration. Use MCP tools for functions that multiple nodes need (for example, a customer lookup or a business hours check). For actions that only one node needs, use a node-level tool instead. → See Tools for full details on creating and configuring tools.

Outcome

Define how call results are classified for analytics and reporting.

Configuration

Example

Outcomes are typically set in End Call nodes, but can also be set via tool calls or webhooks during the conversation.

Phone Number

Assign phone numbers to this agent for inbound and outbound calls. Inbound: When a customer calls an assigned number, the call routes to this flow agent. Outbound: When initiating a call via API, the agent uses one of the assigned numbers as caller ID. All assigned numbers use the same flow configuration. To use different flows for different numbers, create separate agents.

Call Settings

Configure timing and behavior defaults for all calls. → See Call Behavior Settings for full details on each setting.

Webhook

Send call events to an external HTTP endpoint.

Configuration

The webhook endpoint must respond within 5 seconds. Return 200 OK quickly and process the payload asynchronously. → See Webhooks for event types, payload structure, and authentication details.

Next Steps

Node Types

Learn about all available node types

Transitions

Control how conversations move between nodes

Variables

Pass data between nodes and into prompts

Best Practices

Tips for building reliable flow agents