Personas work in Claude Code, Cursor and Codex, too. See how
  1. Home
  2. Industries
  3. IT service providers

Your service standards, in every ticket.

Keep runbooks, the way you write to customers and what each customer needs as playbooks. Service desk, technicians and sales work from the same standards, in the AI tool each of them uses.

Probably AI-generatedRunbook · loaded in Cursor
Start 14-day free trialSee pricing
  • EU-hosted
  • No training on your content
  • Your own keys

One library for every customer.

What changes when your service standards live in sqemes instead of in single heads and chats.

Your library

Runbooks, customer rules, your way of writing.

Write down how you work as skills: runbooks, what each customer expects, how you report an incident. Add prompts for the summaries and replies you write every day. Files such as network plans or checklists are stored once and attached where they are needed.

About skills
Probably AI-generated

Service library

Incident reportSkillReady

Runbook: firewall updateSkillReady

Ticket summaryPromptReady

Every tool

Service desk or terminal, the same standard.

The browser extension brings your playbooks into ChatGPT, Claude and Gemini. Over MCP, Claude Code, Cursor, Codex and other clients find the right runbook by themselves while a technician works.

How MCP works
Probably AI-generated

Cursor · sqemes MCP

Runbook: firewall updateSkillLoaded

Customer: NorthwindSkillLoaded

Control

Customer knowledge for the team that serves them.

Restrict what you know about a customer to the people who work for them, decide separately who may edit it, and keep a version of every saved change.

How governance works
Probably AI-generated

Who can see "Customer: Northwind"

Everyone in the workspace

RestrictedTeam Northwind

A persona for every role in your service.

Pick a task and see what the Service Desk Lead loads.

Try it: pick a task
  • Works in sqemes Chat and in AI tools connected over MCP.
Probably AI-generated

Service Desk Lead

Customer: NorthwindSkillLoaded

Incident reportSkillLoaded

Ticket summaryPromptLoaded

What an IT service provider does with it.

Recurring work between ticket and offer, with your standards already in it. Examples of what you can keep in sqemes.

Ticket summaries

A prompt that turns a long ticket into a summary for the customer, in your words.

Incident reports

What happened, what you did, what comes next, in the structure your customers know.

Runbooks

How you set up, update and check a system, as skills technicians load while they work.

Offers

Offer texts and service descriptions as Word or PDF in your document style.

Scripts and code

Your conventions in Claude Code, Cursor or Codex, through the MCP server.

New technicians

New colleagues find how you work for each customer in the library instead of asking around.

Set it up for your customers too.

Questions, answered.

What IT service providers ask.

Still unsure?

Write to us. A real person answers.

Contact us
01Which AI tools can our technicians use with sqemes?
ChatGPT, Claude and Gemini through the browser extension, sqemes Chat with any provider you connect, and every tool that supports MCP, such as Claude Code, Cursor and Codex.
02Can sqemes read our tickets and documentation?
In sqemes Chat, yes, with connectors such as Atlassian (Jira, Confluence), Microsoft 365 or GitHub, or any MCP server you add by its address. Each person connects their own account or uses a shared one.
03Can we keep knowledge about one customer to one team?
Yes. Restrict any playbook to named people or groups, and decide separately who may edit it.
04Can we set up sqemes for our customers?
Yes. As a partner you can build and look after sqemes workspaces for your customers. The partner page explains how.
05Can we run sqemes on our own servers?
Yes. The self-host version runs on your own servers with your own AI keys and is free for internal use under a fair-code license.