Solution 05 · Activity Cockpit

Every channel, every open item: one prioritised view

The Activity Cockpit brings together what sits in separate inboxes today: email, Slack, Teams, LinkedIn and calendar. Every incoming message becomes an open item with a priority, a deadline and a prepared reply draft.

Processing runs on your own infrastructure, not at a cloud provider. We run this solution ourselves every day, for months and across thousands of items.

01 · What the solution delivers

Whoever has five inboxes has none

The most expensive message is the one that waited in the wrong channel until the deadline had passed. The cockpit turns scattered inboxes into a single working list.

Consolidate

Email, Slack, Teams, LinkedIn messages and comments, appointments: all channels in one list, with a deep link back to the source.

Prioritise

Fixed, readable rules based on sender, deadline and keywords grade every item: from P1 (immediately) to P4 (when time allows).

Resolve

Tick off, reply or defer, right in the cockpit. The reply draft is already waiting and gets revised before it is sent.

Follow up

Reminders, escalations and overdue items are tracked automatically. A quote that goes out creates its own follow-up.

02 · The interface

The view that shows everything

Escalations on top, priorities as tiles, every item with channel, age and reply draft. The cockpit is rebuilt every 15 minutes and reachable from any device, including your phone.

Figure 1: The cockpit overview with channels, priorities and source freshness
Activity Cockpit · Overview
🚨 1 escalation: quote deadline Nordwind expires today Re-rendered 14:32 · next run 14:47
14
Open items
2
P1 now
5
P2 today
7
P3 / P4
3
Follow-ups
All channelsEmail 6 Slack 3Teams 2 LinkedIn 3⊞ Group: priority
Email P1 ✎ draft 2 h
Slack P2 ✎ draft 5 h
Teams P2 1 d
LinkedIn P3 ✎ draft 3 h
Rule P2 ✎ draft 3 d
Email 14:30 Slack 14:30 Teams 11:05 LinkedIn 14:00 Calendar 14:30 Freshness per source, honestly stamped
Every source carries the timestamp of its last sync: what lags behind is shown as lagging, instead of pretending to be current. Names and companies in the example are fictitious.
03 · Data processing

Six steps in a loop · five of them on your own infrastructure

The cockpit collects every hour, reconciles, prioritises and renders. The inboxes stay where they are: the cockpit reads, it does not copy mailboxes to a third party. Only drafting the reply suggestions uses a language model, optionally in your own data centre as well.

Figure 2: From channel input to the prioritised list, with processing locations
Six-stage loop from collecting to recording; only the fourth step uses a language model 010203 040506 Collect Reconcile Prioritise Prepare Render Record Email, Slack, Teams,LinkedIn and calendarevery hour What was alreadyanswered is detectedand closed Fixed rules fromsender, deadline andkeywords: P1 to P4 A language modeldrafts a reply foreach item Rebuilt every15 minutes, reachablefrom any device Every action loggedand kept in theknowledge base Runs on your own infrastructure, in your own house The only step using a language model, optionally in your own data centre The inboxes stay where they are: no additional cloud service mirroring all accounts, no provider reading your correspondence.
The reconciliation in step 2 also checks sent messages: anyone replying directly in the mail client or in Slack keeps working as before, and the item closes by itself on the next run.
04 · Replying

Reply without switching apps

One click on an item opens the reply panel: read the original, revise the draft, send. The same gesture for every channel. Sending uses the regular channel of the source: the reply arrives as a normal email, Slack or Teams message.

Figure 3: The reply panel with original, editable draft and actions
Activity Cockpit · Reply panel
Nordwind Solutions AG · query on the quote Email · M. Keller · today 12:14
“Thank you for the quote. Could you tell us by the end of the week whether user training is included in the package or billed separately?”
Reply draft · editable Dear Mr Keller, training is included in the package: two half-days on site, further sessions billed by effort. I have attached the breakdown. Would a short call on Thursday suit you?
📤 Send & tick off ↗ Open source ✓ Done 🔁 Follow up in 3 days ⏰ Tomorrow
The draft is a suggestion, not an automatism: only what you have revised and confirmed gets sent.
05 · Why this makes the difference

The problem is not the message, but the five places it could be sitting in

Nothing slips throughThe LinkedIn comment counts as much as the email. Every obligation to react sits in the same list.
Priorities, not arrival orderWork follows importance and deadline, not the arrival time of the loudest channel.
Replies in minutesThe draft is waiting. Revising and sending takes a fraction of writing from scratch.
Reliable follow-upQuotes and commitments are chased systematically, not from memory.
An honest pictureThe timestamp per source shows what is current and what lags. No pretended freshness.
Fuel for the knowledge baseEvery recorded action lands in the knowledge base and stays searchable, for your company's own assistant too.

Data handling

Inboxes
Stay where they are. The cockpit reads, it does not copy mailboxes
Open items
On a server in your own house, around the clock
Prioritisation
Fixed, readable rules on your own infrastructure
Audit trail
Every action recorded traceably, in your own knowledge base
Language model
Only for reply drafts, optionally as a model in your own data centre

No additional cloud service mirroring all your accounts. No provider reading the entire correspondence of your company.

Whoever has five inboxes has none. The most expensive message is the one that waited in the wrong channel, until the deadline had passed.
06 · Implementation

As a project in three steps

Clarify channels and rules

Which channels count, who are the important senders, which deadlines apply? Result: the rule set for prioritisation, readable and adjustable.

Connect and operate

The channels are connected, the in-house server set up, and the tone of the reply drafts adapted to your way of writing.

Pilot and fine-tuning

Start with one person or one team. The rules are sharpened on real weeks, then rolled out.

Extension stage

The next stage: your open items call you

The cockpit is the data basis for the digital assistant: it discusses the same open items on the phone, at the interval you choose, urgent ones immediately. Both paths remain open in parallel: click on the screen or word on the receiver.

Solution 06, Digital Assistant
Document

The summary as a PDF

Three pages for the discussion in expert committees and management: interface, process, data handling and implementation.

PDF · 3 pages

Activity Cockpit

The cockpit view, the six-stage processing loop, the reply panel, the reconciliation with follow-ups and the data handling, compact for the decision paper.

We store first name, last name, email and the requested document in order to deliver it to you and to contact you once about it. No passing on to third parties, no newsletter subscription. An informal email is enough to revoke, details in the privacy policy.

How many inboxes do you really keep track of?

In a first conversation we count your channels and clarify where items get stuck today. No obligation, at eye level.

Get in touch All solutions