Makes perfect sense, good suggestion.

Really you can get past it without typing by... not typing.

That field isn't required unless you actually know when you want it to reopen. Otherwise it will auto-reopen when the customer replies regardless.

This is mostly useful when you have something that can only be done on a certain day, such as canceling an account. In that instance it's unavoidable to type "Next Friday" or "June 30 2007". You aren't going to have things landing on the same day often enough for it to memorize your answers. And +1d, +5d are pretty useless except I'd imagine for sales follow-ups.

With the latter point in mind I'll think about it.

I think you've summarised it quite well - "generally" it probably doesn't help so much, but for any general follow-up (could be support too, not just sales - e.g. "has the change we made resolved your problem now that you've had a couple of days to test it") it would be absolutely fantastic!

My guess is that this would be really easy to implement?

Having looked at the existing functionality in the evaluation version of 4.x I think it's fine as it is - I'd prefer not to clutter the interface with links specifically for certain lengths of time (they'd almost certainly be the "wrong" choices - unless the user had the ability to select what they wanted... per queue or something).

@Damien Yeah, this would be incredibly simple to code. We could make the quick links relevant by reusing the options the worker entered manually the first time. The more an option is reused, the higher precedence it would have in the quick list (or you could sort it by last use, and bump old ones off the list after a max).

Consolidating requests about the "Next" area...

CHD-33 requests quick-links for setting when to resume

If watching / voting on CHD-33, please switch to CHD-288.