Skip to content
HelpDesk· an app for Microsoft 365

HelpDesk: No request slips through.
And the app watches the deadlines you promised.

A customer writes to the support address or in the portal, and a ticket with a tracked response time appears. The team handles everything from one queue — and the hours worked are ready as an invoice input.

Who it's for Companies that support their own customers IT services, service teams, agencies
What it costs from €89 per month customers in the portal don't count toward the total
How fast Deployed typically within half a day no Power Automate, no extra servers

Runs in your Microsoft 365 — customers see only their own tickets.

Book a demo
How it works

Three steps from an email to an invoice.

Customers write just as before. What changes is what happens to their request next.

  1. The customer writes

    By email to the support address or in the portal. The app creates a numbered ticket and sends the customer a confirmation.

    No Power Automate, no extra servers
  2. The team works from one queue

    Every ticket shows a response-time countdown per contract. You reply from the app and it reaches the customer by email.

    On a breach, an escalation goes to the lead
  3. Hours go to the invoice

    Time worked stays with the ticket, allowance usage is calculated as you go, and work beyond the allowance gets billed.

    With Worklog the hours are logged automatically
Inside the app

See it in practice

A queue overview with response-time tracking, taking a ticket, replying to the customer right from the detail and resolving the ticket.

What changes

Today vs. with HelpDesk

This is what companies that support their customers — IT services, service teams, agencies — tell us.

Today “Requests land in five different mailboxes.”Nobody knows what's open or who's handling it. When a colleague is on holiday, their tickets sit unnoticed.
With the app One queue for everythingEvery email becomes a numbered ticket, and further messages are paired into a single thread.
Today “We promised a response within four hours — did we make it?”Response times are tracked from memory and from emails. Digging it up takes half a day and still without certainty.
With the app An SLA countdown on every ticketThe queue highlights what's at risk, and the “Waiting for customer” status pauses the SLA clock.
Today “What did we actually work, and can it be billed?”Hours spent on support are logged nowhere, and an overrun allowance never gets billed.
With the app Hours from tickets as an invoice inputAllowance usage is calculated as you go, and the customer sees the status of their requests in the portal.
Customer experience
We finally know what's open and who's handling it. And an overrun allowance finally gets billed — before, it quietly lapsed.
IT services · 6 support staff · 40 customers under contract

Getting started took half a day. We connected the support mailbox in the morning; by the afternoon the team was resolving the first tickets from the queue.

5 mailboxes → 1 queueof customer requests
100 %of tickets with a tracked response time
0extra automations and servers
The fastest route

30 minutes on screen, no company presentation

  • 5 minYour current practice — how you take requests and watch deadlines today
  • 10 minA ticket from an email, the SLA queue and a reply to the customer through the team's eyes
  • 10 minThe customer portal, closing a ticket and logging hours into Worklog
  • 5 minWhat a rollout would look like for you + an indicative price
Pick a demo slot → Free and without obligation · online in Teams
8 areas — click one for details

A ticket from an email without Power Automate

The app picks up the shared support mailbox via Microsoft Graph (delegated, under a team member's account with FullAccess and SendAs), creates tickets, pairs replies into threads by conversation and by the [HD-xxxx] tag in the subject, and sends confirmations and replies. A lock prevents collisions between agents. Unknown senders wait in Unassigned mail.

A queue with sorting and a kanban board

A sortable table with status filters and SLA countdowns, or a kanban with drag-and-drop between statuses (New → In progress → Waiting for customer → Resolved → Closed). Dragging a card triggers the same steps as the buttons in the detail. The “Waiting for customer” status pauses the SLA.

Ticket detail and conversation

The conversation thread separates public replies from internal notes the customer doesn't see. Email attachments stay with the ticket, the record holds the classification (priority, category, work type, billability, effort), watchers on copy, duplicate merging and an Activity tab with the full history.

SLA plans and escalation

A response time and a resolution time for each priority, in business hours Mon–Fri 8–17 or around the clock. A plan is assigned to a company. On a breach a summary escalation goes to a chosen address — once per ticket. An approaching allowance limit is watched by a separate alert.

A customer portal

External users (guest accounts) get an overview, their tickets, creation and replies. The “Whole company” role adds colleagues' tickets, “Only my tickets” keeps the view to their own. Portal submissions go through a secured inbox where SharePoint guarantees the author's identity.

A knowledge base and macros

Published guides are read by customers in the portal (and rated for usefulness); internal articles serve the team. Macros run several ticket actions at once, inbound-mail rules sort new tickets by sender, and automations close resolved tickets or send a reminder.

CRM, Worklog and reports

Companies, service contracts and contacts come from EP365 CRM, and allowance usage is calculated from closed tickets. Closing a billable ticket logs the hours into EP365 Worklog. Monthly reports (new, resolved, SLA compliance, billable hours by company) have charts and a CSV export as an invoice input.

In the browser and in Microsoft Teams

HelpDesk runs as a web part on SharePoint and as a personal app in Microsoft Teams — the team handles tickets right inside Teams, on desktop and mobile (on first launch it picks the site with its support). An admin can also assign specific companies to individual team members, so each person sees only the tickets of the customers they look after.
Area
EP365 HelpDesk
Shared mailbox
Cloud helpdesk
In-house SharePoint build
Data in your Microsoft 365
yes, entirely
in your mailbox
third-party cloud
usually yes
A ticket from an email with a number
automatically
manual triage
yes
needs coding
SLA tracking and escalation
by the company's plan
from memory
yes
partially
Ticket isolation between customers
by SharePoint permissions
the whole mailbox sees it
depends on setup
depends on the build
A customer portal
with company / own roles
no
yes
rarely
Logging hours and billing
logs into Worklog
no
basic only
no
No third-party server or automations
yes
yes
runs at the vendor
depends on the build
Deployment
in half a day
immediately
sign-up and setup
weeks of development
Work in Microsoft Teams
as a personal app
no
sometimes an integration
rarely

Data stays with you

Tickets, conversations, companies and contacts are stored exclusively in your Microsoft 365 environment, under your identities and permissions. No export to a third-party cloud, no data leaving the company.

A customer can't see others' tickets

Each ticket and message gets permissions only for the requester, their company and the support team. Other companies' tickets are technically out of reach, even with a direct link — enforced by SharePoint, not just the app.

Internal notes stay internal

The thread separates public replies from internal notes. What the team writes on a ticket, the customer never sees — not in the portal, not by email.

No new passwords

The team signs in with a company Microsoft account, customers as invited guests to your tenant. When an employee leaves, IT handles it in one step — blocking the account removes access to the tickets too.

Just the support mailbox, nothing more

The app has permissions only to the shared support mailbox (read and send). It picks up mail delegated under the signed-in team member — no service identity with access to the whole company's mail.

No extra automations or servers

No Power Automate, no database or server on our side. The licence is just an encrypted file the app downloads from our CDN — nothing is sent, and no ticket data reaches us.

Licence

Monthly licence by company size

Up to 25 M365 users
€89 / month
26–70 M365 users
€145 / month
71–150 M365 users
€205 / month
More than 150 M365 users
Individual

The subscription depends on the total number of internal users in your Microsoft 365. Within a given size you get the full scope of the app, with no surcharges for individual features. Customers in your portal (invited guests) don't count toward the total.

Deployment

On-site implementation

€509 one-off

We help you get started: installation, connecting the shared support mailbox, an initial team workshop, theme setup to match your brand, configuration of categories, work types and SLA plans, optionally synchronising companies from EP365 CRM and a link with Worklog.

What is not included

The fixed price covers a standard rollout. Connections to CRM or Worklog and configuration beyond a standard rollout. We will send a precise quote after a short call.

Extended support

Support pricing

€110 / hour

Consultations, environment adjustments, custom reports or user support beyond the implementation.

How support is billed

Support is billed per started 15 minutes of work. We always tell you the expected scope in advance.

Prices exclude VAT
Where are our tickets and customer data stored?
Exclusively in your Microsoft 365 environment, within your SharePoint. The app has no database or server of its own — no data leaves your company. The licence is checked by downloading an encrypted file from our CDN, which sends nothing. Only what you choose to send leaves — for example a bug report e-mailed from the app.
How does an email become a ticket without Power Automate?
The app picks up the shared support mailbox via Microsoft Graph, delegated under the signed-in team member's account with FullAccess and SendAs on that mailbox. From each new message it creates a numbered ticket, sends a confirmation, and adds further emails in the same thread (or with the [HD-xxxx] tag in the subject) into the conversation. An unknown sender waits in Unassigned mail — you create the ticket after assigning them to a company.
Can a customer see other customers' tickets?
No. Each ticket and message has permissions set only for the requester, their company and the support team. A customer can't see others' tickets even with a direct link — the isolation is enforced by SharePoint itself, not just the app. The “Whole company” role additionally opens up colleagues' tickets from the same company; “Only my tickets” keeps the view to their own.
Who needs access to the mailbox, and does processing run outside business hours?
The app picks up the shared support mailbox itself via Microsoft Graph — under the account of a team member who has been granted permissions on the mailbox (FullAccess and SendAs; IT sets this once). Processing runs right in the browser, so it happens while the team works in the app (with a lock against collisions) — no server and no Power Automate. When no one has the app open, mail waits in the mailbox and is processed on the next open; the SLA is calculated from the email's arrival time. Round-the-clock 24/7 processing via a background service is an optional add-on for customers with Azure.
Do we have to have EP365 CRM and Worklog?
No, HelpDesk works on its own — you can keep companies and contacts directly in it. With EP365 CRM you additionally get synchronisation of companies, service contracts and contacts; with EP365 Worklog the logging of worked hours from closed tickets into timesheets. Both are optional.
How quickly do we deploy it?
Typically within half a day. You add the app to your Microsoft 365 environment, the first load creates everything needed by itself, and then you connect the shared support mailbox and set up SLA plans. Companies can be imported from CRM or created manually.
Can we adjust categories, work types and SLA?
Yes. Categories, work types and SLA plans (response and resolution by priority, business hours) are fully configurable in the administration. You add your own inbound-mail rules, macros and reply templates, and match the app's colour to your brand.
How do app updates work?
You upload the package to your App Catalog just once. New versions then load on their own and your admin manages them right inside the app — on the Version management card in Settings they can pin a version or roll back to an earlier one. No repeated package deployments: we ship improvements continuously — without a pinned version your site gets them automatically, with a pinned version you switch when you choose.