# 4.3.5 Service sheet ##

## How it works ### **Service name** This helps people understand what your service does and whether they need to use it. ### **Documents and any fees required** A list of things most users need to know: for example, what your service is, what will happen, what users will get or how much it'll cost. To keep the content concise, do not include details about anything that would be obvious to users. ### **A call-to-action** There should be a clear call to action button to start the service, usually “Start now”. You should also include a link to “sign in” or “continue journey” if the user is able to continue an existing journey. ### **Other ways to access the service** You should provide ways for people who can’t access the service online to get support, for example, by phone or text relay. You may also include details for support channels. ## **When to use this pattern** At the start of a service which involves the user inputting information in order to get something. For example, at the start of an application form. --- # 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://specs.govstack.global/overview/23q4/govstack-ui-ux-guidelines/4-design-patterns/6-page-templates/7.9-service-sheet.md?ask= ``` 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.