[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Use cases](https://cotlet.dev/use-cases.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup)

# Triage new ResMan work orders with AI

> Read new ResMan work orders, set priority and category by your rules and assign each to a technician. Runs daily, you approve every change.

Source: https://cotlet.dev/integrations/resman-api-mcp-server/triage-new-work-orders

Residents send maintenance requests through the Resident Portal and the Resident Mobile App at any hour, and each one lands as a new work order that someone on the site team has to read, prioritize and assign before a technician can start.

Cotlet does it in your own ResMan account with list\_work\_orders, get\_work\_order, list\_work\_order\_options and update\_work\_order, called by your AI agent, an n8n workflow or a script.

[Sign up free](https://cotlet.dev/app/signup?app=resman) [All ResMan tools](https://cotlet.dev/integrations/resman-api-mcp-server.md)

Hosted · nothing to install or maintain

## Can ResMan do this on its own?

ResMan Maintenance has Maintenance Workflows to assign tasks and track timelines, and its page lists Smart Automation with InCheck for automatic assignment (checked 23 Oct 2026). The ResMan pages do not describe a feature that reads a request and sets its priority by your own wording rules. The Partner API can read, add and update work orders, but only for approved Integration Partners, so a property manager cannot call it from an agent.

## How you do it in ResMan today

1. Residents submit work orders through the Resident Portal or the Resident Mobile App, with images if they add them, and the requests appear in ResMan Work Order Management.
2. A site manager or maintenance supervisor opens each new work order, reads the description and the photos, and sets its category and priority.
3. The same person assigns the work order to a maintenance employee and notes any appointment the work needs before someone enters the unit.
4. ResMan Maintenance Workflows assign tasks and track timelines, and ResMan lists Smart Automation with InCheck, which assigns work automatically. A site without them repeats this by hand for every request.
5. The list grows with each request, so an urgent one such as a broken door lock is easy to miss between routine ones.

## How to triage new ResMan work orders with AI

Prompt

```
List the new Submitted work orders at Lemon Tree. Set the priority by my rules (no heat, water leak, broken door lock = High), pick the category, assign each to a maintenance employee I name, and list the ones you are unsure about.
```

1. 01  
### Pull the new requests  
Your agent calls list\_work\_orders with status Submitted for each property you name. ResMan answers only when at least one filter is set, so the status filter is what makes the call valid. A login without access to the property gets APP\_PERMISSION\_DENIED and the run stops before any change.
2. 02  
### Read each request in full  
get\_work\_order returns the description, the location, the impacted areas and the pets the resident listed. Photos are attached as documents and the agent does not look at them, so a request that only says "see photo" goes on your list.
3. 03  
### Match the category  
list\_work\_order\_options returns the categories and areas your account defined. The agent picks only from those names and never invents a category. A request that fits none of them stays unassigned with a note.
4. 04  
### Set priority by your rules  
The agent applies the wording rules from your prompt and picks Low, Medium or High. Anything that mentions gas, flooding or smoke is not routed at all: it goes to the top of your report so you can call the technician yourself.
5. 05  
### Assign and save  
update\_work\_order sets the priority, category and assignee. ResMan accepts only employees marked as maintenance employees as assignees, so a name that is not one is refused and the agent lists that request for you. Residents can follow a work order, so each update asks for your OK until you switch confirmation off.

### What you get back

Example data

```
Submitted work orders at Lemon Tree: 6
Assigned 4, e.g. #1453 "Tear in the carpet" (Unit 100): Medium, Carpet, Robert Wilcox
Set High 1: #1457 "No heat in bedroom" (Unit 214)
Left for you 2:
- #1458 "Smell of gas in hallway" (call now)
- #1459 "See photo" (no description)
```

### Other ways to ask

- Every morning at 7, assign new work orders in the Plumbing category to Robert Wilcox and the rest to the on-call technician I name.
- Show me work orders that are still Submitted after 2 days and tell me which unit each is in.
- Only set priority, do not assign anyone, and send me the list.
- Mark Closed work orders older than 30 days at Lemon Tree for my review, but change nothing.

## What ResMan allows, and what to know first

- ResMan work orders have the statuses Submitted, Not Started, In Progress, Completed, Scheduled, Cancelled, Closed and On Hold, and the priorities Low, Medium and High.
- A work order description holds up to 248 characters; longer text belongs in the notes field.
- A work order can sit at a unit, a building, a rentable item or a WOIT account, and the impacted areas come from a list each client defines.
- Only an employee marked as a maintenance employee can be assigned a work order.
- ResMan lets residents track the progress of their work orders in the Resident Portal and Resident Mobile App, so a status change is visible to them.

update\_work\_order asks for your OK by default. To run it daily without you, switch confirmation off for that tool in your dashboard.

Sources: [ResMan Maintenance](https://www.myresman.com/solutions/maintenance/) · [ResMan Partners API Documentation](https://partners-api-docs.myresman.com/)

## Call update\_work\_order from a script

curl

```
curl -X PATCH https://cotlet.dev/api/v1/resman/properties/f308c33b-5865-4f7e-97af-46d35f19eddf/work-orders/a68ce6b2-a9ef-4127-bf97-067e9f4a548c \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"status":"Not Started","priority":"High","assigned_to_person_id":"b5efc29c-a706-4a95-a92f-7b1adcdd7c5c"}'
```

Example response

```
{
"work_order_id": "a68ce6b2-a9ef-4127-bf97-067e9f4a548c",
"property_id": "f308c33b-5865-4f7e-97af-46d35f19eddf",
"status": "Not Started",
"priority": "High",
"assigned_to": "Robert Wilcox"
}
```

MCP: add https://cotlet.dev/mcp/v1 with the same key; the call is resman\_write → update\_work\_order. Example data.

[Schedule it in n8n, Make, Zapier or cron](https://cotlet.dev/integrations/resman-api-mcp-server.md#automations)

## ResMan tools this automation uses

__Cotlet ResMan tools used to triage new ResMan work orders with AI__
| Tool | Parameters |
| -------------------------- | --------------------------------------------------------------------------------------------------------------- |
| list\_work\_orders | property\_id, status, priority, location, assigned\_to\_person\_id, modified\_since |
| get\_work\_order | property\_id, number |
| list\_work\_order\_options | none |
| update\_work\_order | property\_id, work\_order\_id, status, priority, category\_id, assigned\_to\_person\_id, scheduled\_date, notes |

[All 13 ResMan tools with descriptions](https://cotlet.dev/integrations/resman-api-mcp-server.md#tools)

## Frequently asked questions

### Is it safe to connect ResMan to Cotlet?

Yes. You sign in to ResMan yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get ResMan once you enable it, every background request is listed, and the browser profile is stored encrypted with AES-256-GCM, the cipher 1Password uses for its vaults. The AI model never sees a login, posts and messages wait for your OK, and Disable for agents cuts access in one click. Independent scanners grade cotlet.dev A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory; live results are on https://cotlet.dev/security.

## More ResMan automations

- [Track ResMan make-ready units with AI](https://cotlet.dev/integrations/resman-api-mcp-server/track-make-ready-units.md)
- [Summarize ResMan aged receivables with AI](https://cotlet.dev/integrations/resman-api-mcp-server/aged-receivables-summary.md)
- [ResMan API and MCP server: every tool](https://cotlet.dev/integrations/resman-api-mcp-server.md)
- [All use cases](https://cotlet.dev/use-cases.md)

## Give your agent access to ResMan.

Free 7-day trial with 2,000 credits, no card needed. Cotlet is independent and not affiliated with ResMan.

[Sign up free](https://cotlet.dev/app/signup?app=resman)

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [Use cases](https://cotlet.dev/use-cases.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md)

**Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet)

**Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md)

**Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md)

**Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors)

**Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet)

Cotlet.dev is built by Bart Krawczyk and Jake Slugocki, the founders of Take Group sp. z o.o., ul. Wincentego Janasa 4, 40-855 Katowice, Poland. KRS 0000871398, NIP 6342984273, VAT EU: PL6342984273. [About us](https://cotlet.dev/about.md)

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.