Attain OS for IT and support teams

Every request gets a case, an owner and a fix that is written down.

Requests that arrive by form, chat, phone and hallway stop living in five different memories. They become cases with statuses, priorities and owners in one internal desk, and the fixes become notes your team can find next time. Attain OS is a case desk for small teams: it has no SLA timers, no customer portal and no email inbox.

14 days free · No card needed · Cancel anytime

Help Desk Software for Small IT Teams: Cases, Tickets and Runbooks

Who this is for

What this looks like today

Small internal IT teams, office managers who became the help desk, small managed service providers and support teams handling incidents, access requests, new-hire setups and equipment changes for people who need an answer today.

Three tabs are open on tickets you have not touched since this morning. Someone messaged you directly about a laptop that will not join the domain, so it exists nowhere in the queue. Two of your open cases are the same root cause and neither of you noticed. The remote-access fix you spent forty minutes on last quarter is in a chat message you cannot search. A client is on the phone asking for a status you would need ten minutes to assemble. The work is not the problem. The problem is that the record of the work is scattered across the places the work happened to arrive.

  • Requests arrive by chat, phone and someone stopping you in the hallway, and only some become tickets
  • The same five problems get solved from scratch every month because nobody wrote the fix down
  • Who is working what depends on a standup, and anything unassigned quietly ages
  • A new-hire setup needs the same six details every time, and you chase them over three emails
  • Handing a case to the next shift means retelling the whole story

What changes

Intake gets fewer doors. A public request form can open a Customer Care case for each submission, with the priority and tags you set on the form, shortly after it arrives, because processing runs on a schedule. For requests that come by chat or in the hallway, paste the message, upload a file or record a voice note in Smart Tickets, and Atty drafts the ticket for you to review. Email is not an intake channel: there is no forwarding address or shared mailbox.

Triage stays a human call, with better structure. A case moves through New, Triage, Assigned, In Progress, Escalated, Pending, Solved and Closed, with a priority, a category, labels, one or more assignees and a due date. Assignees are notified, and every field change is kept in the case history, so a handoff between shifts starts from the record. No status changes on a timer: a person sets every status, including Escalated.

Resolution feeds the next one. A case keeps its resolution summary and root cause, and you can ask Atty to turn that fix into a note, which waits for your approval. The next time the problem appears, the team opens the note or asks Atty, which reads the notes, cases and tickets in the current project.

Less typing at intake

Request forms collect the details you always have to ask for, and Smart Tickets turns a pasted message or a voice note into a drafted ticket you review. Before creating one, Atty checks for an active ticket with a similar title and asks whether to update that one instead.

One desk instead of a ticket tool, a wiki and a chat app

Cases, board tickets, notes, documents, forms and team chat are built into one workspace, so a fix written down once is not copied into three tools. Attain OS does not connect to your monitoring, remote-access or asset tools, so it replaces the glue between them, not the tools themselves.

Ownership you can see

Every case has assignees, a status, a priority and a due date, and its history shows who changed what. Attain OS has no SLA timers or response-time reports, so priorities and due dates on the shared calendar are how you keep promises visible.

The second time is faster

Repeat problems are what bury a small team. When fixes live in notes and past cases carry their resolution, the same people handle more requests without solving the same thing twice. Atty drafts the tickets and notes; a person approves each one.

The apps that carry the work

Every one of these is built in and already connected to the others. Nothing here is an integration you have to buy or wire up.

Forms

Request forms that open cases

Build forms for incidents, access requests, new-hire setup and hardware with text, dropdown, date, checkbox and rating fields, and share the public link. Each submission lands in a table and can open a Customer Care case with the priority and tags you set, shortly after it arrives. Forms have no file-upload field, so screenshots come later.

  • An incident report that opens a case
  • A new-hire setup form shared with managers
  • Access requests that ask for the approver's name up front
Forms
Smart Tickets

Tickets drafted from a message or a voice note

Paste a chat message, upload a file or record a voice note, and Atty drafts a Work Board ticket for you to review before it is created. It checks for an active ticket with a similar title and asks whether to update that one instead. Nothing is classified or routed on its own.

  • A hallway request captured before you forget it
  • A pasted chat message drafted as a ticket for review
  • A similar-title check before a second ticket is created
Smart Tickets
Customer Care

Cases from report to resolution

Each case holds a category, a priority from 1 to 6, assignees, a due date, labels, image attachments, internal notes and a resolution summary with the root cause, plus a history of every field change. You can share a read-only link to a case; there is no requester portal, and you cannot reply to the requester from the case.

  • Handoffs between shifts that start from the record
  • A read-only link to share a case with the requester
  • Resolution and root cause kept on every closed case
Customer Care
Work Board

Planned work on a board

Keep planned changes, rollouts and maintenance as tickets on a drag-and-drop board with statuses you define, priorities from P0 to P5, types and one or more assignees. New tickets start in the Backlog and move onto the board when work begins.

  • Laptop rollouts and upgrades as board tickets
  • Maintenance windows tracked beside reactive work
  • Tickets waiting to start, visible in the Backlog
Work Board
Notes

Runbooks your team writes by working

Write the fix as a note, with an image if it helps, link it to the client it belongs to, and share it by link when a user needs the steps. Atty reads the notes in the project, so the team can ask it how a problem was fixed last time.

  • Runbooks for the failures that repeat every month
  • Vendor and configuration notes linked to the client
  • How-to steps shared with a user by link
Notes
Customer Management

Requesters and client accounts

Keep each client or department as a customer record with contacts, address, labels and custom fields for equipment, licences or site notes, and link cases, tasks and notes to it. There is no asset register, so equipment details live in custom fields or documents.

  • Equipment and site notes in custom fields
  • Cases linked to the client they belong to
  • A one-off email to a client contact from their page
Customer Management
Conversations

Team chat beside the work

Channels, direct messages and threads for your team, with file attachments and voice notes with transcripts. Mention @atty in a thread to ask about a case or to draft a ticket, which the person who asked approves. Requesters outside your team are not in the chat.

  • An on-call channel for the week's incidents
  • @atty asked for the pending cases in a thread
  • Voice notes with transcripts for the next shift
Conversations
Atty Chat

Ask about your own cases

Atty reads the cases, tickets, notes and documents in the current project. Ask what was written on a past case, which cases are pending, or for a draft handoff note, and approve anything it wants to create. You can also ask it to set up a scheduled summary of open cases, which you approve once.

  • Look up a past fix before starting
  • A handoff note drafted for approval
  • A morning summary of open cases, set up once and approved
Atty Chat
Working guide

IT helpdesk software for a small team should turn each request into a case with a status, a priority, an owner and a due date, so nothing waits unassigned. It should also keep each fix written down with the case, so the next person can find it. Check whether you need an email inbox, a customer portal or SLA timers, because a small internal case desk may not include them.

In practice

Queue, chat requests and a repeat problem

  1. Morning · the queue

    The team lead reads the new cases, sets each priority and assigns an owner. Anything unassigned stays visible on the list until someone takes it. The priority scale is written down, so a priority means the same thing to everyone on the team.

    Customer Care
  2. Late morning · a message in chat

    A colleague writes in the team chat that a laptop will not join the domain. An engineer pastes the message into Smart Tickets, and the assistant drafts a ticket for review. Smart Tickets checks for a similar active ticket and asks whether to update that one instead.

    Smart Tickets
  3. Midday · a new hire's setup

    A manager submits the new-hire form two days before the start date. It lists the role, the device and the access needed on day one. IT builds the accounts, and the setup is tracked on the case with the same details, so nothing depends on three separate emails.

    Forms
  4. Afternoon · planned maintenance

    Rollouts and maintenance windows sit in the Work Board backlog until work starts. Each ticket has a type, one or more assignees and a due date. The board shows where each change stands, so the team can see what is next.

  5. Afternoon · the repeat problem

    Two cases describe the same VPN drop. The engineer fixes the root cause, writes the steps as a note and mentions that note in the internal notes of both cases. The next person who sees the symptom starts from the note instead of from scratch.

    Notes
  6. Friday · a status question

    A department head asks for the status of their open cases. The team lead reads each case's status, owner and resolution summary, writes the reply by hand, and checks the case history for recent field changes before sending it.

    Customer Care
Workflow map

Where requests, fixes and equipment are kept

JobAppWhat it does here
Requests and incidentsFormsA public form for access, hardware or incident reports can open a Customer Care case for each submission, with the priority and tags you set. Each submission saves in a table. Forms have no file-upload field, so screenshots arrive later through the case.
Triage and ownershipCustomer CareEach case has a category, a priority from 1 to 6, assignees, a due date and labels. A person sets every status, including Escalated, and every field change stays in the case history. There are no SLA timers.
Planned workWork BoardKeep planned changes, rollouts and maintenance as tickets with the statuses you define and priorities from P0 to P5. New tickets start in the backlog and move onto the board when work begins.
Fixes and runbooksNotesWrite each fix as a note with its steps, an image if it helps and the client it belongs to. Share a note by link when a user needs the steps. Notes are team records, not a public help center.
Requesters and equipmentCustomer ManagementKeep each client or department as a customer record with contacts, labels and custom fields for equipment or license notes. There is no asset register, so put equipment details in custom fields or documents.
Team chatConversationsChannels, direct messages and threads sit beside the work. Mention @atty in a thread to ask about a case or to draft a ticket, and the person who asked approves it. Requesters outside your team are not in the chat.
Start here

Forms and pages for IT requests

New-hire IT setup form

List the role, device and access a new hire needs on day one, so IT starts before the first morning.

Hardware request form

Name the device, the reason and the approver before a purchase, and the device being retired for a replacement.

Outage notification form

Gather the facts for a staff notice: which system is down, what still works and when staff will hear next.

Internal wiki page

Write one runbook page with an owner and a date, so the fix can be found the next time it breaks.

Mistakes to avoid

Three habits that keep work invisible

Letting requests skip the queue

A request made in a hallway or a direct message never becomes a case unless someone enters it. Ask the requester to use the form, or paste the message into Smart Tickets and review the draft. Nothing is classified or routed on its own, so the case still needs an owner.

Solving the same problem twice

Two cases with one root cause mean the second fix was wasted effort. Check the open cases and notes before starting work, and record each fix in the resolution summary and, if it will recur, in a note. A closed case with no summary helps nobody.

Expecting SLA timers to warn you

There are no SLA policies, first-response timers or automatic escalation. A due date and an assignee are how a promise stays visible, and a person sets Escalated. Do not assume the software will flag a case that has been waiting too long.

Working checklist

Morning check and close-out for each case

Every morning

  • Confirm each open case has one assignee.
  • Check that each priority still matches the impact.
  • Move any stalled case to the status that describes it.

When a case closes

  • Write the resolution summary and the root cause.
  • Turn a fix you will repeat into a note with its steps.
  • Tell the requester what changed, in the channel you agreed.
What this agreement means

What a small IT team decides first

  • Decide which request paths are allowed: form, chat or a message turned into a ticket.
  • Decide who sets priority and who may mark a case Escalated.
  • Decide which fixes must be written as a note before a case closes.

This is an internal case routine for a small team. It is not a service-level commitment, a security certification or a substitute for your incident response plan.

Frequently asked questions

Is IT helpdesk software the same as customer support software?

Not quite. Customer support software usually adds a public portal, email inboxes and response timers for outside customers. A case desk for an internal IT team sorts staff requests and incidents with owners and notes. Check whether your requesters can work without a portal, email inbox or SLA timers before you choose.

How do I keep an IT runbook people actually use?

Write one page per fix, with the steps, an owner and the date it was last checked. Link the page from the case that produced it, and retire pages that no longer match the system. Team notes are the record; they are not a public help center.

Can an assistant draft tickets from chat messages?

Yes, with review. Paste a chat message or record a voice note, and the assistant drafts a ticket for a person to approve. It checks for a similar active ticket first, and it does not classify, route or answer requesters on its own.

Is there a customer portal or an email address for requesters?

No. Requesters use a public form, and you can share a read-only link to a case. Attain OS has no requester login and no forwarding address, so emails and chat messages become tickets when someone pastes them in.

Who Attain OS Is For — One Operating System for the Team You Actually Run

Attain OS BETA