SERVPRO franchise group · Requests
Twelve offices, one place to ask for help.
Requests from 12 offices go into one queue. Each one gets triaged, handed to someone, and flagged if it sits too long.
- Client
- A SERVPRO franchise group (freelance)
- Role
- Freelance Full Stack Developer & AI Automation Developer
- Timeline
- May 2026 to now
- Stack
- React, Supabase, Google BigQuery
Request Center overview
Request details and dollar figures are blurred.
The problem
Requests came in by chat, email and phone. Nobody owned them, and there was no way to tell what was stuck.
What I set up and built
Asking with context
People pick a request type, fill in a short form and attach screenshots or exports, so whoever picks it up has what they need the first time.
Triage and owners
A Needs Triage queue and an Assigned To Me view. Counters show what’s open, what has no owner, what’s been open more than five days, and how much money is under review.
A paper trail
Every status change and comment is logged and emailed. If the fix isn’t right, the person who asked can reopen it.
Moved in and connected
I moved the old requests in with standard request numbers, checked every form’s input, and pulled offices and people from the employee directory.
Handover and adoption
- One queue instead of three channels.
- Anything open for more than five days gets flagged.
- I built the first version and coordinated the technical handover for the next phase.
Try it
A small working copy, with made-up data.
Requests
Send a request and see who picks it up.
Each request goes to the right person based on what it’s about. Urgent ones, or ones left open for five days, go to a manager. Request Center does this for 12 SERVPRO offices.
New 0
Assigned 1
Needs attention 0
Made-up offices and requests · nothing is sent