OTOBO | MAKE PEOPLE SMILE. IT’S EASY.

Ticket Management | Case Management

All information about a process at a glance.

TICKET MANAGEMENT | CASE MANAGEMENT

Benefits

  • Improved collaboration

    Put an end to organizational and process silos, enhance internal communication, and facilitate cross-team handling of operations.

  • Happier employees and customers

    Turn service into an experience and keep users informed about the status of their requests.

  • Comprehensive case management

    Complex cases, including all information and associated processes, are displayed compactly and clearly.

  • Better decision making

    Insightful reports and analyses help optimizing the service organizations performance, identifying bottlenecks, and making data-driven decisions.

  • Time savings

    Efficient ticket forms ensure faster creation of support requests, incident reports, and service inquiries.

  • Increased transparency

    You always maintain full visibility of open tasks and address time-sensitive operations with higher priority.

  • Risk mitigation

    Automating recurring tasks and processes increases teams’ efficiency and reduces the risks of failures.

  • Maintaining service quality

    You avoid SLA breaches, penalties, and reputational damage, ensuring satisfied customers.

TICKET MANAGEMENT | CASE MANAGEMENT

Capabilities

Effective ticket management helps make support more efficient, shorten response times, and improve service quality. When things get busy at the service desk, the service team needs efficient tool support to focus on solving problems and process tickets quickly and efficiently. The core functionality of OTOBO is that of an open source ticket system, which supports you in efficiently capturing requests, properly prioritizing them, automatically routing them to the appropriate team, and monitoring processing progress.

Efficient ticket creation

Ticket Management | OTOBO 1

There are many roads to a new ticket

Let employees and customers choose their preferred communication channel. Whether through the self-service portal on the website or intranet, email addresses, or the telephone hotline – OTOBO automatically creates a traceable ticket for each process. Incoming calls can be efficiently documented with dynamically generated ticket forms that adapt to the context at runtime.

The status of a process has changed, the system monitoring identifies an anomaly, or an integrated third-party system communicates via a web service – OTOBO automatically creates a new ticket.

Ticket Management | OTOBO 2

Ticket prioritization and classification

Tickets created via the self-service portal are automatically prioritized by OTOBO and subsequently sorted based on priority to ensure important tasks are addressed first. Tickets created via email or phone are manually prioritized by service agents. OTOBO automatically assigns operations to the correct team, sets Service Level Agreements (SLAs), or groups tickets for analysis and reporting purposes.

You can conveniently integrate additional category trees into ticket forms with dynamic fields and use them as triggers for automated processes.

Ticket Management | OTOBO 3

State-of-the Art Richtext-Editor

OTOBO offers the widely used WYSIWYG editor CKEditor 5, providing state-of-the-art functionality. You can format tickets as rich text, add images, links, and other multimedia elements or attachments. The editor simplifies the creation of visually formatted ticket responses, comments, and internal notes.

Flexibly customizable ticket forms

Light and compact ticket forms save valuable time – for your team but also for the user. OTOBO offers numerous ways to easily customize and visually lighten forms or adjust them at runtime to the context and previous inputs.

Using dynamic fields, you can easily and flexibly add relevant information to your tickets during the process, such as additional contact details, product information, data from the CMDB, or external databases, or adjust them as needed.

Ticket Management | OTOBO 4
  • Allow field values to be calculated using script fields

    Check conditions or calculate field values based on references to other fields. The result can be displayed in the ticket to initiate follow-up processes or affect the visibility of fields.

  • Group fields into DynamicFieldSets

    Multiple dynamic fields can be grouped as a set to incorporate them as a fixed element.

  • Add dynamic fields at runtime

    Add or remove dynamic fields or predefined field sets at runtime via the form using ⊕ | ⊖.

  • Utilize references to other data

    Use references to directly access OTOBO objects such as Agent, Customer (User), Ticket, CI, or CI Version – e.g. to access the CMDB from customer management. In combination with lens fields, even attributes within the referenced objects can be targeted and their values adjusted.

  • Design ticket forms even more easily

    Using the YAML editor, configuring ticket forms is simple and fast. For example, you can adjust the order of fields, assign individual labels, create multi-column forms, or mark fields as read-only to display values that should not be changed.

  • Incorporate rich text fields

    Using DynamicFields of the Richtext type and CKEditor 5, you can use HTML-formatted text within forms and processes.

  • Centrally manage list selection fields

    With the dynamic field General Catalog, you can centrally manage list selection fields and use them simultaneously in different forms.

  • Incorporate uploads and downloads of attachments

    Provide attachments at any point in the process or integrate an option to upload documents into you form.

Automated routing and dispatching of tickets

Auto-Routing

Incoming requests are quickly and effectively routed to the appropriate teams. Auto-routing improves response time and leads to more efficient resource utilization.

Auto-routing in OTOBO is based on rules and classification criteria, such as ticket categories, priorities, or individually configurable attributes. It is activated once the conditions of the routing rules are met, e.g. whenever a ticket reaches a certain status. For each routing rule, you specify which team is responsible in that case. OTOBO takes care of the rest, automatically moving the ticket to the correct workspace.

Ticket Management | OTOBO 5
Ticket Management | OTOBO 6

Move and assign tickets manually

Need more flexibility and control to assign tickets to the right team, especially when specific expertise is required?

Through roles and permissions, you control which employees can forward tickets to the next process stage and thus to the next responsible team. OTOBO ensures that the new ticket owners are automatically notified.

Efficiently process your tickets

Link related tickets and cases

Keep track and link related incidents to document relationships, dependencies, or thematic connections. Tickets can also be linked to:

  • Customer data

    to track the history of customer support requests and interactions.

  • Entries from the knowledge base

    to provide detailed information and solution suggestions to your service agents, employees, or customers.

  • IT or non-IT assets from your CMDB

    to establish references to Configuration Items (CI) from the Configuration Management Database (CMDB).

  • Appointments and events

    to provide information about scheduled deployments or meetings.

Ticket Management | OTOBO 7

Merge and split tickets

Merge multiple tickets into one target ticket, all articles from the currently processed ticket are chronologically sorted into the target ticket, and the originating ticket receives the status ‘merged.’ If you want to handle a process through multiple teams or outsource certain contents from the history, you split the ticket. Both tickets remain linked.

Ticket Management | OTOBO 8

Ticket bulk actions

Save valuable time by simultaneously handling multiple tickets. Apply actions such as status changes, moving to another queue, or assigning an owner to multiple tickets at once.

Ticket Management | OTOBO 9

Response templates and internal notes

Predefined email response templates save valuable time during recurring operations and high request volumes, ensuring competent feedback. This allows you to establish professional communication even with less experienced staff. Responses created during ticket processing can be saved as drafts for review by colleagues before sending. Notes can be used for internal communication – they are not visible to external users.

Ticket Management | OTOBO 10

Automatic acknowledgment

Automatic acknowledgment emails ensure transparency and satisfaction from the start for users. You can rest assured that their request is being processed. You can prepare appropriate auto-responses in OTOBO and assign them to the respective team inboxes. OTOBO takes care of the rest for you once the condition for sending, such as receiving a new ticket, is met.

Ticket Management | OTOBO 11

Define and customize user-defined ticket statuses

Create custom ticket statuses that align with your individual service management processes and workflows. The ticket status aids in progress tracking, informs all stakeholders, and can be used as a trigger for automatic follow-up activities.

Ticket Management | OTOBO 12

Collaborative ticket handling

Promote collaboration and leverage the roles of owner and responsible party to work on issues together or to monitor progress. OTOBO keeps you updated and automatically sends notifications, such as when the status changes, the ticket is closed, or there is a customer response.

Ticket Management | OTOBO 13

Audit-proof documentation

In OTOBO, tickets are stored in a tamper-proof manner. From OTOBO 11 on, you can modify and even delete internal ticket articles (i.e. notes) without compromising the fully-complete version history. Each editing step remains securely stored with the ticket.

Track ticket processing

Ticket status and notifications

Ticket status informs about which tickets are being processed, at which stage of processing they are, and who needs to respond next in the communication sequence. Through email or SMS, automated notifications ensure that involved roles are always up to date on status changes, new tickets, or follow-ups in communication.

Ticket Management | OTOBO 14
Ticket Management | OTOBO 15

Service Level Agreements (SLA) and Escalations

Set up Service Level Agreements (SLAs) with response and resolution times – either at the service level or within the respective work areas of your teams.

OTOBO automatically monitors the escalation times defined in the SLA to ensure that tickets are processed or resolved within the agreed timeframe. If this is exceeded, OTOBO automatically triggers escalations to ensure that the service team responds appropriately to requests and meets the Service Level Agreement (SLA).

➞ More about Service Level Management

Ticket Management | OTOBO 16

SCALABLE PLATFORM

Integrated Ticket and Case Management

IT Service Management (ITSM)

Ticket Management | OTOBO 17

Ticket management ensures that your users can systematically capture incidents and service requests related to the IT services of your organization and transparently track the progress of their resolution.

➞ Additional ITSM capabilities

Customer Service Management (CSM)

Ticket Management | OTOBO 18

Case management, in conjunction with automated processes, enables the efficient resolution of complex cases, such as in customer service and support.

➞ Additional CSM capabilities

Enterprise Service Management (ESM)

Ticket Management | OTOBO 19

Efficient ticket management forms the foundation for effective service management. It supports communication and the delivery of IT and non-IT services from internal and external service providers in a unified platform.

➞ Additional ESM capabilities

SERVICE EXCELLENCE

Ready to take the next step