The gap
Big changes wait on a yes no one can find.
An invoice over a limit. A price drop across the catalog. A refund past a rep’s ceiling. The yes that should gate each one lives in a Slack thread or a forwarded email — so it stalls, or it gets skipped. oozmi gives it one place to happen:
Raise credit limit · customer #88
- 0 missed payments since 2019
- Current exposure €3,200
- Undo in one step, any time
Raised from anywhere
It’s the same ticket, whatever raised it.
Finance, the AI, a workflow, support, operations — they all raise the one object you just saw. Same envelope, same approve-or-reject, same trail. No separate approval tool to wire up per team.
- Finance an invoice over the approval threshold
- oozmi AI a price change it wants to apply
- A workflow a step that moves money or customer state
- Support a refund past the rep’s limit
- Operations a stock write-off
Why the yes holds
A pause is only worth it if you can trust what comes out.
- A named yes Nothing commits until a specific person approves. The system proposes; a person decides.
- No silent waits It routes to the owner and escalates on an SLA — the wait sits on the record, not in someone’s head.
- Logged & reversible Every change records what moved, from what to what, and who decided — and any of it can be undone.
- Inside permissions The decider only sees what they’re allowed to. Scripts and the AI are held to the same line.
- 14:02 Workflow wf-0214 Raised — credit limit, customer #88
- 14:02 Policy Routed to Finance lead
- 15:08 Stefan P. Approved
- 15:08 Ticketing Wrote CRM #88 · wf-0214 resumed
Undo is the same one click, in reverse.
Built in, by design
- 1 queue every team works from — finance, ops, support, and the AI
- 0 approval tools to bolt on or integrate
- 4 beats logged on every yes — raised, routed, decided, recorded
Boundary
The approval engine, not your help desk.
Ticketing is the cross-module sign-off step, built into the platform and used the same way from finance, operations, support, and the AI. It is deliberately not trying to be the customer-facing help desk you’d replace Zendesk with — and we’ll tell you which side of the line you’re on.
- Built into the platform from day one — nothing to integrate per module.
- The right shape when a change needs a person before it commits: money, customer-facing state, a sensitive AI move.
- Routing, escalation, SLA, and the audit trail as the mechanism, not bolted on after.
- One queue every team works from — finance, ops, support, and the AI.
- A customer-facing support desk with public portals, macros, and CSAT — that depth is still deepening.
- An engineering project tracker. That is Jira’s job, and we don’t pretend otherwise.
- A reporting tool. The SLA surfaces as a KPI in PA; the analysis lives there.
- A replacement for a full ServiceNow ITSM estate. We solve the approval, not the service catalog.
Bring one approval you still run over email.
Twenty-five minutes. We take one sign-off your team does by hand today — an invoice over a threshold, a refund past a rep’s limit — wire it as a ticket from the module that raises it, and walk the audit trail it leaves behind. If it holds up against your real approvals, we talk pilot.