> For the complete documentation index, see [llms.txt](https://docs.sprinthub.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sprinthub.com/en/common-questions/automation-template/360o-customer-support-automation-template.md).
# 360º Customer Support - Automation Template
Automation in 360 Customer Service (SAC) is essential to provide efficient, fast, and personalized support.
### Introduction
Using automation templates allows companies to respond quickly to customer requests, maintain consistency in responses, and optimize human resources. In this article, we will explore how to create an effective automation template for SAC 360, covering the essential steps and best practices.
### Steps to Create an Automation Template
#### Identifying Needs
Before creating a template, it is crucial to identify the specific needs of your customer service department. Do a detailed analysis of the main customer requests and questions. Classify these interactions by category, such as technical support, product questions, billing issues, etc.
**Click on automations in SAC 360º**
**When opening the automation screen, there will be a create template button just above it:**
**When you click it, a name, description, and whether the template is public or not will be requested.**
**What changes if the template is public or not?**
If yes, any and all users in your Sprinthub environment can access it; if not, you need to select who can view the template.
### Adding the template to a new automation
Click on "New automation":
**In the top-right corner, click on "Select Template":**
Then your automation will be identical to the previous one. This way, you can make changes and set it to run as if it were a new automation.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.sprinthub.com/en/common-questions/automation-template/360o-customer-support-automation-template.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.
