>>How would the police who pulled your spouse from a car wreck know your PIN? You need to let organizations know a PIN. Later on, automated channels and PINs c

>>How would the police who pulled your spouse from a car wreck know your PIN? You need to let organizations know a PIN. Later on, automated channels and PINs can be created that each user opts into--like whitelists for public services (police, government etc.). Those could work with automatic notifications/updates for those organizations. You could also opt in to whitelist certain numbers on signup (like public services) once SHAKEN/STIR is ready (so that commonly whitelisted numbers aren't spoofed). I understand I'm describing a long term solution and I'm being very idealistic here. >>How would someone store your PIN in a contacts list that didn't include a field for a PIN? PINs are for organizations and groups to store. Contacts are to be used more in scenarios with whitelisting. You may be able to store contacts with PINs that you can dial, but I haven't had time to play around with the pause functionality in Apple contacts yet. I think organizations will easily store PIN info. >>This system places obstacles in the way of someone who may need to reach you urgently. Is that a good tradeoff to make for not receiving spam calls? More than half of all calls are spam calls. In my mind it is. I used to get 5-10 spam calls every day. But, that's part of the reason I'm running this test :)