Bring requests together
Manage requests received through email and forms as tickets.
osTicket / Open SourceManage requests received through email and forms as tickets. Route requests to the appropriate teams and agents.
Example use case
Manage requests received through email and forms as tickets.
Route requests to the appropriate teams and agents.
Review correspondence on the ticket to support handovers.
Use status and priority to organize work for the team.
DigiRivet
The work below is separate from the platform’s standard features. Scope is agreed during discovery and the proposal.
We assess your users, content and working practices to prepare a suitable setup.
We plan changes and migration after reviewing the source system.
We agree training, maintenance and support options for your team.
Example use case
You want to see who owns each request and its status instead of losing track in an inbox.
Illustrative workflow · Not an actual product screen or client project.
Discuss goals, users and your current setup.
Agree scope, then configure and tailor the installation.
Complete checks and training, then agree ongoing support.
Your email provider and access requirements are reviewed to configure ticket collection and replies.
No. Software licensing is separate from setup, hosting, tailoring and support. Paid editions or extensions are identified separately.
Migration scope and validation are agreed after reviewing the source system, data format and volume.
Updates, backups, user support and service hours are defined in the proposal around your needs.
Tell us about your team, current tools and the work you want to improve. We can assess the platform and scope together.