Sub-Rental in Slack: Draft Vendor POs from Current RMS History

Sub-rentals are the quiet time sink inside a rental shop. Every time an order comes in for an item that is not on the shelf, somebody has to remember who the shop borrowed it from last time, pull up the old rate, confirm the dates, and type out a purchase order from a Word template. That tax falls on one or two coordinators, and it falls again on the vendor waiting for a clean request. With a Slack agent reading Current RMS, both of those steps collapse into a single thread.

Sub-rentals fall through the cracks

Current RMS knows what the shop has. It does not know where the shop goes when it does not have it. That information lives in a coordinator's email and one or two people's heads. When that coordinator is out, the next sub-rental takes longer, the vendor list shrinks to whoever Slack surfaces first, and the rate reverts to whatever the vendor feels like quoting.

• The last rate lives somewhere in a Gmail thread from six months ago
• The PO template is a Word doc that nobody keeps version-synced
• Vendor ranking (who actually ships on time) is tribal knowledge
• New coordinators spend their first month learning the shop's vendor map by hand

How the Slack agent works

1. A coordinator mentions the agent in Slack with the shortage: item, dates, quantity
2. Runbear checks Current RMS through MCP for past sub-rentals of the same item, ranks vendors by recency, rate, and reliability
3. The agent posts a draft purchase order in the thread, complete with item, dates, rate, and delivery notes, ready to confirm

For the team. The agent owns the lookup, the ranking, and the draft, so the coordinator only does the one thing that actually needs a human: confirm the vendor and send. For the vendor. The request lands as a complete purchase order, not a half-written Slack DM, so their side is a faster yes or no.

Setting it up

Add the agent to your rental ops Slack channel

Create the agent in Runbear, give it a Slack integration, and invite the bot into the channel your coordinators already use. The agent only responds when mentioned.

Connect Current RMS as an MCP server

Runbear talks to Current RMS over MCP, so the agent can read inventory, bookings, and past sub-rental records the same way a coordinator would in the web UI. The connection needs a Current RMS API token with read access to products, bookings, and opportunities.

Give the agent your purchase order template

Paste your existing PO template into the agent's instruction and tell the agent which fields it should fill from Current RMS. Keep the tone close to how your coordinator already writes to vendors, because the bot reads the last few exchanges on that thread and matches them.

Before and after

Before

For the team. The coordinator drops what they were doing, searches Gmail for the vendor, opens Current RMS in a second tab to confirm the dates, copies the Word PO template, and retypes the details. Twenty to thirty minutes per sub-rental, twice as long if the coordinator who owns that vendor is out.

For the vendor. They get a short Slack DM or a two-line email (hey got an Easyrig for the 4th?), have to write back asking for the exact dates and the PO, and wait another loop before they can block the stock.

After

For the team. A coordinator pastes the shortage into Slack, the draft PO lands in the thread in under a minute, and they confirm and send. New coordinators ship their first sub-rental on day one because the vendor history is in the bot, not in a senior's head.

For the vendor. A single message arrives with every field already filled: item, quantity, exact dates, agreed rate, delivery and return address. They can confirm in one reply.

Who it fits

• Film and video equipment rentals running Current RMS, Rentman, or a similar RMS
• Event production companies that sub out lighting or staging between shops
• AV rental teams that borrow from peer vendors during festival season
• B2B equipment resellers doing cross-shop fulfillment