> For the complete documentation index, see [llms.txt](https://learn.withessential.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.withessential.com/administration/settings/let-customers-request-service-from-the-customer-portal.md). # Let customers request service from the Customer Portal Create and publish a service request form to give signed-in portal customers a **Request service** button. The portal fills the customer account and sign-in email automatically, so the form only needs to ask for details your team does not already know. Build the form with the same section-and-field editor as the website intake form. The portal form has its own versions and does not change the public website form. You can add Preferred Availability and custom questions such as a short description, service category, or requested date. Customer Name, Contact Info, and Property Address are not available as form fields because the portal supplies that context separately. ![A Customer Portal service request with the signed-in customer, email, and property already filled](https://3838208579-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Flu1pgNH0CrkCPslG8suQ%2Fuploads%2Fgit-blob-44eba709d3d64b4b61f6e22accc53e4aa4c88dbb%2Fcustomer-portal-service-request.png?alt=media) Select **Save** to publish the form. Once published, a portal customer can choose an existing property they are allowed to access. The **Property** dropdown includes search to find a site by its displayed name or address. Contacts with customer-level portal access can also select **Request service at a new property** and enter an address; the address uses your business's State, Province, or Region options and the matching ZIP or postal-code wording. Contacts whose access is limited to particular properties can request service only for those properties. Required questions must be completed before the request can be sent. With the picker open, use the arrow keys to move through results and Enter to choose a property; Escape closes the picker. ![A Customer Portal service request for a new property with its address filled](https://3838208579-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Flu1pgNH0CrkCPslG8suQ%2Fuploads%2Fgit-blob-ba0bc297947a7e1b5fd2a0091c188ef71f8e82a8%2Fcustomer-portal-new-property.png?alt=media) Every submission creates a task in **Tasks -> Service Requests -> All**. A prominent **Submitted through the Customer Portal** status pill and the signed-in email identify its source. Because the signed-in customer and selected existing property are authoritative, they do not carry matching-status tags; their links open the Essential customer and property records in a new tab. For a new address, select **Create New Property** at the bottom of **Request details** to open the full property form with the customer and submitted address prefilled. Complete any other required details or custom fields, then save to create the property and attach it to the request. ![A Customer Portal request task with prominent source context and links to its known customer and property](https://3838208579-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Flu1pgNH0CrkCPslG8suQ%2Fuploads%2Fgit-blob-7824fb1129e68def815a99e24287b9d3283986f4%2Fservice-request-customer-portal-source.png?alt=media) The **Request service** action appears only after the form has been saved and published. Your team is told the moment a request arrives: every back office user gets an in-app notification (each person can turn their own off under Personal Settings), and if you have set up a shared-inbox email copy on the Intake Form Notifications tab, portal requests are emailed there too. See [Get notified about new service requests](/administration/settings/get-notified-about-new-intake-form-submissions.md). > **Where to find it:** Settings -> Customer Portal -> Service request form ## Related guides * [What your customers see in the Customer Portal](/administration/what-your-customers-see-in-the-customer-portal.md) * [What creates Service Requests tasks](/field-operations/tasks/what-creates-website-requests-tasks.md) * [Build your intake form](/administration/settings/build-your-intake-form.md) * [Enable or disable the Customer Portal for all customers](/administration/settings/enable-or-disable-the-customer-portal-for-all-customers.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://learn.withessential.com/administration/settings/let-customers-request-service-from-the-customer-portal.md?ask=&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.