by Industry
by App Stack
Professional Services
Education
Support
Learn how to quickly fix failed rows in your CSV imports. In this video, we download the failed rows file, use the error column to identify a missing reference via dot walking, correct the contact’s unique Work Email field, and re-upload only the corrected record so the import completes successfully. We’ll also highlight common causes of import failures and where to find the full import guide in the knowledge base.
Learn More
In this tutorial, I walk you through the process of importing ticket records into our ticket app using a clean CSV file and the import wizard. I explain the importance of formatting boolean fields as true or false, using unique identifiers like Work Email for contacts, and ensuring choice list fields match exactly with our app's values. After setting up the CSV, I demonstrate how to initiate the import and check the results, which showed that nine records were successfully added while one failed. I encourage you to refresh the page to monitor the import progress. Please follow these steps to ensure a smooth import process for your ticket records.
In this video, I walk you through the process of managing ticket visibility by roles and implementing Access Control Lists (ACLs) to secure sensitive information within our ticketing app. We created four roles: support agent, support lead, finance, and HR, and set specific permissions for each, such as allowing only the finance role to read, create, and edit billing details. I also demonstrated how to restrict access to certain sections and fields, ensuring that only authorized roles can view or modify them. Please make sure to review the roles and permissions assigned to your team and apply the same principles to any app and service as needed. Your attention to these details is crucial for maintaining our data security.
In this tutorial, I walk you through how to effectively filter and sort tickets to narrow down our workload to a more manageable number. We start by filtering out tickets that are not open and those waiting on customer replies, which helps us see a significant decrease in our ticket count. I also demonstrate how to focus on tickets with affected versions and set a specific time frame for resolution by selecting the SLA due date for November. Finally, I show you how to sort the tickets by the user they are assigned to, giving us a clearer view of our responsibilities. Please follow along and apply these filters to streamline your ticket management process.
A quick walkthrough to build dependent Choice Lists in Tickets. You’ll create a parent list (Service) and a child list (Integration), bulk-add their options, and link each child option to the parent value “Integration.” Then you’ll add two fields to the Tickets app: Service (Choice List: Service) and Integration (Choice List: Integration, Parent: Service). In use, when Service = Integration, the Integration field unlocks sub-options (Email, Voice, Documents); otherwise it stays inactive—keeping ticket data precise and easy to route.
A quick walkthrough to add and use an Affected Version text field in Tickets. You’ll create the field (with a 20-character cap and hint), optionally include it in Global Search, and log a bug ticket using it (e.g., 2.1.0). Then you’ll find related issues with a contains filter across list/Rolodex/board views and jump to records via Global Search. Finally, you’ll enforce consistency by adding a Form Rule that requires the field when Type = Bug.
By continuing, you agree to servis.ai Terms of Use. Read our Privacy Policy.
How can I be of servis?
[THIS DAY AND TIME]
You can’t schedule another one until your current meeting has passed.
We've received your booking and will get in touch to confirm the details.
