Skip to main content
Choose the conversation controls visitors see in an agent you can edit. Use features that help the visitor’s task and decide deliberately whether you need any visitor material. Most choices use Design’s Save Changes. Visitor file drop bucket is different: it saves immediately through its own control.

Open the feature controls

  1. Open Home.
  2. Select the intended agent.
  3. Open Design.
  4. Find Features and Conversation Management.
If those controls are already open, continue with Choose the conversation features. On a smaller screen, use the Design subtab for controls and Preview to inspect the widget. Return to Design to save ordinary feature changes.

Choose the conversation features

For a fictional FAQ widget using approved notes, a starting choice is starter prompts on, answer feedback on and file upload off. These are examples, not product defaults. Set a welcome message and starter prompts explains the questions that the display switch uses.

Choose the conversation shortcut

In Conversation Management, Conversation history is shown as Always on in the creator configuration. Conversations in nav bar controls the visible Conversations shortcut in the widget’s main navigation. The account menu still provides a conversation entry. This is a navigation choice, not a switch that deletes or disables all history. Use the shortcut when returning visitors commonly resume chats.

Save the ordinary feature choices

After deciding which controls suit your agent:
  1. Set Starter prompts to the intended state.
  2. Set File upload to the intended state.
  3. Set Answer feedback to the intended state.
  4. Set Conversations in nav bar to the intended state.
  5. Inspect the live preview’s opening screen and menus.
  6. Return to Design if you used the small-screen Preview subtab.
  7. Select Save Changes.
  8. Wait for All Changes Saved.
The preview can show changes before they are saved. Reopen the same agent from Home and check the saved switches. If already shared, inspect that agent’s visitor widget too. If saving fails, keep the page open and read the error before leaving.

Decide separately about retained visitor files

Visitor file drop bucket keeps a shared copy of visitor uploads in a special Library folder after visitors are told about that sharing. This is separate from allowing a conversation attachment. Keep it off unless you need and intend that retained copy. For the simple FAQ example above, leave it off. Retained visitor files do not automatically become general agent knowledge; promotion is a deliberate later step. If you change this toggle, it saves through its own action immediately. It does not wait for Save Changes. Read any result or error, then reopen the same agent’s Design controls to check the retained-file choice. Files visitors send you explains the visitor’s file and sharing experience.

If the expected control does not appear

Check the intended agent, the saved feature state and the relevant opening screen or menu. Feedback and other controls appear where offered; every visitor does not necessarily use them. If uploads fail, read the actual attachment message and check model/input capability. Repeatedly toggling retention does not solve an unsupported upload. Continue with Preview your widget to inspect the overall visitor experience.