# Prerequisites & Data Collection

## The Prerequisites Flow

Depending on the selected service's Prerequisite configuration, the portal may ask the customer for a phone number, email, or customer ID.

<figure><img src="/files/qzZS7NFri8MDk3CER46H" alt="" width="463"><figcaption><p>The Portal's Service Settings / Prerequisites Dialog</p></figcaption></figure>

The following diagram depicts the prerequisites flow:

<figure><img src="/files/rOCsJnxz2c3TpqzQq7Iy" alt=""><figcaption><p>Prerequisites Flow</p></figcaption></figure>

For example, if the service is configured to require a phone number and OTP, the following pages will be displayed:

<figure><img src="/files/HbkActMEIUbgn3JSXRs0" alt="" width="563"><figcaption><p>The Portal's Phone Number and OTP Pages</p></figcaption></figure>

### Require Customer ID

If the service requires a customer ID, the portal will ask the customer to identify himself.

Depending on the "Customers" table self-authentication configuration, the portal will ask for key and validation fields or a customer ID and OTP.

<figure><img src="/files/bw9wYqmEokVfYw6llcal" alt=""><figcaption><p>The Portal Self-authentication Pages</p></figcaption></figure>

To learn how to configure customer self-authentication, see:

{% content-ref url="/spaces/8vfRpZGqpk7N0egaXMQ8/pages/wxhEV21ARVXI5HSy589Z" %}
[The Customers Data Table](/guides/understanding-the-basics/process-management/the-customers-data-table.md)
{% endcontent-ref %}

## **Data Collection**

If the selected service's category configures one or more **required** fields, the portal will ask the customer to provide values for these fields.

Example: Setting First Name  and Last Name as required fields on the service category:

<figure><img src="/files/QszozFN2RYRIVmGoE807" alt="" width="563"><figcaption><p>The Service Category / Fields Page</p></figcaption></figure>

The portal will ask the customer to enter the information:

<figure><img src="/files/6eQ3SfrSJF7qonH9Dew5" alt="" width="327"><figcaption><p>The Portal's Data Collection Page</p></figcaption></figure>


---

# 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.cubu.com/guides/understanding-the-basics/portals/prerequisites-and-data-collection.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.