Skip to content
Content SnareHelp centre

Reminder schedules

Quick answer

A reminder schedule is a set of rules for when Content Snare chases your client for answers and notifies the request owner. You pick a schedule for each request when you publish it. Editing a schedule changes every request already using it.

A reminder schedule is a set of rules that decides when Content Snare chases your client for their answers and when it notifies the request owner. Each timed rule sets a day, a time and which message goes out, so a client who has gone quiet is chased automatically instead of you having to remember. A schedule also includes notifications that go out when something happens rather than on a timer, and there's a section on those below. Open Reminders from the main menu and go to the Schedules tab to see the schedules on your account.

The two schedules you start with

Every account comes with two ready-made schedules. Default runs a full series of timed reminders, from the first email through to overdue notices. No automatic reminders sends the first email, along with the rejection and comment notices, but none of the timed reminders, so the client hears from you once and after that only when you act on their answers.

You can't remove either of these two, and you can't remove any schedule that a request or a recurring request is still using. Everything else you create is yours to edit or delete.

Edit a schedule

You change how often Content Snare chases a client by editing a schedule's rules. One schedule can be attached to many requests at once, so a change here reaches every request already using that schedule, not only the ones you send next. If you only want to try something out, copy the schedule first. Open the menu beside its name on the Schedules tab, choose Duplicate, then edit the copy.

Your changes apply from the next send cycle. A reminder already prepared for the cycle about to run can still go out with the old wording.

The timed rules sit under Scheduled Communications. Take the default's rule for a client who hasn't started:

  • when it sends: 5 days after you publish the request
  • the condition: only if the client hasn't completed any fields yet
  • the message it sends: the "Not Started" email
  • who it goes to: the client
  • the time of day: 9am
A timed rule in the Default schedule that sends the Not Started email to the client 5 days after publishing, at 9am

Change any part of the row to suit. The "when" dropdown offers four triggers:

  • a set number of days after you publish the request
  • a number of days before the due date
  • a number of days after the due date passes
  • a number of days after the client completes every field

A rule can go to the request owner instead of the client. That's useful when you want to know the due date is close and the client hasn't finished.

Add another rule with Add New Rule, or open a rule's own menu to delete it. When you're done, click Save in the top corner.

Reminders arrive in the recipient's time zone

Each reminder goes out at the time set on the rule, but in the recipient's local time zone, not yours. A 9am reminder reaches your client at 9am where they are, from the time zone set on the client. A reminder to a teammate uses theirs. To change when a client's reminders arrive, update their time zone. When no time zone is set anywhere, the reminder uses your company's time zone, and UTC if even that is missing.

Event notifications

Not every message in a schedule runs on a timer. Below the reminder rules is a second list, Event Notifications. These go out when something happens on the request, not at a set time. The first email goes out when you publish, and a rejection notice goes out when you reject an answer. Since they're triggered by an action, there's no day or time to set on them.

You can delete an event you don't want, or add one with Add New Event.

Four of these events can stop themselves firing over and over, so one busy request doesn't fill your inbox with near-identical emails. Each has its own checkbox, worded for that event, such as Suppress further field completion notifications until a team member approves or rejects a field. All four behave the same way. The first email goes out, then the rest wait.

The ones for a submitted answer and a resubmitted one wait on your team in the same way. The fourth is the odd one out. It's the rejection notice that goes to your client rather than to you, and it waits until that client completes a field.

Comment notifications don't work this way. They're capped at one a day, however many come in.

Create your own schedule

You can build a schedule from scratch when neither built-in schedule fits. On the Schedules tab, click New schedule and give it a name and, if you want, a short description. From there you fill in the same two lists you edit on any schedule, the timed reminders and the event notifications, adding as many of each as you need. Click Save and it joins the others on the Schedules tab. You can keep as many schedules as your different types of work call for.

Assign a schedule to a request

You pick which schedule a request uses when you publish it, from the schedule dropdown in Publish Settings, the last step before a request goes out. Two of the options there look similar but behave differently. No automatic reminders still sends that first email. "Don't send any messages to my client" stops Content Snare's reminders and notification emails to that client for the request, including the request link, so you'll need to send them the link yourself. Comment notifications and any manually triggered emails will still go out.

Once a request is live, its scheduled reminders show on the calendar view. To change or stop reminders on a request you've already sent, see pause or stop reminders.