“Hey Siri, show my code”

When you’re using your phone to share contact information speed matters. You need to be able to get to the right screen on the app as quickly as you can. We know that. And our goal is to make you the fastest card-slinger in the West, and East, and North, and South. Heck, we want you to be the fastest card-slinger in the World.

So we’re pleased to announce a new feature for the HiHello app on iOS: “Hey Siri, show my code.” Yup, that’s the magic phrase (for now). Update to the latest version of the HiHello app on the App Store, and then hold up your phone and just say the magic phrase.

Here’s a quick video of just how easy this is:

Music Credits: “Something Elated” by Broke for Free (http://freemusicarchive.org/music/Broke_For_Free/Something_EP/Broke_For_Free_-_Something_EP_-_05_Something_Elated) is licensed under CC BY 3.0 (https://creativecommons.org/licenses/by/3.0/us/legalcode)

To choose which of your cards works with Siri, you can go to the Settings tab and click on the Set Siri Card setting to change which one of your cards gets used by Siri.

The activation phrase for the HiHello app is “Show my code.” You can say that once Siri is activated and listening. The “Hey Siri” based activation for Siri will only work if you’re previously setup your phone to allow “Hey Siri”. If you haven’t setup Hey Siri, you can activate Siri whichever way you like and just say “Show my code.”

So go ahead and give it a try. If you 💜 the Siri feature as much as we do, we’d love to hear from you. And even if you don’t, we’d love to know what you’d like to see improve. We welcome your feedback and are standing by at support@hihello.me. And of course, we have a lot more cool stuff coming your way soon!

N.B.: We were ready to ship this surprise feature to you almost two weeks ago and had it working flawlessly on all of our development phones/accounts. However, when we pushed the release to the App Store, for some reason Siri would not work! This is how we felt: 😒😟😤🤯. After many many days and nights of debugging our team finally concluded out that there wasn’t anything we were doing wrong, and it had to be an issue on Apple’s end. We worked with Apple’s Developer Support Team over several days to have this resolved (Thanks Ed!) .