Fields & Logic

📝 Task Field Types

Forms support lots of different field types for collecting info:

✏️ Text Fields

Type	Description
Short Text	A single line for a quick answer
Long Text	A bigger box for longer answers
Rich Text	Fancy text with bold, italics, etc.

🔢 Number Fields

Type	Description
Number	Any number
Range	A single number that must fall between a configured minimum and maximum
Currency	Money amounts (with dollar signs, etc.)
Percentage	A percentage value

📅 Date & Time

Type	Description
Date	Pick a date
Date & Time	Pick a date and time
Time	Pick a time only
Date Range	Pick a start and end date

For a Date task (single calendar answer), you can optionally turn on Date range in the task sidebar and set From and To. Clients then only see dates allowed on or after the start and on or before the end. Both bounds are required when the feature is on.

☑️ Selection Fields

Type	Description
Dropdown	Pick one option from a list
Radio Buttons	Pick one option (all options visible)
Checkboxes	Pick one or more options
Yes/No	Simple yes or no toggle

📎 File Fields

Type	Description
File Upload	Upload one file
Multiple Files	Upload more than one file
Image Upload	Upload an image specifically
Document Upload	Upload a document specifically

✒️ Signature Fields

Type	Description
Signature	Sign your name electronically
Initials	Write your initials

📇 Contact & Address Fields

Type	Description
Phone	A phone number (checks if it's valid)
Email	An email address (checks if it's valid)
Address	A full mailing address in one field

🏠 Structured address (line-by-line)

When you want clients to type each part of an address separately (often mapped to different case fields), use these task types. They appear as single-line inputs on client forms (mobile portal and secure links). If allow multiple is enabled on the task, clients can add more than one value with an Add another control.

Type	Description
Address line 1	Street number and street name (primary line)
Address line 2	Unit, suite, building, or second line
City	City
State	State or region
ZIP or postal code	ZIP or postal code

Short text with multiple answers

Short text tasks can also allow more than one answer. Clients then see the same style of list as structured address lines: a primary value plus optional additional lines.

🧠 Conditional Logic

Make your forms smarter. In the form editor, each task can use Show Condition (when the task appears), each section can use Page visibility (when the whole page appears), and—for supported field types—a Disqualify rule (when a specific answer should end the workflow).

🔄 Show Condition (visibility)

Show Condition lets you define one or more rules that look at earlier tasks on the form. If the rules match (using AND or OR), the task is shown; otherwise it stays hidden.

📄 Page visibility (whole section)

Page visibility applies to an entire section (page) in the form editor. It uses the same rule style as Show Condition, but it hides or shows all tasks on that page together. Rules may only reference questions from other pages—never tasks on the same page—so clients always answer prerequisites before the page can appear. Individual tasks on that page can still have their own Show Condition for extra branching inside the section.

In the accordion, Match using works like this:

Logic	Meaning in the UI
AND	All rules must match (AND: all rules must match)
OR	Any one rule can match (OR: any rule can match)

Use Add condition to add another rule. Complete the current rule before adding the next one.

📋 Operators (show conditions)

Available operators depend on the type of the task you are comparing. Labels below match what you see in the builder.

Operator	Typical use
Equals	Exact match (including Yes / No for Yes/No tasks, or a specific option)
Does not equal	Answer is not the chosen value
Contains	Text includes the given substring, or (for multi-select) selection includes the value
Greater than	Numbers, dates, times, or date & time — strictly after / larger
Greater than or equal to	Same types — at or after / at least
Less than	Strictly before / smaller
Less than or equal to	At or before / at most
Is completed	The referenced task was completed
Is not completed	The referenced task was not completed
Has any answer	The referenced task has some answer (no extra value to enter)

Comparison types

Greater than, Less than, and the “or equal to” variants apply to Number, Date, Time, and Date & Time tasks (and equality-style checks still use Equals / Does not equal where appropriate).

🎯 Tasks you can use in conditions

Show and disqualify logic can reference tasks whose types support rules, including for example: Yes/No, Dropdown, single- and multi-select lists, Number, Short text, Long text, Email, Phone, Address (full or separate line fields), Date, Time, and Date & Time. Range tasks cannot be chosen as the source question for show conditions or page visibility. Other types may not appear as sources in the condition picker.

🛑 Disqualify rule

For the same family of field types, you can set a Disqualify rule on a task: when the client gives the disqualifying answer (or answers), the form can end with a disqualification outcome instead of continuing.

This is especially important for AI voice agents linked to the form. See AI Agent Builder for how disqualified calls are handled and how the disqualified end-of-call message works.

🛠️ Setting up show conditions

1. Open the form editor and select a task.
2. Expand Show Condition.
3. Choose Match using (AND or OR).
4. For each rule: pick the question (task) to evaluate, the operator, and (when required) the value.
5. Use Add condition for more rules.
6. Save the form as usual so changes apply to clients and assigned cases.

🛠️ Setting up page visibility

1. Open the form editor and scroll to the section you want.
2. Expand Page visibility on that section card.
3. Configure Match using and rules the same way as show conditions (only earlier pages’ questions are available).
4. Save the form as usual.

💡 Example conditions

Show follow-up questions

• If “Were you hospitalized?” Equals Yes, show “Hospital name” and related tasks.

Skip what does not apply

• If “Employment status” Equals “Unemployed”, leave employment detail tasks hidden because their Show Condition does not match.

Completion-based

• Show a task only when an earlier task Is completed or Has any answer, without typing a comparison value.

Pro tip

Conditional logic keeps forms short and focused. Clients only see questions that matter to their situation. 🎯

🔀 Multiple rules

You can combine rules with AND or OR as described above. The editor explains whether every rule must match or any one rule is enough.

⚙️ Task Settings

Set up each task in the form:

📋 General Settings

Setting	Description
Name	The task title the client sees
Description	Instructions telling the client what to do
Info Blurb	Read-only context shown to the agent during the task
Agent Question	(Optional) Custom phrasing the voice agent reads instead of the task title — only affects the agent prompt, not the form
Required	The client must complete this task
Order	Where it appears in the section
Allow multiple values	For supported types (Email, Phone, Short Text, and the separate address line / city / state / ZIP field types), lets clients add a primary value plus Additional entries. Not shown for other field types.

When Allow multiple values is on, clients can enter more than one email, phone, short text, or text-style address part when your workflow needs it (for example, a primary and alternate number).

Agent Question

The Agent Question field is only used by voice agents (AI Receptionist). It lets you write a more natural, conversational question without changing the title shown on the form. If left empty, the agent uses the task title.

🧩 Field Mapping

Map form tasks to case type custom fields so answers are saved to the right case data fields.

Use Suggest Mapping to review likely task-to-custom-field matches across the form. Kayse compares unmapped task names with available custom fields for the selected case type, then shows suggested matches for confirmation before applying them.

Manual mapping remains available for tasks that need a different field or have no suggested match.

Creating Custom Fields from the Form Builder

If the custom field you need doesn't exist yet, you can create one without leaving the form editor:

1. Select a task in the form sidebar
2. Make sure a case type is assigned to the form (or selected in the campaign builder)
3. Click Create Kayse Custom Field below the field mapping dropdown
4. Enter a name for the new field
5. Click Create Field

The new custom field is added to the selected case type and automatically mapped to the current task.

✅ Validation Settings

Setting	Description
Min Length	Shortest allowed text
Max Length	Longest allowed text
Min Value	Smallest allowed number
Max Value	Largest allowed number
Pattern	A special format the answer must match
File Types	Which file types are allowed
Max File Size	The biggest file you can upload

🎨 Display Settings

Setting	Description
Placeholder	Example text shown in an empty field
Default Value	A value that's already filled in
Help Text	Extra tips for the client
Read Only	The client can see it but can't change it