> 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/topics/general/sac-360/sac-360-filters.md). # SAC 360Β° - FILTERS The module of **SprintHub Customer Service** was developed to make it easier to manage support requests and ensure greater agility in customer support. One of the most important features for this are the **filters**, which allow you to organize conversations, prioritize requests, and quickly find any support ticket. {% embed url="" %} *** ### 🎯 What are the SAC filters? The **filters** work as a smart way to segment the support requests shown in the system. With them, you can view only the conversations that really matter at that moment, such as ongoing, completed, from a specific channel, or assigned to a specific agent. This organization makes the team’s routine easier, reduces search time, and improves support request management. *** ### βš™οΈ How to use the filters On the **SprintHub Customer Service**, the filters are located at the top of the panel. From there, it is possible to refine the support request list using different criteria. #### πŸ“± Platforms Allows you to view only the support requests coming from a specific platform, such as: * WhatsApp API * WhatsApp Web * Instagram * Facebook * Live Chat * Gmail * Outlook * IMAP This filter makes it easier to view support requests by communication channel, allowing the team to track only the conversations originating from the desired platform. *** #### 🏒 Accounts If your company has more than one integrated account (such as multiple WhatsApp numbers, email accounts, pages, or social media profiles), this filter allows you to view only the support requests belonging to the selected account. *** #### 🏷️ Tags Allows you to filter support requests that have one or more **tags** linked to the contact or the support request. This filter is very useful for quickly locating conversations related to campaigns, customer categories, priorities, or any other classification used by your operation. *** #### 🏒 Departments Displays only the support requests belonging to a specific department, such as: * Support * Sales * Finance * After-sales *** #### πŸ‘€ Responsible Shows only the support requests assigned to a specific agent. Ideal for tracking each employee’s workload queue. *** #### πŸ“Œ Stages (Status) Filters the support requests according to the current status, such as: * In progress * Waiting for reply * Resolved * Pending > πŸ’‘ Statuses are fully customizable, allowing each company to adapt the support flow to its needs. *** #### πŸ“… Period Allows you to view support requests within a specific date range, making daily, weekly, monthly, or custom queries easier. *** #### πŸ‘₯ Groups Defines whether **WhatsApp groups** should be shown or hidden in the SAC listing. *** ### ⚑ Advanced Menu The **Advanced** menu brings together additional options for specific queries and support request management. Among them are: * View all support requests; * Support requests without a department; * Unanswered support requests; * Support requests from ads; * Ignore restrictions *(available only for administrators).* *** ### πŸ”Ž Advanced Filters In addition to the quick filters, SprintHub offers an area of **Advanced Filters**, allowing you to create much more detailed searches by combining multiple conditions. With this feature, it is possible to add multiple search criteria, refining the results to find exactly the desired support requests. You can combine filters such as: * Platform; * Account; * Department; * Responsible; * Status; * Tags; * Period; * Support request origin; * And several other conditions available in the system. The more criteria are added, the more accurate the search becomes, making it much faster and more efficient to locate support requests. *** ### 🧠 Why use filters? Filters help your team to: * ⏱️ Save time by quickly locating specific support requests; * πŸ“‚ Better organize the workflow between departments and responsible agents; * πŸ“Š Analyze support requests by platform, account, period, or responsible agent; * 🏷️ Find conversations using tags and other classifications; * 🎯 Easily identify support requests from ads and other sources; * πŸš€ Make support more organized, productive, and strategic. With the correct use of filters, SAC management becomes much more efficient, allowing each employee to view only the support requests relevant to their routine. --- # 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/topics/general/sac-360/sac-360-filters.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.