> For the complete documentation index, see [llms.txt](https://docs.ovaledge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ovaledge.com/release8.3/service-desk/service-desk-administration/cta-template-map-flow.md).
# CTA Template Map Flow
The system provides predefined service desk templates automatically mapped to Call To Action (CTA) buttons such as Suggest a Term, Content Change Request, and Data Quality Issue. These templates streamline the process of raising service requests directly from the UI.
Administrators can modify these mappings using the CTA - Template Mapping. By default, system templates are assigned to CTA buttons. However, if a system template is inactive, the corresponding CTA button will not have an associated template.
If custom templates exist for a specific request type and object type, administrators can map them to the relevant CTA button.
Connector-specific templates can be assigned to CTA buttons along with the Global Template. When clicking on the CTA button for the mapped connector, the connector-specific template is opened. For other connectors, the global template is opened.
---
# 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://docs.ovaledge.com/release8.3/service-desk/service-desk-administration/cta-template-map-flow.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.
