The Tickets module is your comprehensive service management solution for tracking, managing, and resolving customer requests. It provides a single, unified workflow from ticket creation to resolution. With features like priority tracking, assignment workflows, and integration with other CRM modules, it helps you deliver consistent service while maintaining organized records of all support interactions.
Introduction
What is the Tickets Module?
The Tickets module is a comprehensive ticket management system that handles the entire lifecycle of customer support requests. From initial ticket creation through resolution and completion, the module provides tools to track issues, manage priorities, assign work, and maintain detailed records of all customer interactions.
The system is designed to streamline support operations by centralizing all customer issues in one place, making it easy to track progress, manage team workload, and maintain complete interaction history. The Tickets module provides a structured approach to service management with a single ticket type.
Why It's Essential for Customer Service
Effective ticket management is crucial for maintaining high customer satisfaction and operational efficiency. Without a proper system in place, support requests can easily fall through the cracks, leading to frustrated customers and overwhelmed support teams.
The Tickets module addresses these challenges by providing a centralized platform where all customer issues are organized, tracked, and managed systematically. This ensures that no request goes unnoticed and that urgent issues receive the attention they deserve. The module's priority management system helps teams focus on what matters most, while assignment workflows ensure that work is distributed evenly and efficiently.
By maintaining complete records of all customer interactions, the module enables support teams to provide personalized service based on historical context. This 360-degree view of each customer's support history helps teams understand recurring issues, identify patterns, and proactively address potential problems before they escalate.
Key Capabilities:
- Centralize all customer issues in one unified system
- Monitor ticket status from creation through resolution
- Prioritize urgent issues to ensure timely responses
- Distribute work efficiently across team members
- Maintain comprehensive interaction history
- Integrate seamlessly with other CRM modules
Key Benefits Overview
The Tickets module delivers significant value through its comprehensive feature set and seamless integration capabilities. One of the most powerful aspects is the 360-degree customer view, which provides complete visibility into all tickets, interactions, and history for each customer. This holistic perspective enables support teams to understand customer needs better and deliver more personalized service.
The module's streamlined workflow ensures that tickets move efficiently from creation to resolution, reducing response times and improving customer satisfaction. Optional equipment fields let you record brand and serial number for assets when relevant, so you can track service history in ticket notes and activity.
Primary Benefits:
- Complete customer interaction history in one place
- Streamlined workflow from ticket creation to resolution
- Optional equipment details (e.g. brand, serial number) when relevant
- Automatic activity logging for all ticket changes
- Seamless integration with the Finance module for service invoicing
Who Should Use This Module?
The Tickets module is essential for any organization that provides customer support or service delivery. Support teams benefit from the organized workflow and assignment capabilities, which help them manage customer requests and technical issues more effectively.
Customer success teams use the module to monitor customer satisfaction and track issue resolution metrics, helping them identify areas for improvement. Business owners gain valuable insights into support workload and customer needs, enabling data-driven decisions about resource allocation and service improvements. Service managers oversee ticket assignment and resolution workflows, ensuring that their teams operate efficiently and maintain high service standards.
Core Features
Ticket Creation and Management
The Tickets module provides comprehensive ticket management with a single, unified ticket type. When creating a ticket, the system automatically generates a unique case number (format YYMMDDXXX) for tracking and reference. Each ticket is linked to a customer via the Owner Card: you can associate it with an individual, an organization, or use an external reference or memo when the customer is not yet in the CRM.
The priority system lets you classify tickets as low, medium, high, or urgent so critical issues get immediate attention. Status is tracked through four stages: Open, In progress, Completed, and Closed. In the UI, the "In progress" stage is displayed as "Parked" so you can put tickets on hold (e.g. waiting for parts or customer response) while keeping them in the active workflow.
Core Capabilities:
- Single unified ticket type (no support vs repair types)
- Automatic case number generation (YYMMDDXXX format)
- Owner Card: link to individual, organization, external reference, or memo
- Four-level priority: low, medium, high, urgent
- Four statuses: open, in progress (shown as "Parked"), completed, closed
- Issue description (required) and optional equipment details when relevant
Priority and Status Management
The priority system helps teams focus on what matters most. Low priority is for non-urgent issues; medium for standard requests; high for issues needing prompt resolution; and urgent for critical issues requiring immediate attention.
The status workflow has four stages. New tickets start as Open (awaiting assignment or review). When work starts, set status to In progress (displayed as "Parked" in the UI), which is also used for temporary holds. When the issue is fixed, set Completed; when fully confirmed and done, set Closed.
Priority Levels:
- Low: Non-urgent issues
- Medium: Standard priority, timely attention
- High: Important, prompt resolution
- Urgent: Critical, immediate attention
Status Workflow (database values; UI may show "Parked" for in progress):
- Open: New ticket awaiting assignment or review
- In progress: Actively being worked on or on hold (UI label: "Parked")
- Completed: Work done, may await confirmation
- Closed: Fully completed and closed
Optional Equipment Details
When a ticket involves a specific asset, you can record equipment details (e.g. brand, serial number) in the ticket. This is optional and available for any ticket, helping you maintain service history for assets when needed.
Assignment and Workflow
The assignment system provides flexible options for distributing work across team members. Tickets can be manually assigned to specific team members through the assignment dropdown, or team members can claim tickets themselves using the "Claim" button. This self-service approach reduces management overhead while empowering team members to take ownership of work.
The system also supports quick assignment through context menu actions, allowing managers to quickly assign tickets directly from the list view. When needed, assignments can be removed, making tickets available for other team members. The system maintains a complete assignment history, tracking who worked on each ticket throughout its lifecycle.
Assignment Options:
- Manual assignment to specific team members
- Self-assignment via "Claim" button
- Quick assignment through context menu
- Assignment removal when needed
- Complete assignment history tracking
Email notifications: You can opt in at Settings ā Notifications to receive an email when someone assigns a ticket to you. Self-assignment (claiming) does not send emails. See How to Configure Email Notifications for Assignments for details.
Communication History
Every interaction with a ticket is automatically tracked by the system, creating a comprehensive audit trail of all changes and communications. This automatic activity logging ensures that nothing is missed and provides complete transparency into the ticket's history.
In addition to automatic logging, team members can add manual notes to document customer conversations, phone calls, or other interactions that may not be automatically captured. When email integration is enabled, email communications are also tracked within the ticket, providing a unified view of all customer communications.
Communication Tracking:
- Automatic activity logging for all changes
- Manual notes for customer conversations
- Email integration for communication tracking
- Resolution notes documenting how issues were fixed
- Invoice notes for billing purposes
Getting Started
Accessing the Tickets Module
To access the Tickets module, navigate to it from the main navigation menu. The module opens with a master-detail view that displays all tickets in an organized list. The interface provides a search bar to find tickets by issue description, case number, or other fields. Filter buttons let you filter by status: all, open, in progress (Parked), or completed.
Creating Your First Ticket
Creating a ticket is a straightforward process. Click "Create Ticket" in the tickets list to open the create modal.
Step 1: Owner and issue Use the Owner Card to link the ticket to a customer: select an individual or organization from search, or use external reference or memo if the customer is not in the CRM. Enter the issue description (required)āthis describes the problem and is the main content of the ticket. Set priority (low, medium, high, or urgent) to indicate how urgently the ticket needs attention.
Step 2: Assignment (optional) Optionally assign the ticket to a team member. You can also leave it unassigned; team members can claim it later.
Step 3: Save Click "Create" to save. The system assigns a unique case number (YYMMDDXXX). The ticket appears in the list with status "Open", ready to be worked on. You can add equipment details (e.g. brand, serial number) when editing the ticket if relevant.
Understanding the Ticket Interface
The ticket interface is organized into two main panels that work together to provide comprehensive ticket management. The master panel on the left side displays a list of all tickets with key information visible at a glance, including case number, title, customer, status, and priority. This panel includes search and filter controls that make it easy to find specific tickets, status filter buttons for quick filtering, and bulk selection capabilities for performing operations on multiple tickets at once.
The detail panel on the right side shows complete ticket information when a ticket is selected from the list. This panel includes tabs for different views: Overview for general ticket information, Equipment for equipment details and history, Billables for billing information, and Activity for a complete history of all ticket changes and interactions. Edit and action buttons provide quick access to common operations, while related information and history help provide context about the customer and previous interactions.
Core Functionality
Unified Tickets
All tickets use the same type; there is no separate "support" or "repair" type. Each ticket has an issue description, priority, assignment, and owner (individual, organization, external reference, or memo). Optional equipment fields are available when editing a ticket if you need to record asset details.
Status Management
Status is stored as one of four values: open, in_progress, completed, closed. In the UI, "In progress" is displayed as Parked, so you can put tickets on hold without losing their place in the workflow.
You can change status from the ticket detail (status dropdown) or from the list (context menu). Bulk operations let you update status for multiple tickets at once. Typical flow: Open ā In progress (Parked) ā Completed ā Closed. Direct closure from any status is available when needed.
Priority Management
Priority management helps teams focus on the most critical issues first, ensuring that urgent problems receive immediate attention while standard requests are handled in a timely manner. The priority system uses a four-level classification that helps teams allocate resources effectively.
When setting priorities, use the priority dropdown in the ticket detail view and consider both customer impact and urgency. It's important to update priority as the situation changes, as an issue that starts as medium priority might become urgent if it escalates. High and urgent priorities should always be addressed first, as these represent issues that have significant impact on customers or business operations.
Priority Guidelines:
- Urgent: System outages and critical business impact requiring immediate attention
- High: Important features broken with significant customer impact
- Medium: Standard support requests and normal operations
- Low: Minor issues, feature requests, and non-critical items
Assignment Workflows
The assignment system provides flexible options for distributing work across team members, ensuring that tickets are handled by the right people at the right time. Manual assignment allows managers to select specific team members from the assignment dropdown, while self-assignment enables team members to claim tickets themselves using the "Claim" button.
For quick assignment, you can right-click on a ticket in the list to access the context menu, which provides fast assignment options without opening the full ticket detail. When needed, assignments can be removed, making tickets available for other team members to claim.
Assignment Best Practices: Effective assignment requires balancing expertise and workload. Assign tickets based on team members' areas of expertise and current workload to ensure efficient resolution. Use assignment strategically to balance team workload, and don't hesitate to reassign tickets if a team member becomes unavailable or overloaded. Tracking assignment history provides valuable insights for performance analysis and workload management.
Optional Equipment Details
When a ticket involves a specific asset, you can record equipment details (e.g. brand, serial number) in the ticket. Navigate to the Equipment tab in the ticket detail view, enter brand name and serial number if known, and add any other details. The system can track tickets by equipment so you can review service history for that asset when needed.
Finance Integration
The Finance module integration lets you convert ticket work into billable items for invoicing. Navigate to the Billables tab in the ticket detail view to add billable items (services from your catalog, custom parts, labor), set quantities and prices, and link to opportunities for invoicing. The system tracks billable status and supports invoice generation when Stripe is configured.
Best Practices
Ticket Creation Best Practices
Writing clear, detailed descriptions is essential for effective ticket resolution. When creating tickets, be specific about the issue, including any error messages that might help diagnose the problem. Mentioning steps to reproduce the problem helps support teams understand the issue more quickly, while noting any troubleshooting already attempted prevents duplicate work.
Setting appropriate priorities is crucial for maintaining an efficient support workflow. Use urgent priority only for critical issues that require immediate attention, and always consider customer impact when setting priority levels. It's important to review and adjust priorities regularly as situations change, and avoid overusing high priority, as this can lead to priority inflation where everything seems urgent.
Linking tickets to customers properly ensures that all customer interactions are properly tracked and accessible. Always link tickets to the correct individual or organization, using the customer search to find existing records when possible. If a customer record doesn't exist, create a new one to maintain complete customer history. Always verify that customer information is accurate to ensure proper tracking and communication.
Status Management Best Practices
Keeping ticket status updated is essential for maintaining visibility into support operations. Update status as work progresses, moving tickets to "Completed" when issues are fixed, and closing them promptly after customer confirmation. Avoid leaving tickets in "In Progress" indefinitely, as this reduces visibility into actual work status and can lead to tickets being forgotten.
Using status transitions correctly ensures that tickets follow the proper workflow. Move tickets from "Open" to "In Progress" when starting work, from "In Progress" to "Completed" when the issue is fixed, and from "Completed" to "Closed" after customer confirmation. The system also allows direct closure from any status for administrative purposes, which should be used sparingly and only when appropriate.
Assignment Best Practices
Balancing workload effectively requires careful attention to both individual capacity and expertise. Distribute tickets evenly among team members to prevent burnout and ensure fair work distribution. Consider each team member's expertise when assigning tickets, matching tickets to the right skills. Monitor individual workloads regularly and don't hesitate to reassign tickets if a team member becomes overloaded.
Encouraging self-assignment empowers team members and reduces management overhead. When team members can claim tickets themselves, they take ownership of the work and can respond more quickly. This approach also improves response times, as team members can immediately claim tickets they're qualified to handle without waiting for assignment.
Communication Best Practices
Adding detailed notes ensures that all customer interactions are properly documented and accessible to the entire team. Document all customer interactions, including phone call summaries, email communications, and resolution steps. This comprehensive documentation helps maintain continuity when tickets are transferred between team members and provides valuable context for future interactions.
Updating customers regularly is essential for maintaining customer satisfaction and managing expectations. Keep customers informed of progress on their tickets, set clear expectations for resolution time, and communicate delays proactively when they occur. Always confirm resolution with customers before closing tickets, ensuring that they're satisfied with the solution.
Equipment Tracking Best Practices
Maintaining accurate equipment records is essential for effective service management. Always enter brand and serial number when available, as this information is crucial for tracking service history and identifying recurring issues. Keep equipment information up to date, and link related tickets to the same equipment to build a complete service history.
Using equipment history effectively helps identify patterns and improve service quality. Review equipment history regularly to identify recurring issues that might indicate underlying problems. This information can help plan preventive maintenance, track warranty information, and ultimately improve service quality by addressing root causes rather than just symptoms.
Integration with Other Modules
Individuals Module Integration
The Tickets module integrates seamlessly with the Individuals Module:
- Link Tickets to Individuals: Connect support requests to customer contacts
- View Ticket History: See all tickets for a specific individual
- Contact Information: Access customer details directly from tickets
- Communication History: Track all interactions in one place
Organizations Module Integration
Connect tickets to companies through the Organizations Module:
- B2B Support: Link tickets to organizational customers
- Account Management: Track all tickets for a company account
- Multi-Contact Support: Handle tickets for organizations with multiple contacts
- Company History: View complete support history for organizations
Opportunities Module Integration
Link tickets to sales opportunities:
- Pre-Sale Support: Track support requests during sales process
- Post-Sale Support: Connect tickets to won opportunities
- Customer Journey: See complete customer interaction history
- Revenue Tracking: Understand support costs vs. sales value
Services Module Integration
Use services from your catalog in tickets:
- Service Selection: Add services to ticket billables
- Pricing: Use catalog prices for consistent billing
- Service History: Track which services are used most
- Catalog Management: Maintain service offerings
Finance Module Integration
Convert ticket work to billable items:
- Service Billing: Bill for support services provided
- Parts and Labor: Track billable parts and labor hours
- Invoice Generation: Create invoices from ticket billables
- Revenue Tracking: Track billable revenue from support
Tasks Module Integration
Create tasks related to tickets:
- Follow-Up Tasks: Schedule follow-up activities
- Task Assignment: Assign ticket-related tasks to team members
- Task Tracking: Monitor task completion
- Workflow Management: Organize ticket-related work
Notes Module Integration
Add notes to tickets:
- Internal Notes: Document internal discussions
- Customer Notes: Record customer conversations
- Resolution Notes: Document how issues were resolved
- Knowledge Sharing: Share information with team
Knowledge Base Integration
Link tickets to knowledge base articles:
- Solution Articles: Reference helpful articles when resolving tickets
- Self-Service: Help customers find answers themselves
- Article Creation: Create articles from common ticket resolutions
- Knowledge Sharing: Build knowledge base from ticket solutions
Use Cases
Use Case 1: Technical Support Request
Scenario: A customer reports a software issue
Steps:
- Customer contacts support via email or phone
- Support team creates a new ticket with type "Support"
- Link ticket to customer's individual or organization record
- Set priority based on issue severity
- Assign to appropriate technician
- Technician updates status to "In Progress"
- Technician works on issue and adds notes
- Issue resolved, status changed to "Completed"
- Customer confirms resolution, ticket closed
Benefits:
- Complete record of the support interaction
- Clear assignment and accountability
- Customer history maintained
- Performance tracking possible
Use Case 2: Equipment Repair
Scenario: Customer needs equipment repaired under warranty
Steps:
- Create ticket with type "Repair"
- Link to customer (individual or organization)
- Add equipment details (brand, serial number)
- Set priority (usually high for warranty repairs)
- Assign to repair technician
- Technician updates work description
- Add billable items if warranty doesn't cover all costs
- Mark as resolved when repair complete
- Close ticket after customer confirmation
Benefits:
- Equipment history tracked
- Warranty information maintained
- Billing handled correctly
- Service quality monitored
Use Case 3: Equipment Repair with History
Scenario: Customer needs equipment repaired, and you want to track service history
Steps:
- Create ticket with type "Repair"
- Link to customer (individual or organization)
- Add equipment details (brand, serial number)
- Set appropriate priority
- Assign to repair technician
- Technician updates work description with repair details
- System automatically links to equipment history
- Review equipment history to identify any recurring issues
- Mark as completed when repair is finished
- Close ticket after customer confirmation
Benefits:
- Complete equipment service history maintained
- Recurring issues easily identified
- Warranty information tracked
- Service quality improved through historical data
Use Case 4: B2B Account Support
Scenario: Supporting a business customer with multiple contacts
Steps:
- Create ticket linked to organization (not individual)
- Multiple contacts from organization can reference same ticket
- Assign to account manager
- Track all interactions in ticket notes
- Link to related opportunities if applicable
- Add billable items for services provided
- Generate invoice from billables
- Close ticket after resolution
Benefits:
- Account-level support tracking
- Multiple contact management
- Billing integration
- Relationship management
Use Case 5: High-Priority Issue Escalation
Scenario: Urgent system outage affecting multiple customers
Steps:
- Create ticket with "Urgent" priority
- Link to primary affected organization
- Assign to senior technician immediately
- Update status to "In Progress" immediately
- Add notes about impact and affected customers
- Create related tickets for other affected customers
- Link related tickets together
- Resolve all related tickets when issue fixed
- Close tickets after customer confirmation
Benefits:
- Urgent issues prioritized
- Related issues tracked together
- Impact assessment possible
- Resolution time tracked
Conclusion
The Tickets module is a powerful tool for managing all aspects of customer support and service delivery. By following best practices, maintaining accurate records, and leveraging the module's integration capabilities, you can provide exceptional customer service while maintaining organized records of all support interactions.
Key Takeaways:
- Organization: Centralize all support requests in one system
- Efficiency: Streamlined workflows from creation to resolution
- Tracking: Complete history of all customer interactions
- Integration: Seamless connection with other CRM modules
- Billing: Easy conversion of support work to billable items
- Quality: Maintain high service standards with proper tracking
Next Steps:
- Create your first ticket to familiarize yourself with the interface
- Set priorities and assignment workflows for your team
- Integrate with other modules (Individuals, Organizations, Services)
- Train your team on ticket management best practices
- Review ticket metrics regularly to improve service quality
Start by creating a few test tickets and exploring the various features. As you become more familiar with the module, you'll discover how it can streamline your support operations and improve customer satisfaction.
Frequently Asked Questions
What is the Tickets module used for?
The Tickets module is used for managing customer support requests and technical issues. It provides a single, unified workflow from ticket creation through resolution, with priority management, assignment, optional equipment details, and integration with the Finance module for billing.
How do I create a new ticket?
Click "Create Ticket" in the tickets list. In the modal, set the Owner (individual or organization, or external reference/memo), enter the issue description (required), set priority, optionally assign to a team member, and click "Create". The system generates a unique case number (YYMMDDXXX).
What do the statuses mean?
Tickets have four statuses: Open (new), In progress (shown as "Parked" in the UIāused for active work or temporary hold), Completed, and Closed. Use "Parked" when work is in progress or when you are waiting on the customer or parts.
How do I assign a ticket to a team member?
You can assign tickets in several ways:
- Use the assignment dropdown in the ticket detail view
- Click "Claim" to assign the ticket to yourself
- Right-click on a ticket in the list for quick assignment via context menu
- Use bulk operations to assign multiple tickets at once
What is the difference between "Completed" and "Closed" status?
Completed means the issue has been fixed but the customer hasn't confirmed yet. Closed means the ticket is fully completed and the customer has confirmed the resolution. Tickets typically move from Completed to Closed after customer confirmation.
How do I set the ticket owner?
Use the Owner Card when creating or editing a ticket. You can link to an individual or organization from the CRM, or use external reference or memo when the customer is not in the system. Only one owner type is used per ticket.
How do I add equipment details?
Equipment is optional. When relevant, open the ticket and go to the Equipment tab. Enter brand name and serial number; the system can associate tickets with that equipment for service history.
Can I convert ticket work to billable items?
Yes. Open the ticket and go to the Billables tab. Add services from your catalog or custom line items, set quantities and prices, and link to opportunities. Invoice generation is available when the Finance module and Stripe are set up.
How does the Tickets module integrate with other modules?
The Tickets module integrates with:
- Individuals Module: Link tickets to customer contacts
- Organizations Module: Link tickets to company accounts
- Opportunities Module: Connect tickets to sales opportunities
- Services Module: Use services from catalog in billables
- Finance Module: Convert ticket work to billable items
- Tasks Module: Create follow-up tasks related to tickets
- Notes Module: Add notes to tickets
- Knowledge Base: Link tickets to helpful articles
How do I search for specific tickets?
Use the search bar at the top of the tickets list. You can search by case number, issue description, customer name, or other ticket fields. The search filters the list as you type.
Can I change ticket priority after creation?
Yes, you can change the priority at any time. Use the priority dropdown in the ticket detail view. Consider updating priority if the situation changes or if you receive new information about the issue's impact.
What happens when I close a ticket?
Closing a ticket marks it as fully completed. The ticket remains in the system for historical records but is filtered out of active ticket lists. You can still view and reference closed tickets, and they appear in customer history and reports.
How do I track ticket resolution time?
The system automatically tracks when tickets are created, when status changes occur, and when tickets are closed. You can view this information in the ticket detail view and use it for performance analysis and reporting.
Can I create tickets from other modules?
Yes, you can create tickets from the Individuals and Organizations modules. When viewing a customer record, you can create a new ticket directly linked to that customer, making it easy to log support requests during customer interactions.