Academic Integrity: tutoring, explanations, and feedback — we don’t complete graded work or submit on a student’s behalf.

You have spent a lot of time developing your application and released it to the

ID: 3888194 • Letter: Y

Question

You have spent a lot of time developing your application and released it to the field. Now you are beginning to get requests from users for updates, improvements, and complaints about what doesn't work.

1. How are you going to organize this influx of information so that everyone can be satisfied and a logical work sequence can be scheduled?

2. How will new releases be handled?

3. Give a concrete example of software the will perform this function or an example of how this was implemented in the real world.

Please give detail on the answers. Thank you!!!!

Explanation / Answer

1. Your customers can provide feedback about their support experience by rating their solved tickets. When you enable customer satisfaction ratings, by default, end-users receive an email 24 hours after the ticket has been set to solved that asks them to briefly evaluate their experience, The survey is designed to maximize the response rate by being quick and simple while also gathering the essential data: a positive or negative rating. Customers can also provide a comment if they want. Agents are not allowed to rate tickets, even if they are the ticket requester.In this way will show our product qulity and attract new users .End user satisfaction is important for every application. So if the end user satisfied they will provide reviews and comments regarding our product in blogs etc.. So in this will show the customer satisfation to other users .

2.Release early and often is what I do, and what we do where we work. We also blog about our updates whenever we make them. It's probably easier for you if you roll all your updates into one update at a time (for QA, having to rollback, etc) as best as you can. From a user perspective I don't think there's any problem with lots of updates. As long as they're not bad updates. I think there is a problem if you wait for an entire year or six months, and roll all your updates into one big release. That's what killed a project I used to work on (a popular feedreader you've probably heard of). People thought we were dead, and perception became reality. We got abandoned. So I'm all for firehose release schedules.

3.Social media sites such as Facebook and Twitter have evolved to become more than emergent platforms for marketing and advertising. Increasingly, they are also valid and important channels through which consumers solicit and receive customer service.You can take an example of Amazon etc.

Hire Me For All Your Tutoring Needs
Integrity-first tutoring: clear explanations, guidance, and feedback.
Drop an Email at
drjack9650@gmail.com
Chat Now And Get Quote