> For the complete documentation index, see [llms.txt](https://features.scnd.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://features.scnd.com/v2.0/front-office/contact-page.md).

# Contact page

Understanding and managing the ‘Contact us’ page used by users to communicate with your organization

{% hint style="info" %} <mark style="color:blue;">Path: Homepage > Contact us</mark>
{% endhint %}

* [Definition](#id-1.14.x-contactpage-definition)
* [Create a contact request](#id-1.14.x-contactpage-createacontactrequest)
* [Read the contact form](#id-1.14.x-contactpage-readthecontactform)
* [Update the contact page](#id-1.14.x-contactpage-updatethecontactpage)
* [Delete the contact page](#id-1.14.x-contactpage-deletethecontactpage)
* [Related resources](#id-1.14.x-contactpage-relatedresources)

## Definition <a href="#id-1.14.x-contactpage-definition" id="id-1.14.x-contactpage-definition"></a>

The contact us page allows users to contact the administrator of the platform via a form.

<mark style="color:red;background-color:yellow;">WHO CAN USE THIS FEATURE?</mark>

All users

## Create a contact request <a href="#id-1.14.x-contactpage-createacontactrequest" id="id-1.14.x-contactpage-createacontactrequest"></a>

A contact request is created when the user clicks the “Submit” button after filling the mandatory fields of the contact form and accepting the Recaptcha, Privacy policy, and Terms and Conditions.

## Read the contact form <a href="#id-1.14.x-contactpage-readthecontactform" id="id-1.14.x-contactpage-readthecontactform"></a>

The contact page is a form (figure 1) users have to fill out.

The following information is requested:

* First name
* Last name
* Email (to allow for administrator reply)
* Phone number
* The subject of the message
* Message

{% hint style="info" %} <mark style="color:blue;">All information boxes are mandatory except for the phone number.</mark>
{% endhint %}

<figure><img src="https://content.gitbook.com/content/n4EIoqjZx1xWQIo6LnjB/blobs/RyFMlXW6gB59QkLVeIXR/image.png" alt=""><figcaption></figcaption></figure>

Only the super-administrator or administrators (who have the right to do so) can see the message in the “Contact” section of the SBO: [Contact management](https://features.scnd.com/v2.0/superadmin/users/contact-management.md)

{% hint style="info" %} <mark style="color:blue;">Path: SBO > Users > Contact</mark>
{% endhint %}

## Update the contact page <a href="#id-1.14.x-contactpage-updatethecontactpage" id="id-1.14.x-contactpage-updatethecontactpage"></a>

Users can not update the contact page

## Delete the contact page <a href="#id-1.14.x-contactpage-deletethecontactpage" id="id-1.14.x-contactpage-deletethecontactpage"></a>

Users can not delete the contact page

## Related resources <a href="#id-1.14.x-contactpage-relatedresources" id="id-1.14.x-contactpage-relatedresources"></a>

**SBO :**

* [Contact management](https://features.scnd.com/v2.0/superadmin/users/contact-management.md)

**Business rules:**

* [Recaptcha feature - Business Rules](https://features.scnd.com/v2.0/core-concepts/recaptcha-feature.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://features.scnd.com/v2.0/front-office/contact-page.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
