Turn your existing customer list into a booked calendar before the season starts. The right customers get invited to the right seasonal service, in the order that fills your quiet weeks first, with a booking link that puts them straight onto the schedule.
A live Taskade Genesis app is embedded on this page. Run a campaign through its stages, look at how invitations become booked slots, then use it and you own a running copy in about ten seconds. You handle the finished campaign system rather than reading a plan for one.
That app is the Appointment Booking System, a live Taskade Genesis app you can click through and clone in about ten seconds. It is not a seasonal booking campaign out of the box, so treat it as the starting point: clone it, then carry its booking slots across and describe the rest of this build to Taskade Genesis.
The build is a real campaign record. It selects who to contact using rules you set: equipment type and age, last service date, contract status, and location, so you can fill one area at a time and cut drive time. Each contact carries the offer, the message, the send date, the response, and the booked slot. Capacity is part of the design, so the campaign invites in waves sized to what your crew can actually deliver rather than dumping four hundred emails and creating a queue you cannot serve.
Read the campaign in whichever layout suits:
- Calendar view to watch the target weeks fill up as bookings land
- Board view for contacts moving through selected, invited, responded, and booked
- Table view for the list with equipment age, last service, and response in columns
- List view to read the offer and message exactly as the customer receives it
- Plus Mind Map, Gantt, and Org Chart across the 7 project views
Automations run the waves. With Taskade automations, a schedule trigger releases each wave, a non-response gets one follow-up and then stops, a booking creates the job and confirms it, and reaching your capacity target pauses further invitations. Across 100+ bidirectional integrations, Gmail and booking forms pull responses in while Slack pushes the daily booking count to whoever is watching the calendar. See scheduled automations and the forms trigger.
The AI agents inside carry 34 built-in tools including persistent memory, web search, file analysis, custom slash commands, and multi-agent collaboration. The Campaign agent writes the invitation from that customer own history, referencing their specific equipment and its last service date, which converts far better than a generic seasonal blast.
Use the app, invite your office, and the lists, the messages, and the booking history are yours.
Explore live campaign apps in the Community Gallery, start a build at Taskade Genesis, or read the booking system guide. Equipment data comes from the site equipment history map, and booked visits join preventive maintenance scheduling.
Your existing customer list is the cheapest demand you will ever have, and in most service businesses it is dramatically under-used. These are people who already trust you, whose equipment you already know, and who need the service anyway. The reason campaigns do not happen is not skepticism, it is that assembling the list, writing the messages, and handling the bookings is a week of work nobody has. When the list comes from your own service history and the bookings land straight on the calendar, running a campaign becomes an afternoon decision rather than a project.
Frequently Asked Questions
How does it choose who to contact first?
By your rules, which usually combine equipment age, time since last service, contract status, and location. Grouping by area matters more than most operators expect, because a full day in one neighborhood is worth more than a scattered day across the county.
Will it flood us with more bookings than we can handle?
No, because capacity is built into the design. Invitations release in waves sized to your available slots, and the campaign pauses when the target weeks fill. That protects both your crew and your reputation.
Can the message reference the customer own equipment?
Yes, and that is the point of running the campaign from your service history rather than a mailing list. Naming the unit and its last service date turns a generic offer into a relevant reminder.
How many follow-ups should we send?
One is usually right for a seasonal offer. The build sends a single follow-up to non-responders and then stops, because a third message costs goodwill for a very small number of extra bookings.
Can customers book themselves?
Yes. The invitation carries a booking link that creates the job directly, which removes the phone tag that kills most seasonal campaigns. Business plans and above support hosting that page on your own domain.
Does it track what the campaign was worth?
Yes. Bookings, completed visits, revenue, and any work found during those visits are all attributed to the campaign, so next season is planned on numbers rather than a feeling.
Can we run more than one campaign at a time?
Yes, and most operators do: a heating campaign and a cooling campaign, or a residential and a commercial version with different offers. The rules keep the lists from overlapping.
When should we start a seasonal campaign?
Earlier than feels natural, usually four to six weeks before the season turns. Once the weather changes you are competing with emergency demand for the same crew hours, and the slots you wanted to fill in advance are gone.
