Signal review
Permit changes, idle assets, service history, and site activity collapse into one tighter decision queue.
CloseoutSignal
Secure access testing
Currently under development
Temporary site asset closeout that feels alive.
CloseoutSignal is being prepared for launch. Public sign in and sign up are paused while we finish secure access testing.
Keep the queue smaller
Start from the assets that changed, not the full route sheet.
Keep proof attached
Messages, replies, overrides, and exports stay tied to the site and asset record.
Keep dispatch cleaner
Only verified asset actions move forward to handoff and route creation.
Product
Temporary asset closeout without the usual queue noise.
CloseoutSignal is not routing software and it is not billing software. It is the verification layer that helps ops teams decide whether an asset should stay, move, stop service, or get picked up with a clean proof trail.
Built for the temporary site asset categories that create repeat pickup, service, off-rent, and proof handoff work.
Portable sanitation, Dumpsters, Temporary fencing, Generators, Light towers, Storage containers, Office trailers, Pumps
Workflow
Work the queue together instead of stitching together status guesses.
The product is built around one operating sequence: surface the signal, verify contact readiness, send the message, wait on the state change, and move the verified asset action into dispatch with the proof already attached.
SMS verification
Outreach happens from the same asset record with contact state, consent, and retry logic visible.
Verified handoff
Dispatch only sees assets that are confirmed for pickup, off-rent, service changes, or keep-on-site.
Surface the signal
Verify the response
Send clean handoff
Use as extension
Add the closeout layer without replacing the rest of your ops stack.
CloseoutSignal fits around the tools your team already uses. Routing stays routing. Billing stays billing. This product handles the signal, outreach, proof, and clean handoff between them.
Current tools stay in place
Before
Routing, billing, CSV imports, and webhooks continue to handle their own jobs.
CloseoutSignal
Asset signals, outreach state, reply history, and proof stay in one review layer.
After
Dispatch receives a verified action instead of another uncertain stop.
Workspace rules
Controls without clutter
Outreach
Require consent before SMS and keep reply, retry, and waiting state visible.
Review
Hold pickup, off-rent, or service-change tasks until the closeout is confirmed.
Fallback
When work happens outside the app, the operator can still record the outcome against the same site record.
Customize it to your needs
Tune the workflow to your own contact rules, service rules, and launch policy.
Teams can work in shadow mode, switch to live outreach, require consent before SMS, and hold back pickup, off-rent, or service-change tasks until the response actually confirms the closeout.
One workflow
Run the whole closeout flow from signal to proof in one place.
Review
Decide what is real
Approve the asset signal, fix the contact, or pause the alert before it creates route noise.
Waiting
Let the state settle
Once outreach is sent, the queue holds until the reply or retry window changes the asset state.
Ready
Hand off verified work
Confirmed pickups, off-rents, and service changes move into dispatch with the proof trail already attached.
Your closeout queue, wherever dispatch starts the day.
The redesign keeps the workflow readable on busy mornings, from the first asset signal to the final proof pack.
100% your site history
Proof is part of the workflow, not an export afterthought.
Operators can see why an asset entered the queue, what message was sent, what reply came back, and what exactly moved into dispatch. That history stays attached to the site record from start to finish.
Fits your current stack
Keep the tools you already trust.
CloseoutSignal is the closeout layer between site signals and the systems that already run the day.
Inputs
Permit signals, rental inventory, CSV imports, site records, and service context.
Handoff
Verified dispatch actions, billing context, webhooks, and audit-ready exports.
Rollout
Halifax is first. Toronto, Calgary, Brampton, Kitchener-Waterloo, Greater Sudbury, Victoria, Kingston, Prince George, and Hamilton are planned next.
Stack coordination
Work with your dispatch and ops stack without losing the closeout signal.
CloseoutSignal coordinates permit data, asset state, outreach, tasks, exports, and webhooks from one record so the operator is not forced to rebuild the story from four disconnected tools.
What operators keep visible
The product keeps the next action, the reply state, and the proof trail in view.
Reply state stays explicit
Waiting, no-response, wrong-contact, and confirmed states do not disappear into notes.
SMS context stays attached
The operator can see the outreach path from the same site record that created the signal.
Proof stays export-ready
The final audit story is already assembled because it never left the workflow.
CloseoutSignal is preparing for launch
Public access is paused while secure sign-in, tenant protection, support, and billing readiness are tested.