Trying to understand the Community Map

This one says ready to claim but then has assembling and what looks to be a completed chair.l

1 Like

Looks like a chair was built for them but the maker couldn’t get in touch with them to schedule delivery. I don’t see any admin messages so I am not sure if anyone on the admin team tried to get ahold of them or not.

1 Like

That’s @BentNotBrokn

This thread - Our First Build Finished

3 Likes

I tried for a couple weeks to communicate multiple ways (the platform, email, and text). I reached out to @MakeGoodScott on here regarding it and he spoke with her as well, I followed through with him the entire time. I did ask if I can unclaim the build if she didn’t reply. I sent a text on May 29 to schedule pick up but she has left my texts on read and has not replied to date. The build was delivered to another child but the pics still show on hers.

4 Likes

Yeah I see where Scott had activity on it. Sucks they aren’t responding! You built a great chair! Glad another child was able to put it to good use!

2 Likes

you can put that request into a hold status.

1 Like

Another question about the map. When we hit the can’t reach the family button what does that do? I usually prefer a family at least respond and confirm the colors/design and that way I know I won’t get it done and not be able to reach them. I have one claimed and tried reaching out twice with no response so I hit that button but I am not sure what happens next.

Usually best to send an admin message with the request number. @MakeGoodScott will have to say what that button is supposed to do and if its actually doing it.

"What the button does:
When you hit “Can’t reach family” it:

  1. Flags the request in the database with a timestamp
  2. Immediately emails all MakeGood super admins with your name, the family’s name/email/phone, the request number, and how many days since you claimed it — so they can step in and contact the family directly
  3. Shows a warning badge on the request card in the admin panel (with the date you flagged it)
  4. You can clear the flag yourself later if the family eventually responds

So right now it’s essentially an escalation signal to admins — it doesn’t automatically reassign or pause the build. Nothing else changes on the request itself"

Can you have it email the “regular” admins as well? You “super admins” are usually super busy handling everything else and we get nothing that tells us there is an issue.

How many builds does it take to get to admin or super admin status maybe you are not there yet. :laughing:

Builds don’t qualify that. Asking for more work does :rofl: :rofl: :rofl: But I love it! Cant get enough of this project!

1 Like
  1. It’s already where admins manage builds. When an admin opens the Requests tab, they’re in the mindset of reviewing active builds. A flagged family is a build problem — the maker is stuck — so it belongs right there alongside other request management.

  2. It’s urgent, so it needs to be impossible to miss. If it lives as a filter or a small badge on individual cards (which is all it is today), admins have to actively go looking for it. A dedicated alert panel pinned to the very top of the Requests section — highlighted in orange/amber — means it’s the first thing an admin sees when they open that tab.

  3. The actions admins need are request-level actions. From that panel, an admin needs to: see the family’s contact info, see how long it’s been since the maker flagged it, try contacting the family themselves, optionally reassign the maker, and clear the flag. All of those already exist in the Requests section — this panel just surfaces the right subset front and center.

  4. Keeps it simple. No new tab, no new section. Admins already know where requests live.


What the panel would show per row:

  • Request # and child’s name
  • Maker name + how long ago they flagged it
  • Family email and phone (click to copy/email)
  • A “Clear flag” button once resolved
1 Like

I’m glad, when you get tired of me, let me know…lol…:rofl:

2 Likes