Your own AI colleague — operated by jemix

Your company thinks along.
Even when you are not in the room.

Your team asks in Teams and gets answers from your own company knowledge — without the long search. The agent runs isolated for your company and is operated entirely by jemix.

Personally configured. Managed on an ongoing basis.

C-MateIllustrative conversation in Microsoft Teams

Synthetic example · not a live product

What should I focus on before Monday’s leadership meeting?

A starting point for your agenda

1. Review the pilot’s open questions. 2. Agree an owner for the rollout decision. 3. Confirm what the team needs next.

Would you like a draft agenda to review?

Example material: Northstar leadership notes · fictional
Fünf unterschiedlich hohe Steinpfeiler stehen in einer Reihe auf einer weiten dunklen Ebene; eine Messinglinie führt an ihnen entlang zum Horizont.
01 / The platform

Your knowledge stays yours — verifiable, not promised.

Five properties decide whether you can entrust company knowledge to an agent. Each one is written into the technical contract your agent is built and operated under — you can read them.

Contract §2 · Tenant isolation

Your agent stands alone

Its own stack, its own gateway, its own secrets area — separated per customer. Exactly one Microsoft 365 Tenant per instance. Access across customer boundaries is neither intended nor technically possible.

Contract §7.1 · 0 */6 * * *

Knowledge stays current

Your SharePoint content is synced every six hours — only changes, not everything anew. With no change, nothing happens: no idle runs, no unnecessary load.

Contract §4.2 · Pre-import gate

Checked before it counts

A check runs before every import. If it fails — empty bundle, unexpected shrinkage, incompatible version — nothing is imported and nothing is deleted. The existing state stays in operation.

Vier parallele Messinglinien verlaufen in gleichen Abständen über eine dunkle Steinebene zum fernen Horizont.
02 / The process

New knowledge is there before anyone asks for it.

Changes from your SharePoint become available to the agent automatically — every six hours, in four secured steps. Nobody has to remember to update anything.

01

Collect

The sync picks up the changes from your SharePoint. The source is only read — nothing is written back and nothing is modified.

02

Check

The verification gate inspects the result before it is imported: is there any content at all? Has an unexpected amount disappeared? Does the format fit? Only when all three questions are answered cleanly does it continue.

03

Import

Only now does the knowledge move into your agent's knowledge store and get prepared for it. A functional test follows.

04

Switch over

If the test passes, the new state goes live. If it does not, the old state stays in operation and we are notified. Your staff notice nothing.

Eine geschlossene dunkle Steintür mit einem waagerecht vorgelegten Messingriegel.
03 / Security

Better no answer than a wrong one.

The greatest risk with automatically maintained knowledge is not the visible error but the silent one: a sync appears to complete, but half the knowledge has disappeared. That is why a gate checks before every import — and stops as soon as something is wrong.

The verification gate

That is why the verification gate decides before the import, not after. It does not touch the knowledge store, it only checks — and stops as soon as something is wrong. Stopping is always the safe direction: an overly cautious stop costs one run, an overly bold import costs your data.

In doubt: stop

Check before import

What is checked

CompletenessVersionScope

On stop: no import, no deletion, no switchover — the existing state stays in operation unchanged and we receive a notification.

Eine lange niedrige Steinmauer mit Messingkante teilt eine weite dunkle Ebene in zwei gleich große Hälften.
04 / Operations

You do not need to assign anyone to it.

Setup, monitoring, updates and maintenance sit with jemix. What stays with you is only what is your decision: which knowledge sources are connected and who may use the agent.

Setup

We provide the instance, connect your SharePoint and set up access in Teams.

Ongoing operation

Monitoring, updates and maintenance are handled by us. You do not need to assign anyone to it.

Your side

You decide which knowledge sources are connected and who may use the agent. Nothing more is required.

05 / Your questions

What decision-makers ask first.

Can other customers see our data?

No. Every customer gets their own separate instance with its own access area and exactly one connected Microsoft 365 Tenant. Access across customer boundaries is not intended.

Does the agent change anything in our SharePoint?

No. The sync runs in one direction only: from SharePoint into the agent's knowledge store. Nothing is written back.

What happens if a sync goes wrong?

Then it is not imported. The verification gate runs before the import and stops as soon as something is wrong — the existing state stays in operation and we are notified.

How current is the knowledge?

The sync runs every six hours and transfers only changes. If there were none, everything stays untouched.

Do we need our own IT staff for this?

No. Operation, updates and monitoring sit entirely with jemix. You decide on content and access, not on technology.

How are costs handled?

The agent works with a deliberately economical standard model. When a task justifies a more expensive one, it asks first instead of switching silently.

What does setup involve?

We discuss your first use case, prepare agreed knowledge sources and configuration, and introduce C-Mate in Teams. The exact sequence and ongoing tuning are agreed together.

08 / Let’s meet

Your next colleague starts with a conversation.

Tell us a little about your company and what you’d like to explore.

This is a demo enquiry, not a confirmed meeting or a service agreement.

All fields are required unless marked optional.

Up to 1,000 characters. Please do not include confidential company information or personal details about other people.

Write to [email protected] — we will get back to you.
Request a demo by email