Techottic

Process management across every department

Work that
outlives
the inbox.

From a one-line request to a project that runs for months, across every department and every role it touches. The record is the work itself, not a thread in one person's mailbox: a new starter can pick it up on their first day, and nothing walks out of the door when somebody leaves. Your customers see the same clarity your team does.

Talk to us about your processesSee how a desk is defined
OPSOPS0000442Air handling unit, level 3Filed 14:02
FLTFLT0001180Van 12 service overdueFiled 14:09
QAQA0003067Batch deviation, line 3Filed 14:11
CLINCLIN0000889Consent form wording changeFiled 14:26
INTINT0009106Laptop will not wake from sleepFiled 14:31
Three of these departments do not ship with the product. Somebody defined them, and each got its own counter that none of the others can read.

Why most rollouts stall

A tool arrives with somebody else's idea of how a company is organized, and every team that does not fit starts working around it. Legal keeps a shared mailbox because there is no request type for a contract review. The fleet manager keeps a spreadsheet because vehicles are not an asset class the tool understands. The work still happens. It just stops happening anywhere you can see it, report on it, or hand it over when somebody leaves.

The five that ship seeded, three a customer added, and one nobody has defined yet.

Three colleagues reviewing printed figures together at a meeting tableFIN

Finance

  • Expense claim
  • Purchase request
  • Invoice query
  • Corporate card

A sign-off step that holds the payment work until somebody decides, and a receipt rule the claimant reads before they submit.

Three colleagues talking through printed layouts pinned to a boardMKT

Marketing

  • Design request
  • Campaign brief
  • Brand asset
  • Event support

A brief that cannot be filed without a deadline, because a request without one sits behind everything that has one.

Four colleagues packing and labeling boxes for dispatch in a bright roomOPS

Operations

  • Facilities
  • Fleet and travel
  • Supplier issue
  • Site access

Anything unsafe jumps the queue and pages a person, rather than waiting politely for business hours.

Two people shaking hands across a desk at the end of an interviewHMR

HR

  • Leave request
  • Payroll query
  • Reference letter
  • Policy question

A bank detail change calls the number already on file before anything moves. That step is not optional.

A rack of network and server equipment in a data centerINT

IT

  • Hardware
  • Access and accounts
  • Network
  • Software

The desk the others were modeled on, with the device, the site and the patch level already attached.

Customer definedFLT

Fleet

  • Service due
  • Breakdown
  • Driver assignment
  • Fuel card

A breakdown on a route pages the duty manager. A service due next month waits its turn.

Customer definedQA

Quality

  • Batch deviation
  • Audit finding
  • CAPA
  • Supplier quality

A deviation carries the batch number from the moment it is raised, because finding it later is the expensive part.

Customer definedCLIN

Clinical

  • Consent form
  • Site query
  • Protocol amendment
  • Ethics submission

Anything touching consent goes to a named reviewer, never to whoever is free.

___

Yours

  • Legal
  • Fleet
  • Quality
  • Clinical
  • Procurement

Name it, give it a prefix, and write the questions it needs answered. Nobody has to ask us to add it.

The same request, from both sides

An employee picks a team. The team gets a queue that is only theirs.

/portalsigned in as an employee
The employee portal: a Who can help you panel of five department tiles, Information Technology on INT, Finance on FIN, Marketing on MKT, Operations on OPS and HR on HMR, each with a one-line description of what it handles and either a count of that person's open requests or an invitation to ask that team
What an employee seesNo queue, no jargon, no guessing which team owns the problem. One tile per desk, each saying what it handles and how many of your requests it already has. Somebody who has never opened the tool before does not need to be told where an expense claim goes.
/ticketssigned in as the platform owner
The staff queue: tickets carrying seven-digit numbers on the INT, FIN and MKT prefixes, each row showing a priority, a subject written in that desk's own words, a requester with a VIP mark where one applies, and a status
What the team seesThe same requests, landing on the desk that owns them, already carrying a priority, a requester and a status. This is the platform owner's view, which is why three prefixes share one list: a laptop that will not sync before a board meeting, a corporate card declined at check-in, booth graphics for a summit. The prefix on the number is what says whose work each one is.

How it holds up once it is running

Separation that holds under a URL

Operations staff see Operations. Not a filtered view of everything, and not a link that fails after they click it. The department predicate is in the SQL that answers the question, so a guessed address returns nothing rather than something it then hides.

Each desk owns its own words

Finance defines Finance's categories, Marketing defines Marketing's. Categories are retired rather than deleted, because the name on a request filed two years ago still has to read correctly.

Clocks that pause honestly

Waiting on the requester stops the clock. A target that keeps running while your team is blocked is a number nobody trusts, and a number nobody trusts gets ignored.

It answers to your other systems

A REST API your own apps can file into, Microsoft Entra for sign-in, and sessions hosted from the technician's own Teams account rather than a shared service mailbox.

How it is licensed

Per organization, not per department

Defining a sixth department does not trigger a conversation with us. Charging by department would price the exact behavior the product exists to encourage.

Your instance, your database

Each client corporation runs as its own instance with its own data, its own branding and its own identity provider connection.

Ask us for a number

Pricing depends on scale and on what you need connected, so there is no table here pretending otherwise. One conversation is usually enough to give you a real figure.

Read the detail

DSK0000001DesksDefine a departmentREQ0000001RequestsThe life of one requestEXP0000001ExperienceBoth ends at onceBND0000001BoundariesWho sees what

Every department you run. Not every department we imagined.

Talk to us about your processesSign in to your workspace

The first of those opens your mail client, addressed to contact@technooptics.com. A person reads what arrives.