Custom fields
If your Twilio Flex flow relies on context from the Ada conversation — such as an account ID or an agent display name — that context can be passed to Twilio Flex as custom fields on each handoff. This is optional and only needed when your Twilio Flex flow requires extra conversation data.
How custom fields work
Custom fields are added to the Twilio Flex block as named inputs. Each field maps an AI Agent variable to a value that is sent to Twilio Flex with the handoff, where it becomes available to your Twilio Flex flow.
Request custom fields
To add custom fields, identify the values your Twilio Flex flow expects, then share them with your Ada team to configure.
To request custom fields:
- Determine the custom fields your handoff needs. For each field, note an ID, a display name, and a description.
- Share the list with your Ada representative.
Your Ada team will add the requested custom fields to the Twilio Flex block and deploy the update. Once deployed, the new fields appear as inputs on the block, labeled with the display name you provided.
You can request additional custom fields at any time by repeating these steps.
Map a custom field in the handoff
After your Ada team confirms the deploy is complete, return to the Twilio Flex block in your Handoff answer to populate each new field.
To map a custom field:
- Locate the new custom field, which appears as an input on the block labeled with its display name.
- Map an AI Agent variable into the field. The mapped value is sent to Twilio Flex with the handoff.