Skip to content
Skipper

Customers, projects and contracts

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

Request a demo All features
Schematic illustration with sample data.

At a glance

Each customer comes with their contacts, the email domains for assigning new requests, their tickets, time and projects, and their documentation in the wiki. If you use Tactical RMM, their devices are added. From the customer record you reach everything important about a customer.

Projects organise tickets and time, such as ongoing support or a server migration, and have their own board. Project types group similar projects across all customers. You build contracts from your own content blocks, generate a PDF with your logo from them and send it to the customer for signature.

  • 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.
  • Contracts with status, version history and PDF. The customer returns the signed copy through a personal link.
  • Email domains per customer, through which new requests are assigned automatically.
  • Project types with default projects that every newly created customer receives.
  • Leads and their opportunities with an attached quote, until they become customers.
  • With Tactical RMM: the customer’s devices with status and a link to remote access.
Good to know
  • No import of customers or contacts, not even from CSV.
  • Leads and opportunities have no amounts and no revenue forecast. Skipper does not replace a sales CRM.
  • No electronic signature: signing happens outside Skipper, and you approve every returned copy by hand. Skipper does not remind you of terms or notice periods.
  • Projects have no budget and no hour quota.
  • Devices are read-only and come only from Tactical RMM; there is no inventory management of its own.
In detail

Everything about a customer

The customer record

The overview of a customer shows the address and primary contact, the number of open tickets and of time entries in the current month, and below that the active tickets. Tabs lead to tickets, time and contacts, along with projects, activities, devices and wiki, and for administrators also opportunities and contracts.

There is no import of customers, not even from CSV. Custom fields cannot be created.

Contacts and email domains

Contacts are created automatically when a request comes from a new address. Using the email domains you store for each customer, Skipper assigns new requests to the right customer. For each contact you decide what they see in the customer portal.

The domain must match exactly and belongs to exactly one customer, so addresses at free email providers are not suitable for the assignment.

Sign-in to the customer portal

Projects, project types and default projects

Projects group the tickets and time of a customer, such as ongoing support or a server migration, with board, list and calendar. If you wish, project types such as managed IT support show the projects of all customers on one page. If you wish, Skipper also creates default projects for every newly created customer, and incoming tickets without a project land in the customer’s default project.

Projects have no budget and no hour quota. Default projects are only created for customers added after the setup.

Leads and opportunities

You keep leads in the same system as your customers. For each one you record opportunities with status and an attached quote, and when a lead becomes a customer, a click is enough, without any data having to be transferred.

Opportunities have no amounts and no forecast, and Skipper does not replace a sales CRM. Only administrators see leads and opportunities.

Contracts from your content blocks

You build contract templates from content blocks with placeholders, and you mark passages that must be filled in as required. Each contract has a status and a version history, and Skipper generates the PDF with your logo, with dates and other placeholder values in German format. You send the finished contract from Skipper to a contact at the customer: they receive the PDF and a personal link through which they return the signed copy as a PDF, without an account. Once you approve it, it is stored on the contract as the original.

There is no electronic signature: signing happens outside Skipper, for example on paper and then scanned, and you approve every returned copy by hand. Sending runs via Microsoft 365, and the link is valid for 30 days and leads to a page in German. Skipper does not remind you of deadlines or supply contract texts, and the contract value is not carried over into billing.

Devices from Tactical RMM

With your Tactical RMM instance, Skipper shows the devices of a customer with their status, a detail window with information such as manufacturer, model and serial number, and a link that opens remote access in Tactical RMM.

The devices are read-only and come only from Tactical RMM; there is no inventory management of its own.

Connect Tactical RMM
Other areas

Related areas

All features

  • Wiki and customer documentation

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

  • Team planning

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

  • 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.

As of Skipper 1.22.1, October 2026. This page describes 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