Closed Bug 1062306 Opened 10 years ago Closed 10 years ago

Do a better job of communicating and following up with partners about badges

Categories

(Webmaker Graveyard :: Badges, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: matt, Assigned: chrislarry33)

Details

(Whiteboard: [badges] [oct3])

* Beyond the technical piece, there's a customer service / account manager piece to this 

* Work with account managers + data entry. Instead of over-relying on things like claim codes, we can just get interim data (like spreadsheets) from partners and then enter it. 

* Claw: you suggested this as an area of focus. What's the best way to push forward with this one?
Assignee: nobody → chrislarry33
Status: NEW → ASSIGNED
Flags: needinfo?(michelle)
Whiteboard: [badges] [sep5] → [badges] [sep19]
Agree this should be part of the 1:1 follow-up with the MP account managers. 

Main badge we should focus on is the skill sharer one. 

What I've done with some groups is ask them to send me all their participants who qualify, and then I did the data entry. We could repeat for more partners. 

Flagging Amira if this is okay for her partner comms.
Flags: needinfo?(amira)
Flags: needinfo?(michelle)
Thanks Michelle! This is helpful.
We've been doing this already the past month and reached out to 50%+ of partners to get their list. Working with Misty and others to continue this by end of week (as well as including it in the wrap-up emails to partners)
Flags: needinfo?(amira)
* That's great. Sounds like nothing further is needed here -- 
just let us know if there's anything we can do on the production side to make this work easier.
Whiteboard: [badges] [sep19] → [badges] [oct3]
* Language and localization is also an issue here
* The [oct3] train has now left the station. So please update the whiteboard with [oct17], or whatever train you're now planning to put this on. Thanks!
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.