IT helpdesk for MSPs
multi-tenant configuration step by step
How to run a helpdesk for many MSP clients? Multi-tenant, per-client SLA, reporting, time tracking for billing, and portal white-labeling in ManageEngine ServiceDesk Plus.
If you run an MSP (Managed Service Provider) and serve 10, 50, or 100 clients, a regular single-tenant helpdesk is a nightmare. Each client can see other clients' data, tickets get mixed, reporting becomes impossible, and billing turns into financial chaos. In this article I show how to build an effective MSP helpdesk in ManageEngine ServiceDesk Plus MSP Edition - with data separation, per-client SLA, billing reports, and portal white-labeling. This is a practical guide for people who already have SDP and want to scale it across many clients.
How an MSP helpdesk differs from a corporate one
A corporate helpdesk serves one organization. An MSP helpdesk serves 50-100 organizations simultaneously - each with different SLAs, categories, technology, and expectations. These differences fundamentally shape how the platform must be built.
Corporate helpdesk
- 1 organization, 1 IT structure
- All users see the same service portal
- SLA is identical across the company
- Reports go to one management team
- sysop@company has access to everything
- Cost: lower infrastructure complexity
MSP helpdesk
- 50-100 organizations, 50+ IT structures
- Client A only sees their own tickets
- Client A has 4h SLA, client B has 24h
- Client A receives SLA report, billing for hours
- MSP technician sees everything, each client sees only theirs
- Cost: higher complexity, but one backend for all
Multi-tenant - how to separate client data
Multi-tenant is an architecture where a single ServiceDesk Plus instance serves many clients (tenants), and each only sees their own data. ManageEngine MSP Edition is the dedicated build for this model.
Step by step: creating new tenants (clients)
- Admin Panel → Tenants → New Tenant
- Provide tenant data:
- Tenant Name: client name (for example "ACME Corporation")
- Subdomain: acme.helpdesk.msp-domain.com (each client gets their own subdomain)
- Admin Email: admin@acme.com (tenant-level admin account)
- Tenant Admin Password: password for the tenant admin
- Language: Polish or English
- Click Create - the system automatically provisions the new tenant with a separate dataset, separate users, separate SLA and category settings.
- Send an invitation to the tenant admin - they can sign in at helpdesk.acme.com, change their password, and start configuring their structure.
From this point client ACME does not see client IBM, their tickets, or their reports. This is critical for security and trust.
Permissions per client (Role-Based Access Control per Tenant)
Within each tenant you assign roles:
- Tenant Admin: full access to configuration, SLA changes, categories, technicians, reports
- Agent (Technician): can view and update tickets assigned to them
- Customer (End User): can create tickets, view their own, use the self-service portal
- Manager: access to reports and SLA analytics for the selected tenant
Pro tip: the MSP technician should not have Tenant Admin access on every client - that is a security risk and complicates access auditing. Better: 1-2 people with full access, the rest of the technicians have standard per-client access.
Per-client SLA - configuration and monitoring
Every MSP client has a different service package - and therefore a different SLA. A premium client gets a 4-hour SLA, a basic client a 24-hour SLA. ServiceDesk Plus MSP Edition supports this.
Defining SLA packages at the tenant level
- Sign in as Tenant Admin (for example admin@acme.com) at helpdesk.acme.com
- Admin → SLA Policies → New SLA
- Define the SLA matrix for ACME:
- Critical Incident (for example, a server is down): 2 hours to acknowledgment, 4 hours to resolve
- High Incident: 4 hours to acknowledgment, 8 hours to resolve
- Normal Incident: 8 hours to acknowledgment, 24 hours to resolve
- Request (password change, etc.): 4 hours
- If client IBM has a different package - sign in as IBM Tenant Admin and define a different SLA.
- The system tracks SLA compliance for each tenant independently.
Per-client SLA monitoring (MSP dashboard)
As an MSP (master admin), you can have a dashboard that shows SLA compliance for all clients at once - per tenant percentage and number of incidents resolved within SLA. A typical view lists clients side by side (for example, "Client A: 15 of 15 incidents within SLA", "Client B: 22 of 24 within SLA").
This is the data the MSP shows in executive reports to each client. You can set a warning threshold (for example, falling below a defined SLA compliance level), after which the Service Manager gets an alert and investigates - perhaps additional capacity or process improvement is needed.
Reporting for MSP clients - what to show
The MSP and the client must reconcile SLAs each month. Reporting is the documentation that justifies a price change or scaling.
Reports you should send to every client
- SLA Compliance Report: what percent of tickets were resolved within SLA? For ACME: 98% within SLA, 2% delayed due to X (for example, resource constraints). Demonstrates MSP professionalism.
- Ticket Volume and Trend Report: how many tickets came in this month? Trend versus the prior month? For ACME: 120 tickets in May vs 115 in April - trend +4%. Useful for capacity planning.
- Time Spent Report (Billing Report): how many hours did technicians spend on each client? ACME: 80 hours of technician work in May (= 80 hours × rate = PLN). Basis for invoicing.
- Category and Priority Distribution: what problems were most common? ACME: 40% Hardware, 30% Software, 20% Network, 10% Access. Shows where to focus technically.
- MTTR and MTTF (Mean Time To Resolve/Fix): average time to resolution? ACME: 3 hours on average. Benchmark against the industry.
How to generate reports in MSP Edition
- Admin (master) → Reports → Tenant Reports
- Select the tenant (for example ACME)
- Select the period (month, quarter)
- Select the report type (SLA, Time Spent, Categories, etc.)
- Export to PDF and send it to the client
Billing and time tracking - helpdesk integration
The most important part of an MSP: hours spent per client = revenue earned. ServiceDesk Plus has built-in time tracking.
Time tracking on every ticket
- The technician opens an ACME ticket: "Laptop will not start"
- "Start Timer" button - the system records the timestamp: 10:15
- The technician fixes the laptop: installs a driver, restarts, tests - 45 minutes of work
- "Stop Timer" button - the system records the end: 11:00
- The ticket automatically logs: Time Logged: 0h 45m
- Ticket closure → the system adds those 45 minutes to ACME's billing for May.
Manual tracking (if the technician forgets the timer)
- Ticket opened → Worklog tab
- Add Worklog → enter the time manually (for example 2 hours) plus a work description
- The system adds it to billing
Billing report: Time Spent per Tenant per Month
- Admin → Reports → Time Spent Report
- Filter: Tenant = ACME, Month = May 2026
- Result (example): the system sums hours logged by each technician on the client and shows the monthly total.
- Client billing = sum of logged hours × agreed hourly rate - the report supplies the hour count, the rate is set in the contract with the client.
Portal white-labeling - selling under your brand
Instead of logging in to "helpdesk.msp-rotech.eu", client ACME can have a portal on their own domain: support.acme.com. That is white-label - your logo and colors, but ServiceDesk Plus underneath.
White-label configuration per tenant
- Admin (master) → Tenants → ACME → Branding
- Customize:
- Portal Name: "ACME Support Portal"
- Portal Logo: upload ACME's logo
- Portal Colors: primary = ACME blue, secondary = ACME gray
- Portal Domain: support.acme.com (requires a DNS CNAME pointing at your instance)
- Footer Text: "Supported by Rotech Group" or "ACME IT Support"
- Email Signature: "ACME Support Team" instead of "Rotech Group"
- Save - the ACME portal now looks like ACME's own system, while technically it is your instance.
DNS setup for support.acme.com
Ask ACME to add to their DNS:
After 24 hours of DNS propagation, support.acme.com is live while still pointing at your ServiceDesk Plus infrastructure.
Note: white-labeling is a sales lever for an MSP. You can sell the helpdesk as "the client's own system" under their brand - it raises perceived value and supports higher pricing.
FAQ
Can I use standard ServiceDesk Plus for many clients?
Technically yes - you can create a separate SDP instance per client. But it is inefficient: you manage 20 instances instead of 1, and backups and upgrades become a nightmare. MSP Edition is the dedicated multi-tenant build - all clients in one instance, data separated, each only sees their own tickets.
How many clients fit in one ServiceDesk Plus MSP Edition instance?
One MSP Edition instance serves many clients (tenants) at once - that is the essence of the multi-tenant architecture. The practical number of clients and technicians depends on server capacity, workload intensity, and ticket volume. Hardware requirements and scaling guidance are in the official ManageEngine documentation; at larger scale, consult the vendor or implementation partner.
Can each client have a different SLA?
Yes, this is the main advantage of MSP Edition. Each client (tenant) has its own SLA, categories, workflow, and permissions. Client A can have a 4-hour SLA, client B 24-hour. Automation rules, reports, and permissions are independent per client.
How do you track time for billing from helpdesk activity?
ManageEngine SDP has built-in time tracking on tickets. The technician can enter time manually, or the system can track automatically from Assigned to Closed. For billing: Admin → Reports, pick Time Report per Client - the system shows exactly how many hours each technician spent on each client every day.
Can the client portal look different for each client?
Yes. In MSP Edition the self-service portal can be white-labeled per client - client logo, colors, domain. The client visits support.acme.com and sees ACME branding instead of ManageEngine. This lets MSPs sell the helpdesk under the client's brand.
Need help setting up a multi-tenant helpdesk for your MSP?
Rotech Group implements ManageEngine ServiceDesk Plus MSP Edition - from multi-tenant planning through tenant setup to white-labeling and billing integration. We walk you through every step.
Book an MSP consultation →