> For the complete documentation index, see [llms.txt](https://specs.govstack.global/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://specs.govstack.global/service-patterns/2.-functional-patterns/find-a-service.md).

# Find a service

Enable users to discover the right service and reach a trusted starting point, regardless of channel, entry point, or level of certainty.

## Steps

{% @mermaid/diagram content="---
config:
layout: dagre
-------------

flowchart LR
B\["Search engine etc"] --> n2\["Service catalogue"]
B1\["Browse topic"] --> D\["Service sheet"]
A\["Kiosk / Service centre / Information poster"] --> D
C\["Direct link <br>(notification)"] --> D
D --> E\["Continue through service"]
n2 --> B1
F\["Handoff within <br>wider service"] --> E
" %}

<details>

<summary><strong>Example user flow</strong></summary>

<figure><img src="https://content.gitbook.com/content/u8moxPbFWK9pTxPYNIyh/blobs/CXCDOaMbvJzA4Hc0LbXM/Find%20a%20service.png" alt=""><figcaption></figcaption></figure>

</details>

#### 1. Discover services

Users discover services through one or more routes or channels.

This may include:

* browsing a [service or topic catalogue](/service-patterns/3.-step-patterns/service-catalogue.md) or using the search function
* offline information sources such as posters, leaflet, signage or frontline staff to support [offline services](/service-patterns/2.-functional-patterns/other-ways-to-access-a-service.md)
* arriving directly at the service from an external search engine or referral link.

#### 2. Confirm service relevance

Users reach a service page or equivalent with information that helps them confirm they have found the right service for their needs.

This step should:

* confirm what the service is for
* explain who it’s for
* set expectations before starting

Use a [service sheet](/service-patterns/3.-step-patterns/service-sheet.md) to help users understand what the service is and prepare them to start.

<br>


---

# 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://specs.govstack.global/service-patterns/2.-functional-patterns/find-a-service.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.