| JOB REF/ REASON FOR USE: | Customers report bugs/RFC's/Wishlist items. These get logged in BugNet and prioritised. High priority items and requests which support our roadmap for that product get delivered. The 'You Said, We Did' is a process for closing that customer feedback loop. It is a way of us reporting back to a customer that we listened and we did the thing they requested. The intention is to drive update of the new version and drive customer satisfaction. It is an activity completed by the support team shortly after a software update is released. Generally the support team will compile a list of the issues/changes in a release and who requested them. They then email those users. It is important to log this outbound contact in Pivotal so that other teams (mostly Success and Sales) have visibility of this good work. | |||||||||||
| ITEM/STAGE | DETAILS: | ||||||
| 1 | Compile a list of the customer requests delivered as part of the software update. The list may come from TFS. You are looking to find the corresponding BugNet number for each item. You are only concerned with customer requests. Internal developing bugs and so on are not relevant here. | ||||||
| 2 | Look up each item in BugNet and compile a list of email addresses for each customer who requested it. It could be a bug that several customers have reported. We want to email those customers to tell them the bug has been fixed in the new version. | ||||||
| 3 | While you are in BugNet please check each record that has been delivered has been marked as 'confirmed fixed' This is something which should be done by QA but please make sure I has been done. | ||||||
| 4 | Send them all an email. There is a template for this called "You Said We Did template.oft" Note: 1. Often the record in BugNet is not written in language we would use with a customer. Please change this so it is customer friendly. 2. We do not want to send a customer more than one email. If they happen to have reported more than one issue which has been fixed in the release, please combine the issues into one email for that person. 3. Send an email to all of the users. If you are sending 1 email to several users please use the BCC field so they do not know who also got the email. | ||||||
| 5 | Send the emails. | ||||||
| 6 | For every user who was contacted please leave a record in Pivotal. | ||||||
| 7 | Finally send the product manager for that product an email of how many customer issues were fixed in the release and how many users have been contacted. | ||||||