Plan the van, not just the diary. Describe your service area and your job types, and Taskade Genesis builds a scheduling app that takes visit requests with an address and access notes, groups them by area and day, and sends each crew a clean run list for the morning.
The Broker Calendar is a live Taskade Genesis app on this page. It schedules visits across a working week, which is the bones of this build; press "Use this app" to clone it in about ten seconds, then add the job types, the crew assignment, and the route grouping described below.
Field service scheduling is not really a calendar problem, it is a geography problem wearing a calendar costume. Two jobs an hour apart are cheap on Tuesday and expensive on Wednesday, and the difference is entirely about what else is nearby. Grouping requests by area before you commit to times is the whole trick, and it is why this build starts with a Board of postcodes and days rather than an empty week.
What the build gives you: a request per visit with address, job type, estimated duration, access notes, and a preferred window. Plus an area grouping so nearby jobs cluster, a day plan per crew with total time and travel gaps visible, a run list sent to the crew each morning, and an on-the-way message to the customer.
The same jobs render across the layouts you need:
- Board view to group unscheduled visits by area, then drag them onto a day
- Calendar view for the committed week per crew
- Table view for job duration, address, and access notes as a run sheet
- Plus List, Mind Map, Gantt, and Org Chart across the rest of the 7 project views
Automations move the day along. The Form Submitted trigger captures a request, an AI categorize step tags the area from the address, a scheduled trigger sends each crew their run list at 7am, and a task due trigger sends the customer an on-the-way text when the previous job is marked complete. Across 100+ bidirectional integrations, forms and Gmail pull requests in while SMS, email, and Slack push run lists and arrival notices out. Automations run on paid plans; the Free plan includes 10 flow runs in total.
The AI agents in the app carry 34 built-in tools including web search, persistent memory, and file analysis. The Dispatch agent reads new requests, estimates the duration from the job description, spots the jobs that need a second person, and drafts the customer message when a day is running late.
Estimated duration is the field that decides whether the whole system works. Guess it too low and every day runs late, which no reminder can fix. The practical approach is to record actual duration alongside the estimate for a month, then let the agent tell you which job types you consistently underestimate. Most field businesses find one or two offenders, correct them, and get their afternoons back.
Clone the app, invite your crews, and the job history is yours. Every address, every access note, every part fitted, kept where the next visit can use it.
Learn categorization in Learn, recurring runs in Learn, and board layouts in Learn. Browse live builds in the Community Gallery. Pair this with the deposit collection flow for call-out fees, and the final balance collection prompt for the money owed once the job is done.
Frequently Asked Questions
Does it calculate routes and drive times?
It groups jobs by the area you define and shows you the day's load, which is the part that actually saves money. It does not compute turn-by-turn routing. Most operators find that clustering by postcode plus a human eye beats a routing engine that does not know which customer needs the early slot.
Can we give customers a time window instead of a time?
Yes, and you should. A window field on the booking is more honest than a precise time you cannot hold, and the on-the-way message closes the gap on the day itself.
How do access notes reach the crew?
They live on the job record and appear in the run list the crew receives each morning. Gate codes, dog in the garden, park round the back. This is the single most appreciated field in any field service app.
Can a job need two people?
Yes. Mark the crew size on the job and the day plan counts it against the people available. The agent can flag jobs whose description suggests they were underestimated.
What if a job overruns?
Mark it and the rest of the day shifts. The automation can send an apology and a revised window to the affected customers, which turns the worst part of the day into a two-minute task.
Can we take payment on site?
Send a hosted Stripe Checkout link when the job is marked complete, so the customer pays from their phone before the van leaves. The final balance prompt covers this in full.
Does the customer get to pick their day?
They propose a preferred window on the request, and you confirm once you can see what else is in that area. That is the request-and-confirm shape, and for field service it is the only shape that survives contact with reality.
Can we see the history for an address?
Yes. Past visits, notes, and parts stay attached to the address and the customer, so a repeat call-out starts with everything the last engineer learned.
