> For the complete documentation index, see [llms.txt](https://knowledge.out-smart.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge.out-smart.com/mobile-app/ios-outsmart-app/module-overviews/work-order/snippets-quick-text.md).

# Snippets (quick text)

Insert reusable text snippets into work order text fields.

## Snippets (quick text)

### Snippets (quick text)

**Snippets** are reusable text fragments for work order fields. They save time when you enter the same text repeatedly.

#### Where you can use snippets

* Work description, internal memo, and short description.
* Comments.
* Text fields in forms.

#### Insert a snippet

{% stepper %}
{% step %}

#### Open a text field

Tap a supported text field.

For example, open the work description or a comment.
{% endstep %}

{% step %}

#### Open the snippets picker

Choose the snippet option for that field.
{% endstep %}

{% step %}

#### Find and insert

Search for a snippet and tap it.

Its text is inserted at the cursor.
{% endstep %}
{% endstepper %}

#### Keep in mind

* Snippets are created and managed in BackOffice.
* If none are available, the list shows **No Snippets**.
* Some snippets add dynamic values, such as location or a dated employee tagline.


---

# 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://knowledge.out-smart.com/mobile-app/ios-outsmart-app/module-overviews/work-order/snippets-quick-text.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.