DigiRivet
← Back to catalogue
osTicket / Open Source

Keep support requests organized.

Manage requests received through email and forms as tickets. Route requests to the appropriate teams and agents.

osTicket

Example use case

  1. 01Request received
  2. 02Assigned
  3. 03Answered
Illustrative interface · Example content

Does this sound like your team?

  • 01Support requests get lost in email.
  • 02You need to see who owns each request.
  • 03You want conversation history in one place.

What can you do?

Bring requests together

Manage requests received through email and forms as tickets.

Assign responsibility

Route requests to the appropriate teams and agents.

Review conversation history

Review correspondence on the ticket to support handovers.

Track priorities

Use status and priority to organize work for the team.

DigiRivet

How can DigiRivet help?

The work below is separate from the platform’s standard features. Scope is agreed during discovery and the proposal.

Discovery and setup

We assess your users, content and working practices to prepare a suitable setup.

Tailoring and migration

We plan changes and migration after reviewing the source system.

Training and support

We agree training, maintenance and support options for your team.

Example use case

osTicket

You want to see who owns each request and its status instead of losing track in an inbox.

  1. 01Request received
  2. 02Assigned
  3. 03Answered

Illustrative workflow · Not an actual product screen or client project.

How we work together

  1. 01

    Define the need

    Discuss goals, users and your current setup.

  2. 02

    Prepare the platform

    Agree scope, then configure and tailor the installation.

  3. 03

    Start using it

    Complete checks and training, then agree ongoing support.

Common questions

Can we use our existing support email?

Your email provider and access requirements are reviewed to configure ticket collection and replies.

Does open source mean the entire project is free?

No. Software licensing is separate from setup, hosting, tailoring and support. Paid editions or extensions are identified separately.

Can existing data be migrated?

Migration scope and validation are agreed after reviewing the source system, data format and volume.

How is maintenance and support arranged?

Updates, backups, user support and service hours are defined in the proposal around your needs.

Find the right setup for your needs.

Tell us about your team, current tools and the work you want to improve. We can assess the platform and scope together.

← Back to catalogue