Requests arrive everywhere. Track them in one place.
Turn mail into tasks, put recurring compliance work on a schedule that does not drift, and let anything sitting too long escalate itself instead of waiting to be noticed.
- Email intake
- Recurring work
- Auto-escalation
- Full audit trail
What usually goes wrong
Not a list of features — a list of the things teams tell us break down, and where Krrim puts them back.
Requests arrive by email, chat and shoulder-tap, and half of them are never recorded.
Give the project an intake address. Mail sent to it becomes a task, so the request exists whether or not anybody remembered to log it.
Recurring work — access reviews, certificate renewals — is remembered by one person until they are on leave.
Put it on a recurrence. Times are wall-clock in your timezone, and a monthly series on the 31st clamps to month end rather than skipping February.
Tickets sit in a status for weeks and nobody finds out until somebody complains.
Each status has its own staleness threshold. Stuck work badges itself, appears on a stuck board, and escalates on a ladder that terminates.
"Who was responsible for this" is impossible to answer after the fact.
Every task has one assignee and a full activity history, and every change — including ones made by an integration — is attributed and audited.
Monitoring already knows something is wrong, but somebody has to hand-create the ticket.
A scoped API token lets your alerting open a task directly, with an idempotency key so a retried alert never creates a duplicate.
The parts that carry the weight
Email-to-task
A per-project intake address. Subject becomes the title, body becomes the description.
Learn moreRecurring tasks
Daily, weekly, monthly or yearly. Idempotent by construction, so a scheduler retry cannot create the work twice.
Learn moreStaleness and escalation
Per-status thresholds — three days in "Input required" is a fire, three days in "Backlog" is Tuesday.
Learn moreQueues as views
Save the filter that is your triage queue, share it with the team, pin it to the sidebar.
Learn moreAlerting that opens tickets
Scoped tokens and idempotency keys, so a flapping alert does not become forty tasks.
Learn moreAudit trail
Every write records who, when and from where — with a service account named as itself rather than as the person who created its token.
Learn moreHow a week runs
Intake
Mail, an alert or a person — all three land as tasks in the same queue.
Triage
A saved view is the queue. Assign, prioritise and set the status that starts the clock.
Escalate on its own
Past the threshold, the task nudges its assignee, then the lead, then admins — once, and then it stops.
Review
Aging and distribution show where things pile up, and the audit log answers who did what.
Stop losing requests between inboxes
Email intake, recurring work and escalation that does not depend on someone remembering.
Free to start · No credit card required