Im being a bit devils advocate here - but the one caveat for me doing it that way is that when I do the weekly review I tend to mix up how I think I should contact people according to how long since I last spoke to them. See them every day? Email them. Not seen them for 6 weeks? Give them a call and shmooze them a little. I tend to only be able to get that thinking out at the weekly review, rather than the daily decision making.
Originally Posted by PeterW
I did this about a year ago, much as PeterW described, and find it works well for me. I realized that -- at least in the context of my work -- everyone's communication style has been evolving over the last five years or so. I rarely just call anyone as an initiating communications step. Many people that I've had long term phone relationships have gradually migrated to email, and this has become a more effective medium to communicate with them. Sometimes I can use email to schedule a phone call (works much better for me than playing phone tag) and once scheduled, that call goes on my calendar, so it doesn't need to be on a separate @Calls list.
I don't find the overhead required to decide how to contact someone onerous in the least; it's much more important for me to have all those contacts corraled together in one place. In fact, it seems a less useful exercise for me, to decide in advance how I want to communicate with someone, since situations are so fluid and may require a different communications medium between when the name goes on the list and when I act on it. I used to waste an inordinate amount of time trying to decide in advance whether to put a name on @Call or @Email, and then realized that it was not a useful step for me, and that the reason I struggled with that decision was that it simply was arbitrary, and not necessary, in my situation. Of course, YMMV.
One alternative would be to use your @agendas for this purpose. @agendas is a a very useful list, especially for those times when you might call, but could email, etc. As one poster pointed out, whether a call or email is best will change over time.
My @agendas list is the newest context for me to implement (very well, anyway). I do not have as many meetings as I have several items to bring up to the same person.
My @calls list is actually called my @phone list. I, like the OP, have a smartphone, and so the @phone context includes all updates, applications, organization, as well as telephone calls to make. As the @phone relates to calls, the actions usually contain fewer topics to discuss with people I do not deal with regularly.
@anywhere could work IF you really have your phone with you as often as you have on clothing. Remember the purpose of the contexts is to separate out items that require special equipment. I don't have a context list for things that require pen and paper because I always carry them. My phone occasionally gets set down.
Note that, for a person who relies on his/her phone for GTD, @anywhere could especially apply, because that person wouldn't know even what was on the @anywhere list without the phone.