Why you don’t need to create an @Call Context
Here is a tip that may not be so obvious. The whole idea behind contexts in the GTD is being in the right place at the right time to take the right action. For example, having a list of items you would like to pick up at the hardware store with you at the same time you are at the hardware store works. This GTD Tip applies this same logic to the placement of your @Call Context. Don’t create a context for calls in your GTD Application when the general wisdom would have you keep all your contexts together. What I recommend is creating a “Category” called @Calls in Contacts. Your contacts are there anyway as well as all the info you need to make the call. Simply place the contacts you need to call in this category. In fact, with Palm’s Quick Connect feature you can initiate the call on your Bluetooth enabled cellphone wirelessly and talking within seconds. Click here for more info. This tip places your @Calls Context in the right “Category.” While your at it here is a Bonus tip - create an “@Waiting for” category there too because when you’ve been “waiting for” longer than is expected you may just want to give those people a call.
Just thought you should know. This may resolve what has been unresolved to 700P Verizon customers. 
