Product
Follow a request from start to finish: record it, assign it, track the time, and prepare the bill. Cards marked “In the product” are available now. Planned features are at the bottom, marked “On the roadmap”.
01
Each support request (ticket) keeps its whole history in one place, and a fair list decides what to work on next.
Each ticket (support request) has one history that is only ever added to, never rewritten. People, AI agents, and FlowRMM work records all go in the same place, so nobody checks three tools to learn what happened.
“Take next ticket” assigns you the most urgent request, using a published score based on priority, major incidents, wait time, and blockers. Easy requests no longer get picked first while an outage waits.
When three or more similar requests come from one company within an hour, FlowPSA shows a warning banner. Declare one major incident, then close the whole group at once with the cause attached.
Each request shows how similar requests were fixed before, starting with the same company, plus that customer's matching written procedures (SOPs). Use one and the link is saved with the fix.
Response-time promises (SLAs) count only business hours, skip holidays, and pause while you wait on the customer. Missed deadlines are calculated live, not by a nightly job.
Pick a set of team rules (Strict ITIL, Balanced MSP, or Rapid Agile) and FlowPSA follows it: limits on open work per person, a root cause on major incidents, linked knowledge, and linked devices before a request closes.
Incoming email joins the right request and ignores automatic bounce loops. Portal requests and FlowRMM alerts are counted once, so a resend never creates a second request.
02
Split a request into tasks, plan bigger jobs as projects, and track changes and repeat problems, all linked to the original request.
Split work into tasks under one request instead of making a new ticket for each team. Planned jobs are work orders. Bigger jobs with phases are projects. All time adds up on the original request.
A change cannot ask for approval until it has a plan to do it, a plan to check it, and a plan to undo it (rollback). Undoing a change is a normal outcome, not a failure.
Link many requests to one underlying cause. FlowPSA suggests groups of repeat issues, and solving the problem adds the cause and workaround to every linked request.
Repeating requests that catch up after a gap without creating duplicates, appointments checked against availability, and scheduled service reports as CSV files.
03
Time you can trust, customer agreements that do the math, and draft invoices a second person reviews before posting.
Weekly timesheets for each person and each AI agent. Changing a time entry needs a reason, and every changed field is recorded. Billing only uses approved weeks.
Included minutes, hourly rates, and billing increments for each customer. Minutes already billed come off the allowance, so extra time is simple math, not an argument.
Approved time becomes a draft invoice, and that time cannot be billed twice. Posting needs the billing role and a second person. FlowPSA does not send invoices on its own. Credits, debits, and accounting export use stable IDs.
04
A list of the equipment you look after, and a portal where your customers can see and submit requests.
Track equipment with asset tags, warranty, who has it, and its status, linked to the FlowRMM computer when there is one. Print QR labels and check a shelf with a laptop or phone camera.
Customers see their company’s requests, reply, attach files, and submit new requests through secure links that expire. Unlimited portal users. They can never decide an internal approval.
05
Connect your own AI app through MCP, a connection that lets compatible AI apps work with FlowPSA. Plus keyboard shortcuts for fast work.
MCP is a connection that lets compatible AI apps, such as Claude, ChatGPT, or a local model, work with FlowPSA. AI can sort requests, pick up work, write notes, and log time using over 100 defined actions at /api/v1/mcp. AI cannot decide approvals and never counts as a paid user.
A command search box and shortcuts for every area: g q queue, g w work, g t time, g a approvals. Built for people who work in FlowPSA all day.
Roadmap
These are not available yet. When one ships, everyone on FlowPSA gets it at no extra charge.
Opportunity to quote to sales order to contract, without making sales the home screen.
Contract-driven recurring lines alongside time-based drafts.
Serialized and bulk stock, POs, and supplier records.
A connector for quote and change sign-off.
Held back until contracted quantities are stored durably. We will not invent true-ups from inventory counts.
A timeline view over the task graph that already exists.
FlowPSA is for IT support companies (MSPs), in-house IT teams, and solo operators who use FlowRMM or plan to.
