# Input

{% hint style="info" %}
Input cells are compatible with the [Dynamic Content](/user-guide/build-dialogs/dynamic-content-and-contexts.md) feature, and may store content for later usage.
{% endhint %}

The wait-input cell are used to wait for a user input, it stops the flow so the user can insert a information that will be interpreted by the agent.

{% hint style="warning" %}
Avoid accents when writing the stored input field, and in compound words, prefer underscores (\_) over spaces. With this syntax, you will make it easier when programming in technical cells, such as rule and code.
{% endhint %}

## **Templates**

### **Date**

Here, the user insert a specific date, ex January 3. This template activates a calendar where the user can select a date.

### **Time** 

The user insert a specific time, ex 3:15 pm. This template activates a clock where the user can select a time slot.

### **Custom** 

You define, using a specific pattern, the input structure. This is useful for country-specific information, such as ID numbers. In the Pattern field, your front-end team must enter the code that defines the field.

## Store Input 

For all templates, the switch **“Remember Input” will store the user answer for later use in the same session**.

**When building a flow, you may need to catch many user data to send to a company and return a response**. For example, in a bank account opening flow: you ask name, birth date, ID... Send this information to the institution and then inform the best bank account to the future client.

**In cases like this, you should create several Input cells and store all this information throughout the session will be stored (remember to hit the "Remember Input" button). And, very importantly, give different names, call to action, and descriptions to each Input cell.**

To make this "bridge" with the company, remember to add a [Service cell](/user-guide/build-dialogs/dialog-cells/services.md) at the end.

{% hint style="info" %}
**Important:**

* You can use those templates at the web/app/mobile channels
* It's also possible *(but not mandatory)* to add a call to action describing what information your user have to insert
  {% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.conversational-ai.syntphony.com/user-guide/build-dialogs/dialog-cells/input.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.