Skip to main content
Collect data turns information shared in a conversation into structured fields saved in Visito. You define the fields and when they should be saved. The agent uses details already available and asks for anything required that is still missing. Use it for contact details, preferences, requests, feedback, or other information your team needs in a consistent format. You do not need a spreadsheet, API server, or webhook.

Choose the right action

Use Collect data when the result you need is a saved set of fields. Use Connect a system to retrieve current information from an API or perform an operation in another system. Use Google Sheets to read or write spreadsheet rows. A saved submission does not automatically create a sales opportunity, schedule an appointment, or assign a follow-up. Configure those workflows separately when needed.

1. Explain what to collect and when

Open Connectors → Add your own system → Visito-hosted. This opens a single setup modal. Name the system, such as Guest requests, then define its first collection action. Give each action a name that describes the information it captures. Select Add action to configure several actions together, for example Save a tour request and Save guest feedback. The system shares its name and description. Each action has its own instructions, fields, business scope, and mode. No API URL or authentication is needed. A named Visito-hosted system with two actions in one creation modal. In When and how the AI should use it, explain the customer’s intent, what each field means, and when the agent should save the information. Tell it to use details already shared, ask only for missing information, and never invent values. If you want the customer to review or confirm the details before saving, say so in these instructions. Marking fields as required does not add a confirmation step on its own. Choose the intended business scope. Use All businesses only when the action should apply throughout the workspace.

2. Define your fields

Select Add field for each piece of information. You can configure up to 20 fields. Choose the type that fits the information: Specify units and meaning in the description. A Number field alone does not tell the agent whether a value is a price, distance, or quantity. For choices, add each option separately and check that all intended options are present. Required fields must be supplied before saving; optional fields can be omitted. If an answer is unclear or does not fit the choices, the agent should ask for clarification. Select Create system when the actions are ready. The system appears once in Installed, and its Actions page lists the actions you created. You can create 1–20 actions at once, subject to workspace limits of 50 saved collection actions and 10 enabled collection actions (including Playground-only actions). If validation or a limit fails, the system and its actions are not partially created. Both collection actions under one installed system.

3. Choose where the data goes

By default, submissions are saved in Visito. After creating the system, click an action to open its right drawer, then choose Destination. Leave it empty if your team will review the information in Visito. To deliver collected information to another system, configure the optional HTTPS destination and any required Bearer token. This is a webhook destination for saved information, rather than an API lookup used to answer the customer. Review collection action delivery with whoever maintains the receiving system. The system setup creates the collection actions first. Optional webhook delivery is configured separately on each saved action. Reopen an action to edit its General, Fields, and Destination tabs. Its webhook URL and token are not shared with other actions.

4. Test the conversation

New collection actions start in Playground only. In Playground, test how the customer would naturally describe their needs. Provide some details first, then the remaining required information. Check that the agent reuses known answers instead of asking everything again. Also try an invalid value, an unsupported choice, a correction before saving, and a complete submission. Confirm that values have the expected types and that the agent saves at the point described in your instructions. After reviewing the results, use Active and save the action to enable it for live conversations. If testing a live channel or webhook, use a controlled destination and synthetic data.

5. Find the saved information

Open Connectors → Activity, filter by the action, and open an execution. Review its inputs and result. A successful submission provides a saved-record reference; the agent’s reply alone is not proof that data was saved. Use Open conversation to see the action receipt next to the exchange. For live submissions, open the conversation’s CRM → Action submissions panel to review the structured values and any delivery status. Playground submissions do not appear as live CRM records. If the customer changes details after saving, do not assume another invocation edits the original submission. Check the saved records and define the follow-up behavior your workflow needs.

Manage the system and add actions later

From the saved system, select Add action to create another collection action. It belongs to this system automatically. Creation opens a modal; clicking a saved action opens its right drawer. Open Settings, then click the system row to edit its shared name and description in the right drawer. The pencil beside the system name opens the same settings. Hosted systems have no external API connection or shared authentication. Add another system from Connectors → Add your own system. Shared hosted-system settings in the right drawer. Existing ungrouped collection actions remain available in Installed → Built-in actions. They are not moved into a new system automatically.

Troubleshooting

Example: capture property preferences

Real estate inquiry

Collect a preferred neighborhood, budget, and purchase timeframe, then follow the saved values through the conversation and CRM panel.
Developers can manage these actions through the Actions API. Learn how to test and debug in Activity.