Start with a question, not a form
Employees describe what they need in their own words. They do not have to know which team owns it, what the process is called, or where the right form lives.
Employees describe what they need. AI finds the right form, fills in the details, and routes a complete request to the team that can help.
Nobody needs to know which form, queue, or department sits behind the request.
Employees describe what they need in their own words. They do not have to know which team owns it, what the process is called, or where the right form lives.
The portal works out which request fits the conversation. No form directory to search. No ticket bounced between teams because someone chose the wrong queue.
Superthread pulls useful details from the chat and asks short follow-up questions only when something is missing. The employee can review the request before it is filed.
Each submission becomes a card on the configured board, with its summary, priority, due date, files, and other details ready for the team to act on.
Learn more about Send it straight into deliveryPeople can see status, assignees, due dates, attachments, and the conversation around their request. They get an answer without chasing the service team in Slack.
Service teams can search and filter submissions by status or request type, see what is urgent, and manage the work alongside their projects, pages, and agents.
Learn more about Give the team one clear queueWhen the answer already lives in your workspace, the portal should surface it before anything enters a queue. If that does not solve the problem, the same conversation carries on into a complete request.
Internal service delivery does not have to feel like administering a ticketing system. Superthread brings the request portal, delivery boards, documentation, and agents together. Employees get a straightforward way to ask. Service teams get work they can actually act on.
See how to build forms, route submissions, and give people a place to submit and track requests.
Create a focused agent for triage, answers, or follow-up. It works from the requests, documentation, and delivery boards already held in Superthread.
Reads each submission, checks for missing context, sets useful properties, and routes the request to the right queue or owner. The receiving team starts with work it can act on.
Starts: a form is submitted or a new request enters a board
Uses the request and the documentation in its permitted spaces to find the relevant policy or process. Mention it on the card to get a grounded answer where the team is already working.
Starts: someone mentions it on a request or asks through Ask AI
Checks open work for overdue dates, unclear ownership, repeated blockers, and requests waiting too long. It can update the queue and create a concise handover for the service lead.
Starts: on a schedule, or when a request's status, owner, or due date changes
Keep each team's workflow separate while giving employees one familiar place to start.
Handle access, equipment, software, security, and facilities requests without a maze of service-desk forms.
Run onboarding, policy, leave, payroll, and people-operations requests with the right context from the start.
Collect purchase, vendor, payment, and contract requests, then route them to the people who can make a decision.
Give the whole company one place for creative, data, enablement, procurement, and other shared-service requests.
For internal request intake and delivery, yes. Superthread gives employees a simpler front door and gives service teams forms, queues, tasks, docs, and agents in one workspace. Teams that need a full ITIL system, a CMDB, or advanced incident management may still need specialist service-management software.
No. They can describe what they need in the portal and Superthread works out which form fits. It gathers the details through the conversation instead of asking the employee to understand your internal process.
Yes. In Ask mode, Superthread prepares the request and asks the employee to approve it. Teams can also use Auto mode when they want the agent to submit once it has enough information.
Each form is connected to a destination board. The submission creates a card there, so the service team can assign it, set its status, discuss it, attach files, and manage it with the rest of their work.
Yes. The portal has a personal request view and a team submissions view. Requesters and participants can follow status, assignees, priority, due dates, comments, and attachments.
That answer-first experience is what we are working toward next. The aim is to use the knowledge already in Superthread to resolve common questions immediately, then continue the same conversation into a request when somebody still needs help.
Yes. HR and People teams can manage onboarding, policy questions, leave and payroll requests, role changes, training, equipment coordination, and offboarding. See Superthread for Human Resources for the full workflow.
Yes. Use separate private spaces and control which employees, guests, and agents can access each one. The company can offer a familiar request experience without exposing HR, Finance, Legal, or IT work to the wrong people.
Internal service teams can create agents to triage new requests, find answers in service documentation, monitor queues, flag overdue work, route tasks, and prepare handovers. Agents can run on a schedule or when forms, comments, tasks, statuses, owners, and due dates change, with access limited to the relevant service spaces.
Yes. A small team can begin with one form and one delivery board, then add portals, private spaces, documentation, and agents as request volume grows. It does not require a large service-management implementation to get started.