Follow up on overdue Rent Manager service issues every week

1. Open Service Manager and pick one of your customized service issue lists, which sort open issues into separately managed lists.
2. Sort by date and open every issue older than a week to read its assignee, schedule and latest note.
3. Call or message the technician on each stuck issue, then change the status (New, Work in Progress, Resolved) or reassign it to another Rent Manager user.
4. Open the tenant on each long-waiting issue and send an update from the Text Messaging Center.
5. Repeat across every list and property. Issues with no assignee, and tenants who never hear back, are the ones that fall through.

Find service issues at all properties open for more than 7 days. Assign the unassigned ones by trade, ask the technician for an update on the stuck ones and text tenants who have waited over two weeks.

1. 01

   Pull what has aged past your line

   list_service_issues with older_than_days set to your threshold, per property or across all of them, gives the open list. Recurring issues that Task Automation posts on a schedule, such as a monthly filter change, are reported apart, because they age by design.

2. 02

   Sort into the four piles that need different action

   The agent groups issues as unassigned, assigned but still New, Work in Progress with no schedule, and scheduled with the date already passed. Each pile gets its own proposal instead of one generic nudge.

3. 03

   Propose, then change with your OK

   Unassigned issues get an assignee from the trade rule you gave. Stalled ones get a note asking the technician for an update through update_service_issue. The agent never sets Resolved on its own, because a closed status tells Rent Manager the work is done and can trigger a closing notification.

4. 04

   Update tenants who have waited longest

   For issues tied to a tenant and older than your second threshold, get_history shows whether someone already wrote to them this week. Tenants with no recent contact get a short send_text naming the issue and the next step.

5. 05

   Hand back what needs a human call

   Issues with no unit, a vague title, or an assignee who is no longer a user are listed for you, so the report ends with the decisions only you can make.

Open over 7 days: 9 issues at 3 properties
Unassigned: 2, assigned to Sam Ortiz (electrical) and Dana Ruiz (plumbing)
Still New after 10+ days: si_20801 Maple Court hallway light, note sent to Sam Ortiz
Past schedule: si_20744 8 Elm St water heater, scheduled 6 Oct, asked Sam for status
Recurring, left alone: 3 monthly filter changes
Tenants texted: Jordan Lee 4B (si_20712, 16 days)
Needs you: si_20655 Oak Terrace "check unit", no unit or details

• Rent Manager Service Manager sorts open issues into separately managed, customized lists, each one filtering out the issues you do not need to see.
• Rent Manager Task Automation can post recurring service issues without user intervention, so the open list mixes routine scheduled work with tenant requests.
• Technicians on rmAppSuite Pro change the service issue stage from their phone on the job, and the Tech View shows each technician their daily schedule.
• Rent Manager Automated Notifications can run on a schedule as well as on an event such as a service issue being closed.
• Report Batches in Rent Manager distribute reports to owners on a daily, weekly or monthly schedule.

update_service_issue and send_text ask for your OK by default. To run it weekly without you, switch confirmation off for those tools in your dashboard.

Sources: Rent Manager: maintenance and service issues · Rent Manager webinar: customizing service issue lists · Rent Manager: automate your operation (recurring service issues, Report Batches) · Rent Manager: tips and best practices (Automated Notifications)

curl https://cotlet.dev/api/v1/rent-manager/list_service_issues \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"older_than_days":7,"property_id":"p_12"}'

{
  "issues": [
    {
      "issue_id": "si_20744",
      "title": "Water heater not heating",
      "property": "Elm Street Duplexes",
      "unit": "8 Elm St",
      "status": "Work in Progress",
      "assigned_to": "Sam Ortiz",
      "created_at": "2026-09-28T09:12:00-04:00"
    },
    {
      "issue_id": "si_20801",
      "title": "Hallway light out",
      "property": "Maple Court",
      "unit": "Common area",
      "status": "New",
      "assigned_to": null,
      "created_at": "2026-10-02T15:40:00-04:00"
    }
  ],
  "next_cursor": null
}

MCP: add https://cotlet.dev/mcp/v1 with the same key; the tool is rent-manager_list_service_issues. Example data.

• Text past-due Rent Manager tenants a personal rent reminder
• Create Rent Manager service issues from tenant texts and emails
• Rent Manager API and MCP server: every tool
• All use cases