> ## Documentation Index
> Fetch the complete documentation index at: https://docs.dimedove.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Configuration

> Configure form settings, agent overrides, and input fields

## Basic Settings

### Form Name

Internal identifier for organizing forms. Not shown to users.

### Agent Assignment

* Every form must be connected to an agent
* Agent must be in "Live" status before form can be enabled
* One agent can power multiple forms

### Form Logo

* Optional custom logo displayed at top of form
* Recommended size: 250x150 pixels
* Supports PNG, JPG formats

### Estimated Duration

* Optional completion time estimate
* Options: 1, 5, 10, 15, or 30 minutes
* Displayed to users when they start the form

## Agent Overrides

Override specific agent settings for this form. All overrides are optional.

### Custom Instructions

Replace the agent's default instructions with form-specific instructions.

### Custom First Message

Replace the agent's default greeting with a form-specific welcome message.

* Supports multiple languages
* Users see the greeting in their selected language

### Custom Conversation Starters

Replace default conversation starters with form-specific quick replies.

* Maximum 4 starters per form
* 100 character limit per starter
* Supports multiple languages
* Only shown on first message

### Custom Human Fallback

Replace the agent's default human fallback message with form-specific escalation handling.

### Task Selection

Choose which agent tasks are available in this form.

* By default, all agent tasks are available
* Enable override to select specific tasks only
* Only active tasks can be selected

## Form Structure

### Title

Main heading displayed at the top of the form.

* Required for live forms
* Supports multiple languages

### Description

Brief explanation of the form's purpose displayed to users.

* Optional
* Supports multiple languages

## Form Inputs

Define data fields to collect from users.

### Input Types

**Text** - Single-line text input

**Number** - Integer values only

**Decimal** - Decimal/floating-point numbers

**Boolean** - True/false values

### Input Configuration

Each input field requires:

**Key** (Required)

* Unique identifier for the field
* Used in webhooks and API responses
* Format: lowercase with underscores (e.g., `first_name`)
* Auto-generated from name, can be edited

**Name** (Required)

* Display name for the field
* Shown to users during collection

**Description** (Required)

* Explains what information is needed
* Used by agent to understand collection requirements

**Required**

* Mark if field must be collected
* Agent ensures required fields are obtained

### Input ordering

* Reorder fields using the drag handle to the left of each input.
* The agent follows this sequence when guiding visitors through a form, so you can create intentional flows (e.g., qualification before scheduling).
* Drag-and-drop updates are saved instantly, allowing you to test new sequences without recreating inputs.

Use templates (First Name, Email, Phone, etc.) at the top of the inputs section to seed commonly used questions before fine-tuning their order.

## Collection Mode

**Manual Collection**

* Agent explicitly asks user for this field
* User provides value in response

**AI-Inferred Collection**

* Agent extracts value from conversation context
* No explicit question required
* May not be collected if context is insufficient

## Advanced submission controls

Open the **Advanced** tab of a form to configure automation that keeps completion rates high.

### Auto-submit on inactivity

* Enable **Auto-submit on Inactivity** to let Dimedove finish the form when a visitor stops responding.
* The platform monitors for short periods of inactivity and automatically submits the conversation using all collected answers, ensuring downstream systems still receive a full payload.
* This setting is ideal for long forms or high-intent flows where you want partial data captured even if a prospect drops off.

Combine auto-submit with redirect URLs or post-form webhooks to continue journeys (CRM creation, scheduling links, etc.) even when the visitor abandons the chat near the end.