Welcome!  English (US) Language Switcher

How to handle "waiting for callback"?

soundsgood says:

Say my task is "Call Jim to discuss X." So, I call him, but I get voicemail, so I leave a message. I'd like the satisfaction of having this moved off of today's todo list, but since we didn't actually speak, the task is technically still incomplete.

I'd like to hear how other people handle this kind of thing with RTM. Also, do you have a different method, depending upon whether you intend to follow up that day vs. the next vs. the next week, etc.?

Obviously, one could mark the task complete, then create another one for the appropriate day or time, but that's really cumbersome (i.e., a lot of typing -- especially on a handheld device; even moreso if you have notes or other info within the task).

So, how do you folks handle this?

Thanks.

Posted at 2:44am on November 6, 2009

davidbwagner says:

Of course, the simplest thing to do is set a due date on this task to remind you to follow up. But suppose you don't want this task appearing in you task list until then.

What I do is, tag this task with the tag '-jim'. I have a smartlist called "Waiting" with this criterion: 'tagContains:-' . You can review this list periodically to see whom you need to ping.

Now go back to your "go-to" smartlist, the one you consult every day, and add 'and not tagContains:-' to the search criterion.

It's important that you don't use '-' in any of your non-waiting task tags for this to work.

Equivalently, you can have a list called waiting and move the task to that list; then add 'not list:Waiting' to your go-to list. But I don't use lists much because they don't show up (like tags do) in the line-item task views.

Does this make sense?

Posted 2 years ago

This topic has now been closed automatically due to a lack of responses in the past 90 days.