Skip to content
Skipper
Features

Exactly what your team needs

Not a large system that does a bit of everything. Skipper brings tickets, planning, time tracking and billing for small IT teams into one system, instead of a ticket system and a separate time tracker. No more and no less.

Request a demo
Overview

The eight areas

  • Tickets and mailbox

    Requests from the mailbox, the customer portal and the phone arrive as tickets in one queue, with the time you bill attached right to the ticket.

    • Several mailboxes, including shared mailboxes in Microsoft 365, each assigned to its own category.
    • New emails become tickets, and the sender receives a confirmation email with the ticket number.
    • If a customer replies to a ticket that is waiting, in the backlog or resolved, the ticket reopens.

  • Team planning

    List, board and monthly calendar show what is coming up, and recurring tickets create repeat work in good time.

    • Views for My Tickets, Co-assigned, Open Tickets and Overdue, each with a counter.
    • Board with the columns Backlog, Open, In Progress, Waiting and Resolved.
    • Monthly calendar in which you move tickets to another day by dragging.

  • Customer portal

    Your customers submit requests via a form, see the status of their tickets and reply directly.

    • Request form with attachments, optionally with a fixed link per category.
    • Status page per ticket with history, attachments and reply box, without internal notes.
    • Sign-in without a password, using a code the customer receives by email.

  • Time tracking

    You book time with a timer, in a form or directly on the ticket, at the hourly rate that applies to the customer.

    • Timer that keeps running on the server, even after the browser is closed.
    • Entries with a duration or with start, end and break.
    • Book time directly on the ticket, with all its time entries and their total in view.

  • Billing and service records

    At the end of the month, Skipper shows what to bill for each customer, with a service record as PDF for any accounting and an invoice draft in Lexware Office.

    • Billing overview per month and customer with a preview of the line items.
    • Invoice draft in Lexware Office for one customer, or in one go for several customers in a month.
    • Service record as PDF with your logo, per customer or for all customers at once.

  • Customers, projects and contracts

    The customer record brings together contacts, tickets, time, projects, contracts and documentation in one place.

    • Customer record with contacts, tickets, time, projects and customer wiki.
    • Projects with status and booked time, their tickets as board, list or calendar.
    • Contract templates from your own content blocks, with placeholders and required passages.

  • Wiki and customer documentation

    Runbooks and customer documentation live in the same system as your tickets.

    • A documentation area per customer, created directly from the customer record.
    • Share individual pages with customers via a link, with subpages if you wish, revocable at any time.
    • German full-text search across all pages, and optionally a search by meaning through an integrated provider.

  • AI integration and MCP server

    Skipper connects to the AI provider of your choice, and AI assistants such as Claude work with tickets, customers, time and wiki via the MCP server.

    • Free choice of AI provider: Anthropic, OpenAI, Mistral, Ollama or an OpenAI-compatible endpoint.
    • MCP server for AI assistants: tickets, customers, time and wiki with the permissions of the person using it.
    • Initial assessment of new requests from mailbox and portal: short description, internal note and, if you wish, a priority.
Access

Access and permissions

You decide who sees what in your instance.

Schematic illustration with sample data.

  • Two roles

    The Administrator role manages settings, billing and contracts. The Agent role works with tickets, customers and the wiki; in time tracking, agents only see their own entries.

  • Access per ticket category

    Each person sees the tickets in the categories you give them access to, plus the tickets assigned to them. This lets you separate support and project work, for example.

  • Sign-in without a password

    Your team signs in with a link sent by email or, if set up, with their Microsoft account. Your customers sign in to the portal with a code sent by email.

  • Ending sessions

    Administrators can sign a person out on all devices. When an account is deleted, access ends immediately; tickets and time entries are kept.

  • Audit log

    Changes to customers, tickets, time entries and many settings are recorded in the log with the person and time. Administrators can view it.

Integrations

What Skipper works with

Skipper works with your mailbox, your accounting, your RMM, your team chat and the AI provider you choose.

All integrations

As of Skipper 1.22.1, October 2026. The area pages describe this version.

See Skipper in a demo

We show you the areas that matter to your business, using your own workflows as the example.

Request a demo