Skipper works with the tools you already use: mailbox, accounting, RMM, team chat and AI. We set up whatever you connect together with you during onboarding.
| Area | Tools | What for |
|---|---|---|
| Email and sign-in (a mailbox is required) | Microsoft 365, Microsoft Entra ID, Google Workspace, Exchange Server, IMAP | Your mailboxes become the ticket inbox, replies to your customers go out through them, and, if you wish, your team signs in with their Microsoft account. |
| Accounting and billing | Lexware Office (cloud version), sevdesk, easybill, Billomat | At the end of the month, the recorded time becomes invoice drafts in your accounting program; without an integrated program, the billing overview and the service record prepare your invoice. |
| RMM and monitoring | Tactical RMM, NinjaOne, Datto RMM, N-able, Checkmk, Zabbix, Uptime Kuma | You see your customers’ devices and alerts in Skipper, turn alerts into a ticket with a click, and monitoring systems create tickets through incoming webhooks. |
| Team chat | Mattermost, Microsoft Teams, Slack, Matrix | Assignments, mentions, customer replies and due dates reach your team as direct messages, and new tickets per category reach a channel. |
| AI providers | Anthropic, OpenAI, Mistral, Ollama | Initial assessment of new requests and summaries via Anthropic, OpenAI, Mistral, Ollama or an OpenAI-compatible endpoint; you provide the access and pay the costs. |
| Interfaces | MCP, Webhooks | Your team’s AI assistants work through MCP with each person’s permissions, other systems create tickets via webhook, and Skipper reports new tickets to other services. |
Email and sign-in (a mailbox is required)
Accounting and billing
RMM and monitoring
Team chat
AI providers
Interfaces
Your mailboxes become the ticket inbox, replies to your customers go out through them, and, if you wish, your team signs in with their Microsoft account.
Your mailboxes, including shared mailboxes, become the ticket inbox, with one category per mailbox. Replies to your customers, confirmation emails and notices in portal mode go out through them, as do the email notifications to your team and the sign-in codes for the customer portal.
Your team signs in with their Microsoft account and goes through your tenant’s multi-factor authentication and access policies.
We set up these integrations with you during onboarding, at no extra charge.
Request an integrationAt the end of the month, the recorded time becomes invoice drafts in your accounting program; without an integrated program, the billing overview and the service record prepare your invoice.
At the end of the month, Skipper creates the invoice draft when you click, for one customer or for several at once. Working time according to your rules, materials and travel costs as separate line items. Status and invoice number come back to Skipper, hourly or at the push of a button.
We set up these integrations with you during onboarding, at no extra charge.
Your accounting program’s plan must include API access.
Request an integrationThe billing overview calculates the line items according to your rules. You transfer them to the program you write invoices with, attach the service record as a PDF (in German) and mark the time in Skipper as billed. This works with any program.
Without Lexware OfficeYou see your customers’ devices and alerts in Skipper, turn alerts into a ticket with a click, and monitoring systems create tickets through incoming webhooks.
Skipper shows your customers’ devices with their status and notes such as a pending reboot, failed checks or outstanding patches, plus a detail view. You filter active alerts by customer and severity, resolve or snooze them, and turn one or more alerts into a ticket with a click. You open remote access via a link in Tactical RMM.
We set up these integrations with you during onboarding, at no extra charge.
Request an integrationMonitoring systems that send messages via webhook create tickets through an incoming webhook. You preset category, customer and priority for each sender.
WebhooksAssignments, mentions, customer replies and due dates reach your team as direct messages, and new tickets per category reach a channel.
Personal notifications arrive as direct messages, for example on assignment, mention, customer reply, due date or a personal reminder; each person chooses email, Mattermost or both for each occasion. Messages about reminders and due dates can be postponed there with a button. Skipper reports new tickets per category to a channel via an outgoing webhook.
We set up these integrations with you during onboarding, at no extra charge.
Request an integrationInitial assessment of new requests and summaries via Anthropic, OpenAI, Mistral, Ollama or an OpenAI-compatible endpoint; you provide the access and pay the costs.
Initial assessment of new requests from the mailbox and portal, and summaries of long conversations with a click, via Anthropic, OpenAI, Mistral or your own model server (Ollama or OpenAI-compatible, such as vLLM or LM Studio). Separately, with its own provider: searching the wiki by meaning.
Your team’s AI assistants work through MCP with each person’s permissions, other systems create tickets via webhook, and Skipper reports new tickets to other services.
Your team’s AI assistants, described for Claude, work with tickets, time and the wiki and read customers as well as devices and alerts from Tactical RMM, each with the person’s permissions. A button with the name of your provider, such as “Claude”, opens a new chat on ticket and wiki pages, and the assistant loads the content via MCP.
Incoming, monitoring and other systems create tickets via HTTP POST. Each system gets its own endpoint with its own secret. Category, customer and priority can be preset. If the sender includes its own key, a retry does not create a second ticket. Outgoing, Skipper reports new tickets per category from the mailbox, from incoming webhooks and created manually to chat channels or other services that accept JSON; a test message is possible.
Get in touch. We set up further integrations with you during onboarding at no extra charge, as long as they do not have to be built for a single business only.
At the end of the month, Skipper creates an invoice draft per customer in your accounting program when you click, which you then finalise and send there: in Lexware Office (cloud version), sevdesk, easybill or Billomat. For this, you link each customer in Skipper once to their contact in the accounting program, and your plan there must include API access. We set this up with you during onboarding. Without an integrated program it works with any accounting: you transfer the line items from the billing overview to your existing program, attach the service record as a PDF (in German) and mark the time in Skipper as billed.
Yes. Skipper shows your customers’ devices and active alerts from Tactical RMM, NinjaOne, Datto RMM or N-able; for this, you assign each customer once to their client in the RMM. You turn alerts into a ticket with a click, snooze or resolve alerts, and open remote access via a link in your RMM. Monitoring systems such as Checkmk, Zabbix or Uptime Kuma create tickets via webhook. We set this up with you during onboarding.
Skipper does not come with its own AI. For the initial assessment of new requests and for ticket summaries, you connect a provider of your choice: Anthropic, OpenAI, Mistral or a model you run yourself, for example via Ollama. Ticket content then goes to that provider. For searching the wiki by meaning, you connect a provider separately, which then receives wiki content and search queries. If your team works with an AI assistant such as Claude, the assistant accesses tickets, customers, time entries and the wiki through an MCP server, with the permissions of the person using it. The data then goes to the assistant’s provider through that person’s account. Contract and costs are always directly with the provider, not through Skipper. Initial assessment, summaries and wiki search by meaning are switched off by default. The MCP server and the button that opens a ticket or wiki page in an AI chat are switched on by default; the button also appears as the “Document knowledge” prompt when a customer ticket is resolved. A click on it passes the subject or page title to the provider, and with “Document knowledge” also the customer name. All of this can be switched off. Skipper also works entirely without AI.
In a demo, we show you the integrations you want to use and how the setup works.