How to create a Zendesk ticket every month on a set day

By Jake Marsh · Updated

To create a Zendesk ticket every month, install Everytide, open it from the left navigation bar (the calendar icon) and choose New schedule. Under Repeats choose Monthly, every 1 month (3 for quarterly), then pick A day of the month, The last day, A weekday (2nd Tuesday...) or A business day (1st, last...). Set the time and time zone, fill in The ticket, check Next runs and click Save schedule.

Steps

  1. Open Everytide and choose New schedule. Give it a Schedule name, such as "Monthly access review".
  2. Choose Monthly under Repeats and set Every to 1 for monthly, 3 for quarterly, 6 for twice a year.
  3. Pick which day. See the table below.
  4. Set the time, Time zone and Starts date. Each schedule has its own time zone, and daylight saving is handled.
  5. Choose when it Ends: Never, On a date, or After a number of runs, such as 12.
  6. Fill in The ticket: Subject, Description (Internal note or Public reply), Requester, Group, Assignee, Type, Priority, Status, Form, Brand, Tags and Custom fields. For Type Task, set Due (days after the run).
  7. Check Next runs and Next ticket on the right. They show the coming dates and the ticket exactly as Zendesk will receive it.
  8. Click Save schedule, then Run now once to see a real ticket. Run now creates one extra ticket and leaves the schedule unchanged.

Which day of the month

OptionExampleNotes
A day of the monthThe 15thThe 29th to 31st fall on the last day of shorter months
The last dayThe 30th, 31st or 28th/29thAlways the month's final day
A weekday (2nd Tuesday...)The 2nd Tuesday, the last FridayFirst, Second, Third, Fourth or Last
A business day (1st, last...)The 1st business day, the last business dayBusiness days come from a Zendesk schedule or Monday to Friday

For a yearly ticket, choose Yearly and a Month, with the same day choices: "every year in June on the 1st business day at 09:00".

Common schedules

JobRepeatsDay
Monthly printer maintenanceMonthly, every 1A day of the month: 1st
Monthly report due at month endMonthly, every 1A business day: last
Patch review on the 2nd TuesdayMonthly, every 1A weekday: Second Tuesday
Timesheet reminderMonthly, every 1A weekday: Last Friday
Quarterly access reviewMonthly, every 3, starting in JanuaryA business day: 1st
Yearly vendor auditYearly, MarchA day of the month: 1st

Say which month the ticket is for

Put run placeholders in the subject, such as "Access review {{run.month}} {{run.year}}" or "{{run.quarter}} vendor audit". They are filled from the run's own date. See how to put the month or quarter in recurring ticket subjects.

Manage the schedule later

A schedule's page shows the next 10 runs and its Recent tickets, and offers Run now, Skip next run, Pause / Resume, Edit, Duplicate and Delete. Deleting a schedule leaves its tickets in Zendesk. Runs that fall while a schedule is paused are not created later.

What it costs

Everytide is $120 a month per Zendesk account on the Standard plan, with unlimited schedules and every feature. Billed monthly by Zendesk after a 14-day trial; Zendesk asks for a card at install. The Everytide documentation covers every option.

Everytide

Recurring tickets on a calendar: 2nd Tuesday, last business day, quarterly. No outside service. $120 a month per Zendesk account.


Questions

Will this month's ticket arrive if last month's is still open?

Yes. Everytide creates tickets on calendar dates, not when the previous one is solved. Both carry the schedule's tag, so a view shows which months are still outstanding.

What if the 1st falls on a weekend?

Use A business day (1st) instead of A day of the month, or set When a run lands on a closed day to move it to the next business day. See how to skip weekends and holidays.

Can I make the ticket a task with a due date?

Yes. Set Type to Task and Due (days after the run). The {{run.due_date}} placeholder prints that date.

How exact is the time?

Runs are created within a few minutes of their time while someone on your team has Zendesk open. If nobody is signed in, the run is created when the first agent signs in, unless you choose to skip missed runs.


More Everytide guides


More Zendesk guides