Service desk

Every client request, answered on time and on the record

Emails, portal requests and phone calls become tickets on one shared queue — with the whole conversation, a visible response clock, and the time your team spent on it, ready to bill.

app.aspirepro.io/tickets
The AspirePro service desk queue: tickets with company, status, priority, board and response-time clock

Help desk software turns incoming requests — emails, portal submissions, calls your team logs — into tickets on a queue, so nothing depends on somebody remembering to follow up. AspirePro's service desk is built into the same system that runs your projects and invoices: every ticket belongs to a client company, the time logged on it lands on the person's timesheet, and billable time becomes a line on the invoice — approved first, if you require it — without being typed a second time.

One queue

Nothing lives in someone's inbox

Email a board's address and it becomes a ticket with the thread intact. Anyone on the team can pick it up; nobody has to be copied in.

Visible clocks

You see the deadline before the client does

Each queue carries response and resolution targets. A ticket running late shows up on the queue today, not in a quarterly review.

Billable

Support time reaches the invoice

Log time on the ticket. It lands on the weekly timesheet and becomes a line on the client's invoice — after approval, if you require it.

Boards

A separate queue for each kind of work

A board is a queue for one kind of request — Support, Website Requests, IT Helpdesk. Each board has its own statuses, priorities, types, tags and sources, its own mailbox, its own rules and survey, and its own access list. Look at one board at a time, or the whole business at once.

  • Statuses and priorities per board, so a website queue never has to borrow the support workflow
  • A mailbox per board: it sends and receives as itself, and replies thread correctly
  • An access list per board, so a contractor sees one queue and not the whole company
  • Saved views and bulk actions for the daily triage pass
app.aspirepro.io/tickets
The ticket queue showing subject, company, status, priority, board and tags for each ticket
The ticket

The whole conversation in one place

Open a ticket and the customer thread, internal notes and forwards sit in one feed, with status, priority, type and assignee on top. Tasks, logged time, scheduled work, attachments, the survey result and the change history each have their own tab — so the record answers "what happened here?" without a hunt through email.

  • Reply, add an internal note, or forward from the same composer, with templates
  • Log time as you reply — tick a box rather than opening a timer app
  • AI reads the thread and proposes the tasks still open; you confirm before anything is added
  • Link a ticket to a project and hand its checklist to the project board when support becomes delivery
  • A full history of every change, so escalations are never guesswork
A ticket header showing status New, priority Low, type and the assigned agent
The ticket record
Email

Email in, email out — and the threads stay together

Connect an Outlook (Microsoft) mailbox to a board and incoming mail becomes tickets; a Google or other support address forwards its mail to the board's own forwarding address. Replies attach to the right ticket instead of creating duplicates, because AspirePro follows the mail provider's own message headers rather than guessing from the subject line. Outgoing mail goes out as the board, so clients reply to support@ and not to whoever happened to answer.

  • Outlook (Microsoft) mailboxes connect with a sign-in and are read directly, with no shared passwords. Google Workspace and Gmail boards send as the mailbox and receive by forwarding a copy to the board's own address
  • Auto-replies, customer addresses and templates set per board
  • A Failed emails screen shows anything that could not be sent or read, so nothing vanishes silently
app.aspirepro.io/tickets/settings
The board settings page listing the Support and Website Requests boards with their mailboxes
Rules and targets

The rules do the chasing, so people don't have to

Every board can have rules: when these conditions match, take these actions. Move a ticket forward on the first reply. Warn the assignee when a response target is about to be missed. Route by type or source. Recurring schedules open the same monthly maintenance ticket without anyone remembering to.

  • Response and resolution targets per board, with late tickets flagged on the queue
  • Conditions combine status, priority, board, type, tags and time elapsed
  • Recurring tickets for monthly maintenance and check-ins
  • Every rule that fires is logged, so a surprising status change is explainable
app.aspirepro.io/tickets/settings
The ticket rules list showing auto-progress on first reply and a response-target warning
Satisfaction

Ask how you did, and keep score

When a ticket reaches a status you have marked as the moment to ask, the client gets a one-question survey. The answer is stored with the board, the company and the person who handled it — so satisfaction can be read by team and by client, not just as a number in an email.

  • One-click rating on a public page that shows only the ticket number and subject
  • Satisfaction score and response rate on dashboards and scheduled reports
  • Breakdowns per person and per board for the coaching conversation
The satisfaction dashboard showing average score, satisfied percentage, response rate and individual ratings
Satisfaction surveys
How it works

From request to invoice

1

A request arrives

A client emails the board address, submits through the portal, or your team logs the call. It becomes a ticket on the queue.

2

Someone picks it up

They reply from the ticket, log the time it took, and move it through the board's statuses.

3

The clock keeps everyone honest

Response and resolution targets track each ticket; the survey goes out when it closes and records what the client thought.

4

The time gets billed

Logged time lands on a timesheet and becomes an invoice line under the client's agreement — approved first, if you choose.

Questions

Frequently asked questions

What is help desk software?
Help desk software captures client requests as tickets on a shared queue, tracks each one through to resolution, and keeps the full conversation and history on the record. The point is that support stops depending on individual inboxes and memory: anyone on the team can see what was promised, what was done, and what is still open.
How does email-to-ticket work?
You connect an Outlook (Microsoft) mailbox to a board with a normal sign-in, and mail sent to that address becomes a ticket. A Google Workspace, Gmail or other support address sends as the board but is never read, so you forward a copy of its mail to the board's own forwarding address instead. Either way, later replies attach to the same ticket because AspirePro follows the mail provider's message headers rather than guessing from the subject line. Replies go out as the board, so the client keeps one tidy thread.
Can I run separate queues for different teams?
Yes — that is what boards are. Each board has its own statuses, priorities, types, tags, sources, mailbox, rules, survey and access list. Most teams run one per service line, and the ticket list can show one board or every board at once.
What happens with duplicate tickets?
Merge them. The duplicate moves to a Merged status — closed quietly, with no closing email or survey — and links into the ticket you keep. Its messages appear in the surviving ticket's conversation, marked with where they came from; a client replying to the old thread lands on the right ticket automatically; time and files stay on their original records. Merges can be undone, and any message can be split out into its own ticket.
Does it track response-time promises (SLAs)?
Yes. Each board carries response and resolution targets and picks the clock they run on: around the clock, your business hours (with holidays), or a custom schedule. Statuses such as "Waiting on customer" pause the clock. The queue flags tickets approaching a target as well as ones that have missed it, and rules can act when a target is missed — including emailing a standing list of people on every miss.
Can clients submit and follow their own tickets?
Yes, through the client portal. It is a separate login tied to a contact, and every ability — seeing tickets, creating them, replying, changing status — is switched on individually, and only for the boards and companies you allow.
Is support time billable?
Time logged on a ticket flows onto the person's weekly timesheet. Billable time becomes work in progress — once a manager approves it, if the client is set to approved time only — and is pulled onto an invoice under the client's agreement, so support hours reach the invoice without anyone re-typing them.
Do you measure client satisfaction?
Yes. Moving a ticket into a status you have flagged as the moment to ask sends the contact a one-question survey. Ratings are recorded against the board, company and agent, and are available as metrics on dashboards and scheduled reports.
Documentation

Read the documentation

The full how-to for this module, written for the people who use it every day.

Bring your whole services business together

Stop stitching together five tools. Run sales, delivery, support, and billing from one organization — with an AI assistant on every page.