Define structured config forms and real-time agent settings.
The Configuration Builder allows builders to define JSON schemas that generate structured config forms. These forms let managers safely update settings—like opening hours or toggle flags—across environments.
Configuration Builder separates structure (schema) from values (data).
Tab | Purpose |
---|---|
Schema | Define what fields exist (like opening hours, toggles) |
Data | Fill in the environment-specific values |
The schema ensures consistent structure and validation. The data defines what the agent uses at runtime.
The configuration builder is not tied to the main publish lifecycle.
The builder sits outside the agent’s draft/publish system, so changes to schema and values take effect immediately.
This means:
In Configuration Builder → Schema, define the fields your manager should configure. For example:
opening_hours
after_hours_enabled
fallback_number
These fields are written in JSON Schema format. The schema drives the form layout in the next step.
Once a schema is saved, the Real Time Configuration UI will appear automatically, even if no values are set.
You can, however, populate values manually, at any time, in the Data tab, where each environment (Draft, Pre-release, Live) maintains its own data.
Fields can be left blank unless marked required.
You do not need to publish your assistant for config changes to take effect. However, publishing may still be useful if you want to include these changes in a documented release.
Once your schema is added, the Real Time Configuration tab becomes available for managers to enter values for:
Use the conv.real_time_config helper to read real-time values.
Design schemas for clarity. Labels and descriptions help non-technical users.
Validate critical fields (like phone numbers) with regex.
Test behavior across all environments before deploying to Live.
Keep track of which flows and functions use which configuration fields.
If the schema is edited in a way that invalidates existing data, the system will prevent publishing until all environments are valid again.
Yes. For example, you can test one phone number in pre-release while using a different one in live.
Need help? Contact platform-support@poly-ai.com.
Define structured config forms and real-time agent settings.
The Configuration Builder allows builders to define JSON schemas that generate structured config forms. These forms let managers safely update settings—like opening hours or toggle flags—across environments.
Configuration Builder separates structure (schema) from values (data).
Tab | Purpose |
---|---|
Schema | Define what fields exist (like opening hours, toggles) |
Data | Fill in the environment-specific values |
The schema ensures consistent structure and validation. The data defines what the agent uses at runtime.
The configuration builder is not tied to the main publish lifecycle.
The builder sits outside the agent’s draft/publish system, so changes to schema and values take effect immediately.
This means:
In Configuration Builder → Schema, define the fields your manager should configure. For example:
opening_hours
after_hours_enabled
fallback_number
These fields are written in JSON Schema format. The schema drives the form layout in the next step.
Once a schema is saved, the Real Time Configuration UI will appear automatically, even if no values are set.
You can, however, populate values manually, at any time, in the Data tab, where each environment (Draft, Pre-release, Live) maintains its own data.
Fields can be left blank unless marked required.
You do not need to publish your assistant for config changes to take effect. However, publishing may still be useful if you want to include these changes in a documented release.
Once your schema is added, the Real Time Configuration tab becomes available for managers to enter values for:
Use the conv.real_time_config helper to read real-time values.
Design schemas for clarity. Labels and descriptions help non-technical users.
Validate critical fields (like phone numbers) with regex.
Test behavior across all environments before deploying to Live.
Keep track of which flows and functions use which configuration fields.
If the schema is edited in a way that invalidates existing data, the system will prevent publishing until all environments are valid again.
Yes. For example, you can test one phone number in pre-release while using a different one in live.
Need help? Contact platform-support@poly-ai.com.