Connection 01
Customer-requested windows
Let customers request from the supported availability offered for their rental setup.
Rental delivery scheduling
Rivet helps rental teams coordinate the delivery request with the customer, inventory, location, and operational steps behind it.
What connects
Connection 01
Let customers request from the supported availability offered for their rental setup.
Connection 02
Connect scheduling decisions to tenant locations, reservations, and the work already planned.
Connection 03
Keep inventory assignment, required evidence, agreements, and payment state visible before activation.
How it works
Each stage preserves the customer, rental, tenant, and operating context needed by the next one.
Define the locations and scheduling choices that match how the rental company fulfills work.
Present supported delivery options inside the Rental Setup path instead of coordinating through scattered messages.
See the requested timing beside inventory, agreement, payment, and other required steps.
Track the scheduled work, finish delivery tasks, and retain the event with the rental history.
Operational outcomes
01
The customer and team work from one supported request instead of proposing times across several channels.
02
Staff can consider readiness and capacity before treating a date as committed.
03
Scheduling becomes part of setup rather than a separate process the customer has to discover.
Questions
Rivet currently focuses on delivery requests, calendar coordination, capacity, locations, and readiness. It does not claim automated route optimization.
Yes. The rental company controls the capacity and availability used for supported delivery requests.
No. A request remains connected to the readiness workflow, and staff retains control of the operational decision.
Yes. Delivery requests can be included in the connected Rental Setup journey.
Keep exploring