HomeIndustriesIT service providers

Industry · IT service providers

Less ticket chaos.
More engineering.

AI assistants for IT service providers: they pre-qualify tickets, answer customer enquiries as drafts, schedule appointments, prepare quotes and make your knowledge findable for your engineers. Actions on the customer’s system are approved by your engineers. Everything in one platform, built individually for your business.

  • Data processing agreement under Art. 28 GDPR
  • EU hosting
  • No use of your data for training
  • Fixed price

Inbox today

  • Sample GmbHNetwork printer offline since yesterdayTicket pre-qualified
  • Ticket 4712 · Example ConstructionEmail sending disrupted for all usersPossible outage flagged
  • Example Trading GmbHEnquiry: six new laptopsQuote drafted
  • Call 8:12 amAppointment request: on-site call-out2 appointments proposed
  • Ms DoeOpened a suspicious attachment, what now?Handed to engineering

Draft

To: Sample GmbH · Subject: Your ticket: network printer offline

Draft in progress …EditApprove
0 of 5 cases prepared0 sent without approval
  • DPAData processing under Art. 28 GDPR, roles, logs and deletion concept
  • EUEU hosting, protected operation of the language models
  • Fixed priceOne-off setup, monthly care, no preliminary analysis
  • 3–10Weeks from booking to go-live

Where it gets stuck

Four things that cost engineer time.

None of them needs an engineer. All four still land with your team.

01

Tickets without details

“It doesn’t work” is not a ticket. Which user, which device, since when, what was tried? Until the queries are answered, engineer time has already been used without anything being fixed.

02

Always the same questions

Resetting a password, setting up a printer, access for new employees: the answers are somewhere in documentation and old tickets, but nobody has them to hand right now.

03

Appointments and call-outs

On-site call-out, maintenance window, callback: every appointment needs coordination between customer, calendar and engineering. In total this costs more time than some call-outs themselves.

04

Quotes for small things

Two laptops, a switch, a licence extension: the quote is quickly explained, but someone has to gather items, terms and service contract and type them up.

How the service assistant works

Intake. Preparation. Your approval.

Three steps, always in this order. The third stays with you.

1

Intake

Email, phone, website chat and customer portal come together in one place.

  • Customer, contract and response time identified
  • Request, category and urgency classified
  • Disruptions and suspected security incidents straight to engineering
2

Preparation

The assistant gathers the facts from your systems and drafts what needs to be done.

  • Customer documentation, ticket history and knowledge base searched
  • Queries and draft reply in the tone of your business, source for every statement
  • Ticket fully created, appointment proposed
3

Your approval

Service and engineering see the draft and the sources, edit and approve. Only then does anything go out.

  • Approval in seconds instead of processing in minutes
  • Every change feeds into the knowledge base
  • Log: who approved what, and when

Use in the IT service

Six tasks the assistant takes on.

Bookable individually, combinable. For each one we state what stays with you.

AI email assistant

Pre-qualifying tickets

Intake
“Since this morning nobody here can get into their mailbox.”
Preparation
Customer, contract and response time identified, ticket created with category and priority, affected systems assigned, queries drafted.
Result
A complete ticket with engineering before anyone has to ask.
Stays with you
The classification as a disruption and every action on the customer system. Engineering approves that, never the assistant.

AI phone assistant

Taking disruptions by phone

Intake
Call during the lunch break, the helpdesk is busy and the customer is waiting.
Preparation
The assistant answers, identifies the customer, captures the disruption and callback number, creates the ticket and passes disruptions to on-call.
Result
No missed call, no scraps of notes, one complete ticket.
Stays with you
Statements about time to fix and the deployment of on-call. A person decides that.

AI back-office assistant

Knowledge base for engineering

Intake
“How did we solve this error at the last customer?”
Preparation
Answer from your work instructions, the customer documentation and earlier tickets, with a source for every statement.
Result
Knowledge is findable, even when the colleague with the experience is on holiday.
Stays with you
Whether a solution is applied. Changes to customer systems are carried out and owned by engineering.

Workflow automation

Scheduling on-site appointments

Intake
A customer needs a call-out, for example to replace a switch.
Preparation
Free time slots from the engineers' calendar, appointment proposal to the customer, material and access noted, reminder the day before.
Result
Appointments without back-and-forth, the call-out details are complete in advance.
Stays with you
The commitment to the appointment and the deployment planning. The appointment proposal goes to the customer only after approval.

AI administration assistant

Preparing quotes

Intake
Customer enquiry by email: six laptops with setup and data migration.
Preparation
Items from your service catalogue, terms from the service contract, quote draft in your template, follow-up reminder to chase.
Result
Quote draft with a source for every item, consistent in structure.
Stays with you
Prices, discounts and the technical suitability of the solution. No quote goes out without your approval.

AI website chatbot

Customer questions around the clock

Intake
“How do I report a disruption, and how quickly do you respond?”
Preparation
Answer from your service catalogue, recording of the disruption as a ticket with callback number, pointer to the emergency route.
Result
Customers get an immediate answer, and engineering gets a cleanly created ticket.
Stays with you
Commitments on response and resolution times. The chat only repeats what the service contract says.

Also possible: invoicing and payment reconciliation for maintenance and service contracts · time tracking and timesheets · summaries of long ticket histories · reminders about contract renewals and licence expiry

One case, step by step

8:41 am. One disruption, one minute.

This is what a case looks like when the email assistant and knowledge base are set up.

Fictitious example with invented data

Incoming · 8:41 am

Example Construction GmbHSubject: Outlook does not start

Good morning,

since yesterday’s update Outlook no longer starts for two colleagues. Can you send someone today?

Kind regards
Petra Example

Preparation · 8:41 am

Assistant · case notesSources: customer records, service contract, knowledge base, calendar
  • Customer identified: Example Construction GmbHService contract with remote maintenance, response time according to the contract
  • Ticket created: Outlook does not start, 2 usersTwo similar cases after updates in the knowledge base
  • On-site appointment possible: today 14:00 or tomorrow 09:00from the engineers' calendar
  • Draft reply created, queries insertedFollow-up reminder “Feedback from the customer?” for today 16:00

For approval · 8:42 am

Draft to Example Construction GmbHSubject: Your ticket: Outlook does not start

Good morning Ms Example,

thank you for reporting this; we have logged the ticket. After updates this error occurs occasionally. Please tell us the two affected computers and the version of Outlook.

For an on-site visit we can offer you today at 14:00 or tomorrow at 09:00. Our engineering team decides whether it is necessary.

Kind regards
Example IT Services

ApproveEditApproval by: service

All names, tickets and times are invented. Underlined details in the draft are linked to their source; when approving, the service team can see where every detail comes from.

One platform instead of ten

Everything in one dashboard.

For IT service providers we develop a bespoke all-in-one platform: tickets & pre-qualification, emails, phone & fault reporting and everything else in one dashboard, on your computer and as a web app on your phone. No more switching between ticket system, Outlook, calendar, documentation and filing.

  • One platform instead of several programs: everything in one place, built around your processes
  • The seven AI modules are part of the platform and pass cases on to each other
  • What has to stay, we connect through interfaces instead of replacing it

Connected, not replaced: remote maintenance and monitoring

Your platformTuesday · 8:41 am
  • Tickets & pre-qualification
  • Emails
  • Phone & fault reporting
  • Quotes
  • Appointments & call-outs
  • Invoices
  • Customer correspondence
  • Knowledge base & filing
As a web app on your phone: the same dashboard, the same approvals, on the move.

The products named are trademarks of their respective owners. The platform is developed individually for each business; scope and order of the replacement are defined in the quote.

Confidentiality and data protection

Confidentiality is not a setting. It is a contract.

What we assure to IT service providers, in writing, before the first case.

Confidentiality

Tickets often contain network diagrams, access credentials and customer data. We and our staff are bound in writing to confidentiality, as Art. 28 GDPR requires.

Protected operation

Our cloud server is located in a data centre in Germany, and the language models run in protected operation in the EU. Your data is not used for training.

Data processing

Data processing agreement under Art. 28 GDPR with annexes on data types, sub-processors and technical measures. If you are yourself a processor for your customers, we align the chain with you.

Roles and logs

Access by roles in service and engineering. Every draft, every approval and every change is traceable: who, when, what.

Labelling

Where the AI Act requires it, the assistant is recognisable as such to customers. Approved replies go out as a reply from your business.

Approval by engineering

The assistant changes no customer systems and executes no commands. Actions, access and statements on resolution are approved by your engineers.

Who it is for

Particularly worthwhile if…

  • many tickets and enquiries arrive by email and phone and too many without the necessary details
  • knowledge is scattered across documentation, old tickets and heads, and new colleagues search for a long time
  • at least one person reviews and approves drafts, usually service or engineering
Small systems house? With the Starter package you begin with one module, usually the email assistant. You can expand at any time.

Working together

Five steps. Clear effort.

From booking to go-live usually 3 to 10 weeks, depending on modules and interfaces.

  1. 1

    Free introductory call

    Your processes: tickets, customer enquiries, knowledge, appointments. We tell you what is worthwhile and what is not.

    Your effort: 30–45 minutes

  2. 2

    Package selection

    Starter, Business or Professional, matched to the number of modules and interfaces.

    Your effort: one decision

  3. 3

    Binding booking

    Fixed price, service description, confidentiality undertaking and data processing agreement.

    Your effort: signature

  4. 4

    Setup, testing & go-live

    First with anonymised cases, then with real ones under your approval. Team training.

    Your effort: access and test phase

  5. 5

    Ongoing care

    Operation, maintenance, support and further development in the Care package, with reporting.

    Your effort: feedback when needed

Questions from IT service providers

What IT service providers ask us.

Does the platform replace your ticket system?

Yes, that is the goal. We develop an all-in-one platform for your business in which email, phone, WhatsApp, quotes, order confirmations, invoices, customer correspondence and back office come together in one dashboard, on your computer and as a web app on your phone. You no longer switch between ticket system, Outlook, calendar, documentation and filing. What has to stay, we connect through interfaces: remote maintenance and monitoring.

We plan the changeover step by step: first the platform runs alongside your existing tools, then in their place. Nothing is switched off until it runs in the platform and your team has been briefed.

Does the assistant access customer systems?

No. The assistant works with tickets, documentation, calendar and mailboxes. It changes no customer systems and executes no commands. Actions on the customer system are approved and carried out by your engineers themselves. How access credentials in tickets are handled, we define in the introductory call.

Does the assistant decide on priority?

It makes proposals. According to your criteria, such as affected users and contract situation, it classifies tickets and flags possible disruptions. Classification and priority are confirmed by your engineers. Suspicion of a security incident goes straight to a person.

We are a processor for our customers. What applies then?

Then we are a sub-processor. The data processing agreement is structured so that it fits into this chain. Whether your clients have to consent and how you inform them depends on your contracts with them. We compile the information for this for you.

How is confidentiality regulated?

Before the first case we are bound in writing to confidentiality. In addition there are the data processing agreement under Art. 28 GDPR and protected operation: our cloud server is located in a data centre in Germany, and the language models run in the EU, and your data is not used for training.

How does the assistant know our knowledge?

From your work instructions, the customer documentation and earlier tickets. Answers come with a source. If the knowledge is not enough, the assistant flags the gap and hands over to engineering. Corrections feed back into the knowledge base.

What happens if the assistant prepares something wrongly?

Then you see it before it goes out: nothing leaves your business without approval, and every detail in the draft is linked to its source. In the test phase we work with anonymised cases first.

How long does setup take?

One module in 2 to 3 weeks, up to three modules in 4 to 6 weeks, extensive processes with several interfaces individually. The test phase is part of this time. You provide access and approve during the test phase; that is all the effort you have.

What does it cost?

Setup at a fixed price, depending on the package; ongoing care monthly. After the introductory call you receive a binding quote with a service description; there is no paid preliminary analysis. All prices are net plus VAT. You will find the packages on the home page.

What happens if the assistant itself is disrupted?

You report by email, ticket or – in the Care Professional package – by phone. Response within 48, 24 or 4 hours depending on the Care package. Monitoring, daily backups, maintenance and updates are included in every Care package.

Next step

Introductory call for your IT service.

30 to 45 minutes, online, free of charge. We talk about tickets, customer enquiries, knowledge and appointments in your business and tell you honestly what is worthwhile and what is not.

Pick a slot in the calendar

Prefer email or phone? info@ki-partnersysteme.de · +49 211 92 32 63 126

On request we will send you the confidentiality undertaking and data processing agreement in advance for review.

WhatsApp