Smart Dispatch
One button gives each person the most urgent request next, using a published score. A big outage does not wait behind password resets.
Autonomous PSA for FlowRMM
Tickets that fix themselves. On real endpoints.
FlowPSA is a fully autonomous PSA. AI agents pick up the ticket, run the fix through FlowRMM on the real endpoint, check it worked, and close the request with the proof attached. People approve the money.
For example
A web server goes down. FlowPSA opens a ticket, an agent works it through FlowRMM, brings the server back online, confirms it is responding, and records what it did. The time lands on a draft invoice for a person to approve.
PSA stands for professional services automation. Here, it means organizing the work of a service team.
FlowPSA is an add-on to FlowRMM Business · combined $1.50 per endpoint (enrolled computer) per month, from $150/mo · no per-technician fees
FlowPSA / Tickets / INC0001042
PersonAgentFlowRMM evidence
INC0001042HighResolved · vetted
VPN drops at Acme Warehouse
- Company
- Acme Corp
- Site
- Acme Warehouse
- Device
- acme-wks-01
- Owner
- Alex
Illustration of one support request (ticket) in FlowPSA, with made-up Acme example data. Press play or pick a step.
- shared record with FlowRMM
- 1
- AI actions available over MCP
- 100+
- per-technician fees
- 0
- people to post an invoice
- 2
The promise
Open one request. See the whole story.
A ticket is a support request. Anyone on your team should be able to answer these five questions from that one screen, without opening other tools.
- 01
What is the work?
The title, type of request, priority, and the latest message from the customer.
- 02
Who owns the next move?
A named person or AI agent who has taken it from a team list.
- 03
What changed most recently?
The newest entry in one history that is never rewritten.
- 04
Who and what is involved?
The company, location, contacts, and the FlowRMM computers involved.
- 05
Is the computer actually fixed?
A recorded FlowRMM session or checked action, not just a note saying “fixed.”
The daily loop
From the first request to the invoice.
Each request moves through the same five steps. When FlowRMM fixes the computer, the record of that work is saved on the request, and approved time becomes a draft invoice.
01
Intake
A request arrives by email, the customer portal, a FlowRMM alert, or an AI agent. A resend never makes a second request.
ensure_work_item02
Assign
The most urgent request goes to the next person by a published score, not by preference. Tasks go to the right team list under the same request.
claim_next_ticket03
Work
Open FlowRMM from the request to work on the computer. The session and the approved action are saved in the request history.
session.attached04
Close
Tasks are done, changes are approved, proof from the computer is saved, and a named person signs off. Then it closes.
resolution_gate.passed05
Bill
Approved time is applied to the customer agreement and becomes a draft invoice. A second person reviews it before posting.
invoice.draft
Autonomous agents
Agents do the work. People approve the money.
Agents claim the next ticket, run remediation on the real endpoint through FlowRMM's actions, verify the result with a fresh check, and resolve the ticket with the evidence attached. Invoices and billing stay with people. This works through MCP, a connection that lets compatible AI apps such as Claude, ChatGPT, or a local model work with FlowPSA. FlowPSA itself decides what the AI is allowed to do, not the AI's instructions.
- No paid AI add-on. You choose the AI and pay its vendor, not us.
- You can assign work to an AI agent like a person, and it never counts as a paid user.
- Agents resolve tickets on their own once FlowRMM verifies the fix. Invoices need people.
claim_next_ticketget_ticketfind_similar_resolutionsdetect_incident_stormscheck_resolution_gaterequest_resolvelog_timeget_weekly_timesheetcreate_changerequest_change_approvalpreview_invoicerequest_invoice| Action | MCP agent | Person |
|---|---|---|
| Open a ticket, add an internal note | Yes | Yes |
| Assign an owner, add tasks | Yes | Yes |
| Send a customer-visible note | Proposes | Approves |
| Log billable time | Proposes | Yes |
| Fix an endpoint through FlowRMM | Yes | Yes |
| Resolve with a verified FlowRMM check | Yes | Yes |
| Resolve without a verified check | Proposes | Vets |
| Approve a change | Never | Second person |
| Post an invoice | Never | Second person |
FlowPSA enforces these rules itself. Agents fix and close verified work on their own. Posting an invoice always needs a second person: the person who asked cannot approve their own request.
Everyday help
Less searching. More finished, billed work.
Outage Shield
Seven people at Acme Corp report the same problem. Your team can link the requests to one incident, record the fix, and close the related requests together.
Resolution memory
See how a similar problem was fixed last time at this company, and the written procedure that applies, before anyone starts guessing.
Changes with a way back
A change cannot ask for approval until it says how to do it, how to check it, and how to undo it. Undoing a change is a normal outcome, not a failure.
Timesheets with a full history
Changing a time entry needs a reason, and the old value is kept. Billing only uses weeks that a person approved.
Agreements to invoices
Prepaid hours, rates, and billing increments per customer. Approved time becomes a draft invoice, and a second person reviews it before it is posted.
Works with FlowRMM
Keep the computer work with the support request.
FlowRMM lets your team connect to computers and do the work. When a technician uses it, the remote session and approved actions show up on the support request in FlowPSA, so nobody has to copy notes between tools.
No duplicate requests
If FlowRMM sends the same alert twice, you still get one request. Each message carries an event ID.
Optional
FlowRMM works the same with FlowPSA turned off. Teams using only FlowRMM never see a FlowPSA charge.
One computer count
Billing uses the enrolled computer count FlowRMM already reports.
Separate permissions
Being an admin in FlowRMM does not make someone an admin in FlowPSA. Each app has its own Microsoft Entra roles.
FlowRMM
schema publicConnects your team to computers
- Endpoints and inventory
- Remote Console sessions
- Approved actions + verify
- Endpoint MCP
FlowPSA
schema flowpsaOrganizes requests, time, and billing
- Tickets, tasks, changes
- Time and timesheets
- Agreements and SLAs
- Draft invoices + PSA MCP
One Postgres
tenant_idclient_idsite_iddevice_idThe same customer, site, and computer records in both apps. No nightly copying, no mapping spreadsheet.
Technical detail: FlowPSA keeps its data in its own section (schema) of the same Postgres database FlowRMM uses, with the same customer, site, and device IDs. There is no mapping table and no nightly sync.
Pricing
Pricing based on managed computers.
FlowPSA is an optional add-on to FlowRMM Business, billed on the same count of enrolled computers (endpoints). Hiring people or adding AI agents does not raise the price.
FlowRMM Business + FlowPSA
$1.50/endpoint/mo
100-endpoint minimum, so it starts at $150/month. All FlowPSA modules.
That is FlowRMM Business at $1 (from $100/mo) plus the FlowPSA add-on at $0.50 on the same count. FlowPSA is not sold without FlowRMM.
- ✓ Never billed: technician seats, including part-time and after-hours
- ✓ Never billed: mCP agent accounts (your AI vendor bills its own usage)
- ✓ Never billed: client portal users
- ✓ Never billed: a paid “AI” add-on from FlowDevs
Billed on your enrolled count. The minimum is 100 endpoints. Adding technicians or AI agents does not change this price.
FlowRMM Business (required base)
250 billed endpoints × $1
$250/mo
FlowPSA add-on (optional)
Same 250 endpoints × $0.50
$125/mo
Estimated combined total
$375/mo
Estimate only, not a bill or quote. Estimates assume the same enrolled count for the whole month. FlowRMM bills enrolled endpoint-months, so computers enrolled for part of a month are prorated.
Honest scope
What is not in the product yet.
FlowPSA already handles the daily work: requests, assignments, changes, projects, time, agreements, and draft invoices. These are planned next. We will not label them as available before they are.
Quotes and sales orders
Opportunity to quote to sales order to contract, without making sales the home screen.
Recurring invoices
Contract-driven recurring lines alongside time-based drafts.
Stock and purchase orders
Serialized and bulk stock, POs, and supplier records.
E-sign
A connector for quote and change sign-off.
License and seat reconciliation
Held back until contracted quantities are stored durably. We will not invent true-ups from inventory counts.
Project Gantt
A timeline view over the task graph that already exists.
FAQ
Common questions.
Request access
Request access to FlowPSA.
Tell us about your team. We will follow up and show you a real support request on a real computer, not a slide deck.
- Self-serve by default. Set it up next to FlowRMM with the guides. Hands-on setup help is optional, never required to get a licence.
- A published price. FlowPSA adds $0.50 per endpoint to FlowRMM Business, for $1.50 combined, from $150/mo. No quote call, no per-user count, no onboarding fee.
- A direct line. Your feedback shapes quotes, stock, and recurring billing as they ship.