> 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/field-operations/tasks/what-creates-website-requests-tasks.md). # What creates Service Requests tasks A Service Requests task is created when someone submits the public website intake form or requests service while signed in to the Customer Portal. Each submission becomes its own task in the single All folder, and the task identifies whether it came from the website or the portal. Website requests are checked against existing customer names and property addresses. High-confidence matches are highlighted in green. Similar names and addresses with small differences are highlighted as amber **Possible match** suggestions so you can review them before attaching. Possible matches are never attached automatically. The action at the bottom of **Request details** lets you attach the matching property or open the full customer or property form. Submitted address and contact details—including name, two phone numbers, types, and extensions—are prefilled so you can complete roles, required information, and custom fields before saving and attaching the request. Portal requests already know the signed-in account and email. The task shows a prominent Customer Portal source banner instead of matching tags for that authoritative account and selected property, and links directly to both Essential records. A request for a new property keeps the submitted address on the task; **Create New Property** opens the full property form with the account and address prefilled, and saving attaches the new property to the request. Once a property is attached, **Create New Contact** opens the full contact form for that customer and property. The Service Requests group appears once either request form has a published version. You work each request by moving it through its statuses; you change the status, not the folder. > **Where to find it:** Tasks page, the Service Requests group in the left sidebar (the All folder) ## Related guides * [How tasks are created and organized](/field-operations/tasks/how-tasks-are-created-and-organized.md) * [The Tasks inbox: folders, status filters, and search](/field-operations/tasks/the-tasks-inbox-folders-status-filters-and-search.md) * [What creates Deficiencies tasks](/field-operations/tasks/what-creates-deficiencies-tasks.md) * [What creates Invoices tasks](/field-operations/tasks/what-creates-invoices-tasks.md) * [What creates Jobs tasks (and moving them between folders)](/field-operations/tasks/what-creates-jobs-tasks-and-moving-them-between-folders.md) * [Let customers request service from the Customer Portal](/administration/settings/let-customers-request-service-from-the-customer-portal.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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://learn.withessential.com/field-operations/tasks/what-creates-website-requests-tasks.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.