One Service Desk for Every Department: Inside TATER Ops

Service management software has a structural problem. ServiceNow's IT Service Management module is licensed separately from HR Service Delivery, which is licensed separately from Customer Service Management, which is licensed separately from Field Service. By the time an organization has consolidated its service desks, it is paying for four or five overlapping platforms — each with its own admin learning curve, its own data model, and its own integration story.

TATER Ops asks a simpler question: if every department's workflow is fundamentally "someone needs something done by someone else by a date," why are they running on different platforms? Built on the same identity, database, and audit infrastructure as TATER Security, TATER Ops gives organizations one customizable service surface for IT, DevOps, HR, accounts payable, accounts receivable, operations, and anything else that takes requests.

Hierarchical Categories

The foundation of TATER Ops is the category tree. A category defines a service surface — an icon, a color, a default priority, response and resolution SLA targets, optional per-category statuses, optional custom request fields, and an optional default approval chain. Categories nest up to 5 levels deep, so an "IT" parent can contain "Helpdesk", "Hardware", and "Access & Identity" subcategories, each of which can contain its own children.

Crucially, each level can override its parent's defaults. The "IT / Helpdesk" subcategory might keep the IT color but use a stricter 2-hour first-response SLA. The "AP / Invoice Review" subcategory might inherit a custom field set for invoice number, vendor, and amount. Tasks store the full breadcrumb path ("AP / Invoice Review / Approval Pending") so the value remains stable even if the tree gets reorganized.

Custom Priorities and Statuses

The built-in priority lifecycle is Critical / High / Normal / Low and the built-in status lifecycle is Open / InProgress / OnHold / Closed / Cancelled. Many organizations want different labels — P1/P2/P3, or Urgent/Standard/Backlog. TATER Ops lets each org replace the built-in lists entirely with custom labels and colors. Order matters: the first row in the priorities list is the highest.

Statuses can be customized per category. HR Onboarding might use Submitted → IT Setup → Equipment Issued → Training Assigned → Day 1 Ready → Closed. AP Invoice Review might use Received → Awaiting Manager → Awaiting CFO → Approved-Pay → Paid → Closed. The task detail modal renders status-change buttons based on the category's defined lifecycle, so users always see exactly the right transitions for the work they're doing.

"The cleanest service management platforms are the ones that disappear. Each department thinks it's running its own thing. Operations thinks of it as facilities tickets. AP thinks of it as invoice approvals. HR thinks of it as onboarding workflow. They're all running on the same primitives."

Multi-Step Approval Chains

Approval workflows are a first-class feature. Each category can declare a default approval chain — Manager → Director → CFO, for example. New tasks in that category automatically pick up the chain. Each step has a designated approver, a label, and a status (pending, approved, rejected, skipped). The chain advances one step at a time. Only the user whose email matches the current step can act on it. Rejection halts the chain immediately and remaining steps are marked as skipped. Every action is recorded in the audit log with user ID, timestamp, and an optional note.

Bulk Actions and Self-Service

Triage at scale is built in. Bulk-edit mode adds checkboxes to the tasks list, exposing a toolbar with Set Status / Set Priority / Reassign / Close / Archive operations. Up to 500 tasks can be processed per bulk operation, with per-task success/failure tracking and a single audit log entry for the whole batch.

For requests that come in from outside the app, TATER Ops includes two intake paths. The first is a hosted self-service portal — a single-page form at /request.html that any end user can submit through. Each org generates a per-org intake token and receives a portal URL to share on intranets, employee portals, or as QR codes for facility issue reporting. The second is email-to-ticket via Power Automate: a flow that watches a shared mailbox (helpdesk@yourcompany.com) and POSTs each new email as a JSON task. Multiple mailboxes can be routed into different categories — IT to "IT", HR to "HR", AP to "AP" — with the same intake token.

Searchable Everywhere

One of the most underrated features is native typeahead. Every dropdown in TATER Ops — categories with full breadcrumb paths, assignees from the People directory, teams, parent tasks — uses HTML5 datalist for instant autocomplete. No scrolling through hundreds of options. Type to filter, click to pick.

Cross-Product Bridge

Because TATER Ops shares a database with TATER Security, tasks can optionally cross-link to compliance entities. A failing control in TATER Security shows a "+ Task in Ops" button on its detail panel. An auditor working in TATER Ops sees the linked control's live status inline. Audit findings can spawn remediation tasks. HR onboarding tasks can reference the policy-acknowledgment requirements they're tracking against. The cross-product bridge is optional — TATER Ops works as a standalone service desk for organizations that don't need the compliance side.