For everyone
Good habits
Name the owner, say when, keep one ask per message: how to write asks Pondros tracks cleanly.
Pondros tracks what people actually say. A few habits make what it tracks cleaner.
Tag the person
An @mention is unambiguous; a first name isn’t. Tagged asks become tasks, while untagged names only become suggestions.
@Rob can you send the revised scope? ✓ Rob can you send the revised scope? only suggested
Say when
A due date is what switches on follow-ups. “By Friday”, “tomorrow” and “end of month” all work. A task with no date is tracked but never chased.
One ask per message
Three asks in one message can become one muddled task. Put each on its own line, or ask Pondros to split them:
@Pondros make these three tasks: Maya the deck by Fri, Rob the scope by Tue, Priya the Q3 numbers by Thu
Ask where the work lives
Tasks are filed under the channel they were asked in. Asking in the client’s channel puts the task in the client’s project.
Reply to check-ins
Any reply, even “still on it”, resets the escalation count and keeps the requester informed. Silence is what escalates. See When it goes quiet.
Tell it how you work
Standing rules save correcting it every time:
@Pondros from now on, file anything about invoices under Finance