RubymazeRubymaze

RubyDesk · Ticketing & helpdesk

Every request, owned and on the record.

RubyDesk gives your team one place to receive, prioritise and resolve requests, with SLA targets, a customer portal and a complete audit trail behind every ticket.

Try the demoBook a demo

01Try it

Run a small helpdesk right here.

Add a ticket, change its priority, assign it to an agent and move it across the board. Watch the audit trail keep up.

RubyDesk · Ticket board
Interactive demo

Use the buttons to move a ticket on, or drag a card into another column.

Open

2
  • RD-101High

    Invoice PDF is not reaching the client

    SLA 4h
  • RD-102Low

    Reset password for new starter

    SLA 24h

In progress

2
  • RD-103Medium

    Printer offline on the second floor

    SLA 8h
  • RD-104Urgent

    VAT report shows the wrong period

    SLA 1h

Resolved

1
  • RD-105Medium

    Add a new branch to the portal

    SLA met

Audit trail

  1. #01Demo board loaded with 5 sample tickets.

Sample data only. Nothing you do here is saved or sent anywhere.

02What's inside

Calm support, by design.

The things a helpdesk needs to keep promises, and nothing that gets in the way.

  • Tickets that stay organised

    Priorities, categories, teams and assignment, plus saved views and templates for the requests you see every day.

  • SLA policies

    Set response and resolution targets by priority, so the urgent work is always the work in front of you.

  • A customer portal

    Requesters sign in with a magic link to raise tickets and follow their progress. No passwords to forget.

  • A full audit trail

    Every change to a ticket is recorded, so you can always answer who did what, and when.

  • Time tracking and comments

    Log time against a ticket and keep the whole conversation, attachments included, in one place.

  • API keys and webhooks

    Connect RubyDesk to the rest of your tools with API keys, and have it tell them when something changes.

03The ticket lifecycle

From request to resolved.

A simple path that every ticket follows, with a record at every step.

  1. Request arrives

    A requester raises a ticket from the portal, or your team logs one for them.

  2. Triage

    Set the priority, pick a category and assign it. The SLA clock starts with the priority.

  3. Work it

    Comment, attach files and log time as the ticket moves to In progress.

  4. Resolve

    Mark it resolved. If something was missed, reopen it. History is kept either way.

Ready to see RubyDesk with your team's requests?

Book a short demo and we'll walk you through RubyFinance, RubyDesk, or both.

Book a demo