Central Ticket View
Status, priority, queue, owner, responsible agent, customer, service, SLA, and processing history remain visible directly on the ticket.
Features
Qisutu brings ticket handling, email communication, customer management, automation, and service organization into one working environment.
Day-to-Day Ticket Work
Each ticket brings communication, processing status, organizational context, and all related information together in one place.
Status, priority, queue, owner, responsible agent, customer, service, SLA, and processing history remain visible directly on the ticket.
Incoming messages create new tickets or are assigned to existing requests. Outgoing mail supports SMTP as well as Microsoft 365 and Google.
External replies, internal notes, and files form a complete, chronologically organized communication history.
Find tickets by text, number, queue, status, priority, customer, assignee, service, SLA, date range, and dynamic fields.
Process multiple requests together and link, split, or merge related tickets when service work requires it.
Custom fields and configurable ticket forms capture exactly the information required by each service process.
Organization and Collaboration
Qisutu supports internal teams as well as customers, organizations, and distinct service areas.
Granular permissions control which teams can view, process, move, or administer tickets.
Agent accounts, customers, customer users, and organizations are managed separately and connected where required.
Service catalogs, calendars, and SLA targets define binding response, update, and resolution times.
Defined work steps and prepared replies support quality and completeness in recurring tasks.
Language, time zone, notifications, absence periods, and replacements can be configured individually.
Qisutu supports German-, English-, French-, and Italian-speaking agents and customer users.
Automated Service Processes
Event-driven and scheduled rules respond to defined conditions and perform specific actions. Workflows become faster while decisions and changes remain transparent and controllable.
Knowledge, Data, and Extensions
Beyond the ticketing core, Qisutu connects knowledge, configuration data, reporting, and interfaces with operational work.
Categories, articles, permissions, and ticket relationships make existing knowledge available to agents and customers.
Configuration items, types, states, relationships, and ticket links support technical service processes.
CSV and configurable import functions simplify the transfer and maintenance of larger data sets.
Work time, activity types, and configurable reports provide a reliable basis for management and billing.
Secured API access supports integrations for tickets, articles, attachments, customers, and central master data.
Additional capabilities can be installed as separate packages and integrated into the interface and runtime in a controlled way.
Authentication and Security
Agents and customer users can authenticate against separately configured LDAP directories and be mapped to Qisutu accounts.
An additional verification step and recovery codes protect accounts beyond the password.
Incoming and outgoing email can be decrypted, encrypted, signed, and checked for valid signatures.
Versatile Use Cases
Qisutu adapts to different organizational models and creates a reliable working foundation for teams that need to coordinate and process requests in a structured way.
Capture, prioritize, and process incidents, access requests, workplace issues, and standardized IT services transparently.
Receive requests from email and the web in one place, route them effectively, and respond with consistent communication.
Model individual processes for technical services, administration, institutions, and specialized support organizations.
Next Step