FirstHelpdesk

A simple, fairly priced helpdesk for small and mid-sized teams, with a shared inbox, customer portal, phone call logging, service levels, rules and reports.

Client

FirstHelpdesk

Industry

Customer Support

Website

Visit
C# .NET 10 Blazor SQL Server AWS Stripe

Background

FirstHelpdesk is our own helpdesk product: a simple, fairly priced helpdesk for small and mid-sized teams. It brings a shared inbox, a customer portal, phone call logging, service levels, rules and reports together, for one price per agent.

It began with our own support desk. Like many software companies, we handled customer support in Jira, and it never quite fitted. When a customer copied a colleague into an email, that colleague was left out of the conversation, and their reply opened a brand new ticket. We wanted a helpdesk built for the way support actually works, and one we could recommend to the smaller teams we work with. So we built it, and our own support is moving onto it first.

FirstHelpdesk opens to its waiting list soon, and you can see the full feature list at firsthelpdesk.com.

The Challenge

Most helpdesks are built for large support teams, and priced that way. A low starting price is common, but service levels, automatic assignment and reports are often kept for plans that cost two or three times as much. For a team of five, that adds up quickly.

The teams we had in mind have a few things in common:

  • They take a lot of their contact by phone. A helpdesk that only understands email misses half the picture.
  • They promise response times. Service levels need to respect working hours and holidays, and pause while the team waits on the customer.
  • They don’t have an administrator. Setup has to be quick, and the everyday tools have to make sense without training.
  • They look after other people’s data. Customers need to trust that the helpdesk keeps their information private.

What We Built

FirstHelpdesk is a multi-tenant web application written in C# and Blazor on .NET 10, with SQL Server for data. It runs on Amazon Web Services behind Cloudflare, sends email through Twilio SendGrid, and takes payments through Stripe, so card details never reach our servers.

FirstHelpdesk ticket list showing open tickets with status, priority, channel and service level countdowns
The ticket list. Design mock-up: every ticket, customer and figure shown is made up.
AreaWhat it does
Shared inboxEmail becomes tickets, with canned replies, internal notes, @mentions, merging, tags and saved views
Customer portalCustomers raise and follow their tickets, in English, French, German or Spanish
Phone callsLog a call with caller lookup and a call timer, even for callers without an email address
Service levelsWorking hours, holidays, pausing while waiting on the customer, and a “Breaching soon” view
AutomationRules that act on events or time, round-robin or least-busy assignment, a REST API and webhooks
Reports and wallboardResponse and resolution times, service levels met or missed, and a wallboard for the office screen
Incident reportsDrafted, reviewed and approved, then sent to the customer as a branded email with a PDF
Teams and rolesOwner, Admin, Supervisor and Agent roles, with custom fields and branding on higher plans

Key Technical Decisions

  • Everyone copied in stays on the ticket. Anyone in CC becomes a participant on the same ticket, and a reply from any of them is matched back to it rather than opening a new one. This was the problem that started the whole project, so it was the first thing we got right.
  • Each team’s data is walled off in the database. All customers share one database, and SQL Server row-level security keeps every helpdesk’s rows separate, even if the application asked for the wrong ones. Uploaded files are scanned for viruses, and all traffic to and from a helpdesk is encrypted.
  • Support access is off by default. Our staff can only open a customer’s helpdesk when the customer allows it, and every visit is recorded in an audit log that can’t be changed. Two-factor sign-in, a full data export and UK GDPR export and erase are built in.
  • Plans are data, not code. Each plan’s limits and its prices in pounds, euros and dollars are stored in the database, and billing runs per agent through Stripe, with Stripe Tax working out VAT.
FirstHelpdesk ticket screen showing the original request, people copied in, ticket properties and service level progress
A ticket, with the original request pinned at the top and the service level clock on the right. Design mock-up: every ticket, customer and figure shown is made up.

Pricing

FirstHelpdesk has one price per agent, billed monthly, with no charge for customers or portal sign-ins:

PlanPrice per agent a monthBest for
Starter£5 + VATUp to five agents and one mailbox
Team£8 + VATMost teams: reports, wallboard, rules, automatic assignment and several service levels
Business£12 + VATEverything in Team, plus your own branding and the audit log download

Every account starts with a 30-day free trial of the Business plan, with no card needed. Prices are also available in euros and US dollars on the pricing page.

FirstHelpdesk workflow settings where statuses can be renamed, recoloured and reordered
Workflow settings, where teams rename, recolour and reorder their statuses. Design mock-up: every ticket, customer and figure shown is made up.

The Outcome

FirstHelpdesk is built and opening soon, with our own customer support as its first helpdesk. Teams can read about every feature, see how it compares with other helpdesks, check how it handles security, and join the waiting list.

For us, FirstHelpdesk is a product built the way we build for clients: start from a real problem, keep the everyday screens simple, and get the security and data handling right from the first line of code. If your team needs a helpdesk that doesn’t hold the useful parts back for a top tier, take a look.

You can find out more at www.firsthelpdesk.com.

One price per agent, from £5 a month + VAT

Service levels and reports on the Team plan

30-day free trial, no card needed

Like What You See?

Get in touch to discuss your project requirements.