Skip to content
AI agents & answers

Configure questions for human support

Collect required support answers before automatic forwarding, in chat or a configured form.

Where to find itAI agents → agent → Features → Human support intake / Vragen bij overdracht

Before you begin

Open AI agents and select the agent you want to edit. Check its name and workspace before saving: other agents have their own settings.

Example workspace · Demo data. Resume returns the conversation to the AI; choose deliberately after finishing human support. Select the image to enlarge it.
A staff-controlled conversation with the Resume button and message composer

Example workspace · Demo data. Resume returns the conversation to the AI; choose deliberately after finishing human support. Select the image to enlarge it.

Step by step

  1. 1

    Choose the presentation

    An administrator opens the separate Human support intake panel. With human support enabled, existing and new agents default to conversational questions, one at a time. Choose Form for the alternative presentation, or disable the built-in intake while keeping human support available.

  2. 2

    Review the questions

    The default order is issue, name, email and phone. Known details are reused; email OR phone is enough for optional contact questions. Every enabled required field must be answered, including both contact channels if both are required. Enable, disable, reorder or remove questions and add custom text or choices, up to ten fields. Standard field types keep their meaning.

  3. 3

    Edit the wording

    Set questions, labels, placeholders and opening/confirmation text. Mark fields Required before forwarding for both chat and form. Configure the form title and submit label. The issue is required by default. Built-in wording supports seven languages; custom form copy appears as configured. Conversational wording adapts to the visitor and is not guaranteed verbatim.

  4. 4

    Save and test both sides

    Save, request a person from a test visitor session and check the issue and collected details in the staff Contact panel. Test a known contact, a refusal, the optional form and staff takeover before collection finishes. An incomplete request stays with the AI without entering the staff queue. Automatic forwarding occurs only after the final valid required answer; optional questions need not be completed. A staff member may still intervene manually.

Good to know

Collected information is self-provided and unverified. It does not authenticate an account or grant marketing permission. Visitors can decline optional questions. Declining or skipping a required question leaves the request unforwarded; the assistant explains this without repeatedly pressuring the visitor. Skips or an old completion flag cannot satisfy current required fields.

Routing and tagging workflows still run. The built-in intake suppresses competing workflow questionnaires while collecting; disable it if an advanced workflow must own the questions. Hosted WordPress/PrestaShop widgets receive this behavior without a plugin ZIP update. Older native connector forms keep their existing layout.

Existing queued support requests and subsequent messages are retained when AI credits run out. An incomplete required intake offers the same validated form and is forwarded only after all required answers are supplied. This fallback does not charge AI credits or interpret answers with AI. No immediate staff response or callback time is promised.

Check the result

Save, start a fresh test conversation and compare the answer with your approved business facts. Settings do not rewrite messages already sent.

Questions & troubleshooting

The visitor is asked twice

Check known details, skipped questions and competing workflows. If a workflow must own the questionnaire, disable the built-in intake rather than running both.

Was this article helpful?

Rate this guide on this device. Ratings are not sent to Corthex.