Use case · Software, integration, operations
Anonymised, like all our use cases
Every request a ticket, every area on its own.
A company manages tasks for several areas and clients. We built a ticket system for it in which every tenant has its own tickets, tags, people and email address. Requests by email automatically become tickets, with an AI summary of the thread.
Deployed in
Project and order management
Services
Software, integration, operations
Tenants
Separate, each with its own email address
Permissions
Read, edit, administer
From the inbox to the board.
Emails to a tenant’s address become tickets if the sender is approved. With the tag [#412] in the subject, every further email lands in the same ticket. On the board, one drag changes the status.
How a task runs.
- Intake By email to the tenant’s address or by hand. On the board, the plus creates a ticket right in the matching column.
- Assign Owner, client including external ones, due date, value in euros, tags and the matching GitLab issue.
- Work Change the status by dragging, record discussions in the history. Every field change is logged automatically.
- Close Completed and cancelled tickets move to the archive, read-only and always easy to find.
- Evaluate Opened and closed tickets, lead time and values across all tenants, exportable for spreadsheets.
7
statuses from “Open” to “Cancelled”
3
access levels per tenant
1
subject tag keeps the email thread in the ticket
0
tickets from senders without approval
One application, six areas.
For everyone who manages tasks, and for everyone who should only read along.
Platform
Tenants
Tiles with open and total tickets and the assigned people, as blocks or a list.
Software
List
Search by number, title, tags and people, filters with hit counts, total value and export. Filters live in the URL and can be shared.
Software
Board
One column per status, drag cards to move them, create tickets right in the column.
Automation
Email intake
Whitelist per tenant, held emails to approve, original formatting with collapsed signatures and quotes.
AI
Summary
For tickets from emails, the AI summarises the thread, refreshed at the push of a button.
Software
My tickets and reports
Everything I own across all tenants, ordered by due date. Plus key figures per period.
What makes the difference.
Tenants cleanly separated
Tickets, tags, people and email address belong to exactly one tenant. A ticket never changes it.
Nothing gets lost
History entries are fixed once saved, the change log writes itself.
No email sprawl
Only approved senders create tickets. An admin decides on all other emails.
Permissions per tenant
The same person can administer one tenant and only read the next.
What we built it with
- .NET 10
- Blazor
- .NET Aspire
- PostgreSQL
- Redis
- MailKit
- GitLab
- Docker
- GitLab CI
- Ansible
- OpenTelemetry
Where do tasks get lost for you?
In an intro call we look at how requests from email, phone and meetings can land in one place.