> For the complete documentation index, see [llms.txt](https://wiki.lucysecurity.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.lucysecurity.com/application-reference/templates/campaign-templates.md).
# Campaign Templates
Campaign templates can help you get started quickly.
{% hint style="info" %}
Navigate to **Templates > Campaign Templates**.
{% endhint %}
***
## Creating a Campaign Template
To create a campaign template go to the campaign's **Summary** tab and select **Actions > Save as Template**.
## Creating a Campaign from a Template
The campaign template can now be used when [creating a campaign in expert mode](/application-reference/campaigns/expert-mode.md) to quick-start your campaign creation. Just select the template from the list and **Save**.
{% hint style="warning" %}
Recipients are not saved in campaign templates. If you included a schedule in your campaign template you must edit the schedule rule to re-bind your recipients to it after adding them to the campaign.
{% endhint %}
---
# 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://wiki.lucysecurity.com/application-reference/templates/campaign-templates.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.
