[Tutorial] How To Turn Off Siri App Suggestions In IOS 11/12

[Tutorial] How To Turn Off Siri App Suggestions In IOS 11/12

Step 2. Choose Spotlight Search. Step 3. You will see Siri Suggestions. Toggle it to OFF position. Step 1. On your iOS 11/12 device, go to the home screen. Swipe from left to right or just pull the notification center down to enter the Spotlight Search/Widgets screen. Step 2. You should see your widgets including 鈥淪IRI APP SUGGETSIONS鈥? Scroll down until you see the 鈥淓dit鈥?button. Step 3. Locate Siri App Suggestions or other apps you want to turn off. Tap the read minus button and tap on Remove. Step 4. Tap on Done. Now you will see the Spotlight Search screen is clear. You can tap on the Edit button to add Siri App Suggestions or other apps to widgets again. After updating to iOS 11, or even the newest iOS 12, if Siri is not working well on your iPhone or iPad, please check How to Fix Siri Issues on iOS Devices. For those who lose notes, contacts, messages and more after iOS update, we offer you Three Ways to Get Back Lost Data on iOS. Member of iMobie team, an Apple fan as well as an anime lover. Like to share solutions on iOS and Android related problems.

The hypothetical email above, suggested by Chase Clemons from Support Ops, does this well. By explaining why he thinks the suggested feature would be useful for users, he is showing that he considered the suggestion from the customer鈥檚 point-of-view. Now, let鈥檚 dive in deeper into the two main situations: feature requests that you are not working on and those that you have already planned to do. In The Ultimate Guide to Communicating Product Feedback, we show you how to make a case for your customer鈥檚 great feature requests. As much as we love our customers and their suggestions, we know that we do not have the resources to work on all the requests. Even when we could, it might not be the wisest thing to do. So do we. But we don鈥檛 want a thousand features. That would be ugly. Innovation is not about saying yes to everything. However, nobody likes to be told 鈥淣o鈥?

Nobody likes to be rejected. So how do we say 鈥淣o鈥?and without angering them? Before replying 鈥淣o鈥?immediately, pause for a moment and think from your customer鈥檚 perspective. Why do they want that feature? Our co-founder Jamie wrote a great post about this where he explained how in the early years of Kayako we struggled with high volumes of customer feature requests. In many cases, we ended up directly implementing what the customer asked for, only to realize it wasn鈥檛 right for us, or even the customer! In one instance, a substantial feature request was implemented only to turn out that the functionality the customer wanted could be achieved by making a minor change to an existing feature in the platform. So we started using the 5 Whys principle to dig deeper into customer feedback. The 5 Whys means that by asking 鈥渨hy鈥?five times, you鈥檙e able to tease out the real root cause of the problem and make the changes needed to resolve the underlying issue for good.

Adii Pienaar, co-founder of WooThemes and now Receiptful, also wrote a great post on this topic. He suggested that startups should try and understand the end goal customers have when they request for a feature. He said that this not only allows you to learn from the customers but also engages the customers, lets them know that you are listening and communicates that you care about their wants and needs. As we talked about in politely rejecting customer requests, there鈥檚 some kind of 鈥測es鈥?most of the time. Your customers may not know your product as well as you. So they might not know the possible workarounds. When you understand the real need that they have, you will be able to offer them alternative ways of using your product. However, don鈥檛 create imaginative workarounds just to win a customer. Finally, if you really really have to say 鈥淣o鈥? be transparent and provide an honest explanation for why you are not going to work on the feature.

An honest explanation will help the customers understand your context and they might empathise with your situation. This might not be what the customer likes to hear, but putting in the effort to give a genuine explanation can help to build their trust in your company. It shows that you value them enough to explain how you will act on their feedback. What if you are already working on the feature? Tell them that the features are coming soon and they will be satisfied! Yes, they might be delighted that your team is already building the feature for them. However, they are still unable to use the feature now. The next question will pop up in their head - when can I use the feature? Similar to dealing with feature requests that you are not working on, honesty is key. At Buffer, they let customers know transparently where they are with the feature development - dreaming and discussing, customer research stage, building or testing.