Chasing somebody who has not signed

A request is chased only if it has a due date. Without one, nobody is emailed a reminder however this workspace is set — a firm that did not set a deadline has not asked us to chase their client.

Choosing the schedule

Under Settings, Reminders, you choose two things: how often somebody is chased while the due date is still ahead, and how often once it is late. Both are named choices rather than a number of days, so you can tell a client exactly why they heard from you.

Before the date, chasing is a courtesy — too much of it gets your mail filtered. Once it is late the request has a real problem, so that setting is usually the tighter of the two.

You can also have new requests start with a due date already filled in, a set number of days from the day they are created. It is off unless you turn it on, because a due date is the thing that turns chasing on at all.

Chasing always stops

Whatever you choose, a request is chased at most five times and then stops. That limit is not a setting, and reaching it writes an entry on the request — so "why did they stop hearing from us" has an answer that is not "the job must have died".

What a change reaches

The schedule is read when a request goes out. Changing it re-paces what you send from then on; a request already out keeps the pace it was sent with.

One thing we cannot see

If an address is dead, the rejection goes to whoever runs your mail server rather than to us. Reminders will keep being sent and the silence will look like your client ignoring you. If a request goes quiet, check with them directly.