FFairday Docs
Open app
IntroductionWhat is Fairday?
Introduction

What is Fairday?

Fairday is an AI-assisted operations platform for building, running, and improving how work gets done inside an organization.

Open FairdayExplore Operations

Fairday at a glance

Fairday combines process design, service desk operations, organizational accountability, AI agents, goals, and issue tracking into one workspace. Teams can document repeatable workflows, trigger them from real requests, assign ownership, monitor execution, and improve outcomes over time.

Why teams use it

Fairday is designed to act as an operating system for internal work, especially where requests, approvals, handoffs, compliance, service delivery, or recurring execution need structure.

What Fairday can be used for

Fairday helps organizations turn operational knowledge into live systems that can be documented, triggered, owned, reviewed, and improved over time.

What organizations do with Fairday
Document internal processes in a structured way
Convert source material into usable operating procedures
Run processes consistently across teams
Connect service desk requests to operational workflows
Use AI to classify, route, and assist work
Assign accountability to owners, teams, and departments
Track goals and milestones
Manage issues and maintain written change history
Understand employee and agent involvement across the system
Typical use cases
IT help desk operations
HR onboarding and offboarding
Customer support operations
Finance approvals and request handling
Compliance and audit workflows
Cross-functional project execution
Internal service delivery and shared operations

Who Fairday is for

Fairday is suitable for organizations that need structure, repeatability, and visibility in internal operations. It is especially valuable when work spans support, operations, leadership, and other shared service functions.

Best fit organizations
Startups building their first scalable operating system
Mid-sized companies formalizing internal workflows
Support-driven organizations with service desk needs
Regulated teams that require process control and auditability
Operations-heavy businesses coordinating work across departments
Typical teams using Fairday
Operations
IT
Customer support
People / HR
Finance
Compliance
Revenue operations
Shared services
Leadership and department heads

Getting started

The best first implementation is usually narrow and practical. Start with one service desk, one important process, and one owner who can refine the system from real usage.

Recommended first setup
This sequence helps teams stand up Fairday in a way that creates immediate operational value without over-modeling the organization too early.
1
Create a service desk
Pick a shared internal function such as IT, support, or operations intake.
2
Publish one process
Start with a workflow that is repeated often and is painful when handled inconsistently.
3
Assign a responsible owner
Choose one person to keep the workflow, settings, and related documentation accurate.
4
Link the desk to the process
Give Fairday a valid operational path when incoming requests match the workflow.
5
Test end to end
Submit a real or simulated request and review what happens in the request detail page and Portal.

Overview

The Overview page is the command center for operational activity. It gives teams a high-level view of processes running, processes completed, service desk requests, and processes deployed so they can quickly understand system health and workload movement.

Key capabilities
KPI cards for active and completed operational work
Reporting tables for requests and processes
Control visibility for manual vs automated processes
Time filters and date range selection
Command-palette search support
Common use cases
Monitor current operations load
Review process execution across teams
Understand service desk volume
Identify what is live and currently deployed

Operations

Operations is the process system inside Fairday. It is where teams create, edit, publish, version, and run structured processes. Use Operations when you need to document a repeatable workflow, define handoffs, turn source material into a process draft, assign owners, configure execution logic, and maintain versions over time.

What Operations is for
Document a repeatable workflow
Define handoffs and steps
Turn raw source material into a process draft
Assign process owners
Configure execution logic
Publish and maintain versions over time
Viewer
Read the process as documentation, understand the published structure, and inspect the current process content.
Editor
Write and revise the process description using headings, lists, checklists, quotes, and links so the process stays understandable to humans.
Designer
Configure start nodes, define execution steps, control decision flow, and connect start and completion behavior to service desk workflows.
Settings
Assign a process owner, choose one-time or recurring behavior, configure manual start or automation start, and review linked trigger context.
Portal
Manage live process runs, track version history, restore prior versions, review run state, and complete operational work.

Process drafting from source material

Fairday supports turning source material into a written process draft. This makes it easier to start from existing content instead of writing processes from scratch, especially when the process already exists informally across notes, links, or operational guidance.

Supported source patterns
Notes
Links
Documents
Imported context
Pasted operational guidance
Use cases
Convert a meeting note into a formal process
Turn support guidance into a repeatable SOP
Draft a workflow from policy text
Transform existing documentation into an executable process

Process version control

Processes in Fairday support version history. Each version stores the historical state of the process so teams can review changes over time, inspect the creator and creation time, and restore earlier versions if needed.

Version history includes
Version number
Creation date and time
Version creator
Historical content
Historical structure
Use cases
Audit how a process changed
Restore an earlier workflow definition
Compare old and new process structures
Recover from an unwanted change

Service Desk

Service Desk is the request intake and triage system in Fairday. It allows teams to receive requests, classify them, route them, and optionally connect them to operational processes. Use it when users need to submit internal requests, ask for help from a shared team, trigger operational work from a service interaction, or receive AI-assisted routing and support.

Key capabilities
Multiple service desks by function
Custom desk configuration
AI-enabled response handling
Process linking per desk
Ticket assignment and comments
SLA tracking
Request detail views
Example desks
IT Helpdesk
Customer Support Desk
Finance Desk
People Ops Desk
Operations Desk

Service Desk + Process Automation

One of Fairday’s most powerful features is the ability to connect service desk requests to processes. A service desk can be linked to one or more processes, and when a request is submitted, the AI agent tied to that desk can analyze the request to determine whether a linked process should be triggered.

Example

An IT Helpdesk is linked to a Password Reset Process Macbook and a Laptop Issue Troubleshooting Process. A user submits: “Help me return my macbook password, use a process if possible.” Fairday can analyze the ticket, match it to the correct linked process, start the process run automatically, inform the requester that the specific process was triggered, and resolve the ticket once the linked process completes.

Faster request resolution
Requests reach the right workflow without waiting for manual triage.
More consistent execution
Recurring requests are handled through known processes instead of ad hoc responses.
Lower triage burden
AI can do the first pass of deciding whether a workflow should start.
Operational traceability
The system keeps a visible connection between the ticket, the triggered process, and the final outcome.

Service Desk Requests

Each service desk request has its own detail page. This page acts as the working record for the request, giving teams one place to understand the state of the ticket and any workflow that was used to resolve it.

Request detail includes
Request summary
Status
SLA information
Assignee
Comments
Linked process used
Link to the triggered process portal, when applicable
Use cases
Track request handling
Collaborate through comments
Review AI decisions
Move from ticket context into process execution

Goals

Goals gives organizations a place to define strategic outcomes and operational milestones. It supports both company-level and department-level goals so strategy stays visible inside the same system as execution.

What Goals is for
Define a company objective
Assign a single accountable owner
Break the objective into milestones
Optionally define success metrics
Make strategy visible inside the same system as execution
Use cases
Annual company priorities
Department quarterly targets
Operational rollout goals
Measurable strategic initiatives
Each goal can include
Goal title
Description
Scope: company or department
Owner
Optional success metric
Milestone list
Each milestone can include
Title
Description
Owner
Status
Optional success metric

Issues

Issues is the problem-tracking system inside Fairday. It allows anyone in the organization to report an issue and maintain a written record of the problem over time, including version history for issue descriptions.

What Issues is for
Report an operational problem
Assign follow-up to a team or person
Maintain detailed written context
Track issue evolution through versions
Use cases
Report broken workflows
Log product or process problems
Document operational incidents
Maintain a written issue history for audit and learning
Key capabilities
Reporter is automatically recorded
Assignment to a team, individual, or no owner
Issue list filters by team, individual, status, and created date
Detailed issue description page
Rich text editing
Issue version history
Restore prior issue versions

Agents

Agents lists the AI agents operating inside Fairday. Each agent has a role, scope, configuration, and budget so teams can understand what AI is doing and govern it clearly.

What Agents is for
Understand which AI agents exist
Configure what they can manage
Control agent responsibilities
Define linked desks and processes
Review agent skills and connectors
Use cases
Configure operational AI behavior
Limit or expand agent scope
Connect agents to specific desks or workflows
Govern AI responsibility inside the workspace
Agent detail includes
Tasks assigned
Skills
Connectors
Service desks managed
Linked processes managed
Budget
Editable name and settings
Current common agents
Process Designer Agent
Customer Service Desk Agent

Organization

Organization is the people directory and involvement reporting layer. It gives visibility into who is in the workspace, what role they have, and how they contribute across processes, requests, and operational outcomes.

Organization list page
Employee list
Role
Online or offline status
Access to each employee’s detail dashboard
Member detail page
Processes completed
Service tickets solved
Active time in the app
Calendar-style activity view
Average processing time for selected processes
Average SLA adherence
Average service ticket completion time
Date filtering
Use cases
Review operational involvement
Understand team participation
Evaluate workload contribution
Spot high and low activity periods

Teams

Teams help organize responsibility across the workspace. They are used to group users and control which teams are responsible for specific work.

Use cases
Assign issues to teams
Manage access boundaries
Structure departmental responsibility
Connect process ownership to departments

Settings

Settings governs workspace-level configuration. This is where the broader structure of the workspace is tuned so the rest of the platform behaves correctly for the organization.

Common configuration areas
Teams and access
Organizational defaults
Service desk controls
AI provider settings
Templates and integrations
Use cases
Configure the workspace structure
Manage admin-level operational settings
Define how the platform behaves for the organization

Search and Navigation

Fairday includes a command-palette search experience across core pages. The goal is to make moving across operations, requests, and dashboards faster than relying on sidebar navigation alone.

Features
Open with Command + K
Keyboard navigation with arrow keys
Enter-to-open behavior
Recent items and quick actions
Page-aware search results
Use cases
Navigate quickly across operations
Open requests and processes faster
Move efficiently between product areas

MCP Integrations

Fairday exposes a remote MCP endpoint so external AI clients can work directly with your workspace. Use it to create service desk requests, issues, goals, and AI-generated process drafts, or to query workspace status from ChatGPT apps, Codex, Claude, or any other MCP-compatible client.

Current capabilities
List service desks the current Fairday user can access
Create new service desk requests in a specific Fairday desk
List operations categories the current Fairday user can create processes in
Create new AI-generated process drafts directly in Fairday
List existing issues and create new issues in the connected Fairday workspace
List existing goals and create new goals with optional milestones
Query workspace status for running processes, completed processes, open service desk requests, and deployed processes
Setup flow
Open Account settings in Fairday and copy the MCP endpoint plus OAuth endpoints
For ChatGPT apps, connect Fairday as a remote MCP server and use OAuth instead of a personal bearer token
For Codex, Claude, or manual MCP clients, create a personal MCP token and connect with Authorization: Bearer <token>
Test the connection with list_service_desks, list_operations_categories, and query_workspace_status before using create tools
Client connection notes
ChatGPT apps: register Fairday as a remote MCP app, let ChatGPT use the Fairday OAuth flow, and authorize access from the Fairday consent screen.
Codex: add Fairday as a remote MCP server in your Codex plugin or MCP configuration and pass the personal bearer token in the Authorization header.
Claude: connect the same remote MCP server through Claude’s MCP connector settings with the Fairday personal bearer token, or migrate to OAuth later.
Authentication

Fairday MCP now supports OAuth for ChatGPT apps and personal bearer tokens for Codex, Claude, and manual clients. Personal tokens are user-scoped, org-scoped, and should be treated like credentials. Revoke any token you no longer want external tools to use.

Typical End-to-End Use Cases

These guides show how Fairday is typically used in practice. They are intentionally procedural so teams can map them to real adoption workflows inside the product.

Build a new repeatable process
Use this flow when you want to turn operational knowledge into a published workflow that can be reused consistently.
1
Open Operations
Start in Operations so the process can move through writing, design, publishing, and execution in one place.
2
Create a process from source material or from scratch
Use notes, links, documents, or pasted guidance as starting context if you are formalizing existing knowledge.
3
Write the process in Editor
Turn the core instructions into readable documentation that future operators can understand quickly.
4
Build the workflow in Designer
Define start conditions, steps, decision points, and completion logic so the process becomes executable.
5
Assign ownership and timing in Settings
Choose the responsible owner, decide whether the process is one-time or recurring, and set trigger behavior.
6
Publish and monitor in Portal
Create a version, review runs in Portal, and use version history if the process needs to evolve over time.
Expected outcome
You end up with a documented, owned, publishable process that can be read, run, and improved without losing version history.
Resolve a service request through a linked process
Use this pattern when a service desk receives recurring requests that should launch a structured workflow instead of being handled ad hoc.
1
Link one or more processes to a service desk
Choose the workflows that are valid candidates for the desk so Fairday has explicit options to evaluate.
2
Configure the process start node for service desk triggering
The start node should be able to accept service desk context if the desk’s AI agent decides the workflow is a match.
3
Let the requester submit a ticket
The ticket becomes the input context that Fairday uses for classification, routing, and process selection.
4
Allow the AI desk agent to evaluate the request
Fairday first decides whether a linked process could resolve the issue before defaulting to a text-only response.
5
Start the matched process run
If a linked process is the right fit, Fairday starts the run and informs the requester which workflow has been triggered.
6
Close the loop through Portal and the ticket detail page
The request detail page shows the linked process used, and once the process completes, the ticket can resolve automatically.
Expected outcome
You get faster resolution, clearer operational traceability, and less manual triage between intake and execution.
Track a strategic initiative
Use Goals when you want strategy and execution to live in the same operating system instead of separate planning tools.
1
Create a company-level or department-level goal
Start with the outcome the business wants to achieve and decide whether it belongs at the company or departmental level.
2
Assign one accountable owner
Every goal should have a single person responsible for coordinating progress and maintaining clarity.
3
Add milestones
Break the objective into smaller checkpoints that make execution visible and easier to monitor.
4
Define optional success metrics
Use metrics when you need a measurable definition of success for the goal or for individual milestones.
5
Review alongside the rest of the operating system
Keep the goal visible in the same environment as processes, requests, issues, and ownership so it stays operationally relevant.
Expected outcome
The initiative becomes visible, accountable, and measurable instead of existing only as a planning artifact.
Track and improve an issue over time
Use Issues when operational problems need a written record, an owner, and a versioned narrative of how understanding changes.
1
Report the issue with written context
Capture the problem in enough detail that others can understand the operational impact and likely next steps.
2
Assign it to a team, person, or leave it unassigned
Choose the most useful ownership pattern for the stage the issue is currently in.
3
Edit as the issue evolves
Refine the description over time as new evidence appears or the operational understanding becomes clearer.
4
Save new versions deliberately
Each meaningful edit creates a stronger written history of the issue and the decisions around it.
5
Restore prior versions if needed
Use version control when the current issue narrative becomes unclear or you need to revisit an earlier documented state.
Expected outcome
You maintain a durable, auditable history of the issue instead of losing important context across chats or status updates.

Product Positioning Summary

Fairday is best understood as a platform for operational execution. It helps organizations define how work should happen, connect requests to execution, use AI responsibly inside operations, assign ownership clearly, preserve written history, and improve visibility across people, processes, and outcomes.

Positioning

Fairday is especially valuable for organizations that are moving from informal work toward a repeatable, auditable, AI-assisted operating model.

Was this page helpful?
Next: Explore Operations