Fieldworker Reschedule Assist: Automated Alternate Time Suggestions & Rebooking
Fieldworker Reschedule Assist is an automated rescheduling workflow in OctopusPro that helps prevent declined booking requests from turning into lost bookings. When a fieldworker cannot accept a booking request, they can select a structured decline reason and, when enabled by your settings, suggest one or more alternative availability windows directly from the Fieldworker App.
Those suggested times can then be used to quickly rebook the customer, either automatically through OctopusPro’s assignment engine or manually by a dispatcher. Instead of leaving the office team to call the customer, check calendars, contact fieldworkers, and coordinate a new appointment by hand, Fieldworker Reschedule Assist captures useful availability at the moment the fieldworker declines and turns it into a clear rescheduling path.
This feature works especially well alongside Dynamic Real-Time Fieldworker Availability, fieldworker working hours and availability, fieldworker calendar availability, fieldworker service assignment, fieldworker service areas, and OctopusPro’s job assignment and dispatch settings. Together, these tools help your business recover bookings faster, reduce scheduling gaps, improve customer communication, and keep admin, customer, and fieldworker calendars aligned.
Important note: Some screenshots in this guide use the label “Hero”. In OctopusPro, this label can be customised to match your business terminology. In this article, the standard term fieldworker is used.
What Fieldworker Reschedule Assist Is Used For
Fieldworker Reschedule Assist is designed for situations where a fieldworker receives a booking request but cannot accept the originally requested appointment time. Instead of simply declining the request, the fieldworker can provide alternative dates and time windows they are available for the job.
OctopusPro then uses those suggested availability windows to support two main workflows:
- Automatic rescheduling and assignment: The customer receives an email and/or SMS with a secure link to choose from suggested time slots. OctopusPro can then re-broadcast the booking request to eligible fieldworkers and assign it based on your automatic assignment rules.
- Manual dispatcher-controlled rescheduling: The suggested times appear inside the booking record, allowing an admin or dispatcher to review the options, apply a suitable time, notify the customer, and assign the job manually.
This gives your business a structured way to handle declined booking requests without losing control of the job, confusing the customer, or creating unnecessary back-and-forth communication.
Workflow Summary at a Glance
| Step | Who acts | What happens | Result |
|---|---|---|---|
| 1. Booking request sent | OctopusPro | The booking request is sent to one or more eligible fieldworkers. | Fieldworkers can accept or decline the request. |
| 2. Fieldworker declines | Fieldworker | The fieldworker selects a decline reason from the Fieldworker App. | The reason is recorded against the booking. |
| 3. Alternate times suggested | Fieldworker | If Fieldworker Reschedule Assist is enabled for that reason, the fieldworker adds one or more available time windows. | The booking now has practical rescheduling options. |
| 4. Customer or admin selects a time | Customer or dispatcher | Depending on your workflow, the customer self-selects a time or the dispatcher applies a suggested time manually. | The booking is moved toward a new appointment time. |
| 5. Job is assigned | OctopusPro or dispatcher | The job can be re-broadcast to eligible fieldworkers or manually assigned. | The appointment is confirmed according to your assignment rules. |
Key Terms Used in This Guide
| Term | Meaning |
|---|---|
| Declined booking request | A booking request that a fieldworker cannot accept for the original proposed appointment time. |
| Decline reason | The structured reason selected by the fieldworker when declining a booking request. |
| Suggested availability | One or more alternative date and time windows submitted by the fieldworker when declining. |
| Rescheduling | The process of moving the booking to another appointment time, either through customer self-service or admin action. |
| Re-broadcasting | Sending the updated booking request to eligible fieldworkers after a new time is selected. |
| Final assignment | The point where the booking is assigned to a fieldworker according to your automatic or manual assignment settings. |
Important Behaviour Notes
- Suggested availability is not always the final booking time: A customer or dispatcher may still need to choose, apply, or confirm a specific time depending on your workflow.
- Customer selection does not always mean instant assignment: In automatic workflows, OctopusPro can continue the assignment process. In manual workflows, a dispatcher may still need to review and assign the job.
- Assignment rules still apply: Fieldworker availability, assigned services, skills, service areas, travel radius, and your job assignment method should still be used to determine who can receive or accept the job.
- Not every decline reason should trigger rescheduling: Time-related reasons are usually suitable, while reasons such as missing licences, outside service area, or unclear job scope may require office review instead.
- This feature is a recovery workflow: It helps recover declined booking requests, but it should not replace accurate fieldworker working hours, blocked time, calendar availability, and service area settings.
Who This Feature Helps
| Role | How Fieldworker Reschedule Assist helps |
|---|---|
| Customers | Customers receive clear alternative appointment options instead of waiting for the office to call them back. |
| Fieldworkers | Fieldworkers can decline unsuitable job times professionally while still offering times they can attend. |
| Dispatchers | Dispatchers get suggested availability recorded inside the booking, reducing manual calls and calendar checks. |
| Managers | Managers can review decline reasons, fieldworker response patterns, and rescheduling outcomes to improve scheduling performance. |
Quick Navigation
- Key benefits
- Before you start
- When the workflow is triggered
- How the decline and suggestion workflow works
- Recommended decline reason setup
- How suggested times are filtered and assigned
- Automatic assignment workflow
- Manual assignment workflow
- What happens after the customer selects a time
- Fallback workflow when no suggestions are provided
- Recommended configuration by workflow
- Configuration steps
- Suggested template wording
- Testing checklist
- Practical examples
- Best-practice recommendations
- FAQs
Key Benefits
- Recover more declined bookings: A declined job request does not have to become a cancelled job. Fieldworkers can immediately suggest times that may work better for them and the customer.
- Reduce dispatcher workload: Your office team spends less time calling fieldworkers, checking calendars, collecting availability, and manually negotiating new appointment times.
- Improve customer experience: Customers receive clear rescheduling options by email or SMS instead of waiting for a phone call from the office.
- Increase fieldworker utilisation: Fieldworkers can offer available gaps in their schedule, helping your business fill more appointment windows and reduce idle time.
- Improve assignment accuracy: Rescheduled jobs can still respect service matching, fieldworker availability, service areas, travel radius, location, and your configured job assignment rules.
- Keep the booking visible: Declines, suggested times, customer actions, notifications, and final assignments are recorded in the booking history for audit and follow-up.
- Support both automated and manual dispatch models: Businesses that prefer automatic job assignment can automate the process, while businesses that require office approval can keep dispatchers in control.
- Reduce missed opportunities: The customer is given another path to book instead of being left with a failed or unaccepted booking request.
- Improve operational visibility: Managers can see whether declines are caused by time conflicts, service area issues, skill gaps, missing equipment, or poor availability management.
When This Feature Should Be Used
Fieldworker Reschedule Assist is useful when your business sends booking requests to fieldworkers and needs a structured process for handling declines caused by scheduling conflicts, service area limitations, missing tools, unavailable parts, personal emergencies, unclear job details, or other operational reasons.
Common use cases include:
- A fieldworker is unavailable at the requested time but can attend later in the day.
- A fieldworker has another job, personal appointment, emergency, or calendar conflict.
- A booking was sent to multiple fieldworkers, but none accepted the original appointment time.
- The job is urgent and the office wants to keep the customer engaged with alternative options.
- A dispatcher wants to review suggested availability before confirming a new appointment.
- A customer needs a new appointment time, and your team wants to use realistic fieldworker availability instead of manually checking each calendar.
- Your business uses mobile workforce teams that do not always keep their availability updated.
- Your office team wants to reduce manual phone calls after declined booking requests.
Before You Start
Before using Fieldworker Reschedule Assist, make sure the following areas are configured correctly:
- Job assignment method: Decide whether your business uses manual assignment, automatic assignment, or a combination of both depending on job type.
- Fieldworker permissions: Fieldworkers must be allowed to accept and decline booking requests.
- Decline booking request form: Your decline form should include clear reasons for declining a job request.
- Reschedule-enabled decline reasons: Enable Fieldworker Reschedule Assist only on the reasons where alternative time suggestions are useful.
- Working hours and availability: Keep fieldworker calendars, working hours, blocked times, and service areas up to date.
- Service and skill matching: Make sure fieldworkers are assigned to the services they can actually complete.
- Service areas and travel radius: Confirm that each fieldworker’s location and service area settings are accurate.
- Customer communication templates: Review the email and SMS templates used when notifying customers about suggested times or failed job acceptance.
- Booking assignment rules: Confirm that service matching, fieldworker skills, service areas, and travel radius settings match your dispatch process.
Useful setup references include Fieldworker Permissions & Access Control, Fieldworker Job Decline Reason Form, Fieldworker Availability Finder, Assign Services to Fieldworkers, and Fieldworker Service Areas.
When the Workflow Is Triggered
Fieldworker Reschedule Assist is triggered when all of the following conditions apply:
- A booking request has been sent to one or more fieldworkers.
- A fieldworker opens the request in the Fieldworker App.
- The fieldworker selects Decline.
- The fieldworker selects a decline reason that has Fieldworker Reschedule Assist enabled.
- The fieldworker submits one or more alternative availability windows.
If the selected decline reason does not have Fieldworker Reschedule Assist enabled, the decline can still be recorded, but the fieldworker may not be prompted to provide alternative times. This is useful when the reason for declining cannot be solved by offering another time, such as missing certification, unavailable equipment, or the job being outside the fieldworker’s service area.
How the Decline and Suggestion Workflow Works
1. The fieldworker receives a booking request
The fieldworker opens the booking request in the Fieldworker App and reviews the job details, schedule, location, service information, and any notes or requirements attached to the booking.
If the fieldworker can attend, they can accept the request as usual. If they cannot attend the requested time, they tap Decline.
2. The fieldworker selects a decline reason
After selecting Decline, the fieldworker is shown the Decline booking request form. This form can include structured decline reasons created by your admin team, such as:
- Requested time not suitable
- Address outside my service area
- I do not hold the required licence or certification
- Needed parts or equipment unavailable
- Safety concerns at the job site
- Scope or information unclear
- Customer not responding to confirmation calls or texts
- Personal emergency or illness
- Other reason
If the selected decline reason has Fieldworker Reschedule Assist enabled, OctopusPro prompts the fieldworker to suggest alternative availability before submitting the decline.
3. The fieldworker enters alternative availability
The fieldworker can add one or more available time windows. Each suggestion includes a date, an earliest available start time, and a latest available finish time. This allows the fieldworker to offer flexible windows instead of only one fixed appointment time.
| Fieldworker action | What it means | Why it matters |
|---|---|---|
| Select a date | The fieldworker chooses the service date they are available. | Each suggestion is tied to a specific appointment date. |
| Add a time interval | The fieldworker enters the earliest start time and latest finish time. | This creates a bookable availability window for the customer or dispatcher. |
| Add another interval | The fieldworker taps + Add new time interval. | Useful when the fieldworker has multiple gaps available on the same day. |
| Add another date | The fieldworker taps + Add new date. | Useful when the first suggested date may not suit the customer. |
| Send suggestions | The fieldworker submits the decline with suggested availability. | The booking now has rescheduling options instead of only a rejection. |
4. OctopusPro records the decline and suggestions
Once the fieldworker submits the form, OctopusPro records the decline reason, the suggested time windows, the fieldworker who submitted them, and the time the response was submitted. These details appear in the booking record and can be used for manual follow-up, customer communication, automatic rescheduling, and reporting.
Recommended Decline Reason Setup
Not every decline reason should trigger Fieldworker Reschedule Assist. For best results, enable the feature only on decline reasons where suggesting another time can realistically help recover the booking.
| Decline reason type | Recommended setup | Why |
|---|---|---|
| Requested time not suitable | Enable Fieldworker Reschedule Assist | The fieldworker may still be able to complete the job at another time. |
| Schedule clash or calendar conflict | Enable Fieldworker Reschedule Assist | The fieldworker can suggest gaps around their existing commitments. |
| Personal emergency or illness | Optional | Use this only if the fieldworker can realistically suggest another date. |
| Outside service area | Usually do not enable | A different time will not solve the location problem. |
| Required licence, skill, or certification not held | Do not enable | The fieldworker is not suitable for the job regardless of time. |
| Required tools, parts, or equipment unavailable | Optional | Enable only if the fieldworker can suggest a later time when the required items will be available. |
| Job scope or information unclear | Usually do not enable | The booking should be reviewed by the office before rescheduling. |
How Suggested Times Are Filtered and Assigned
Suggested availability should be used together with your existing booking and dispatch rules. This helps ensure customers are offered realistic options and that the booking is sent to fieldworkers who can actually complete the job.
| Rule or setting | Why it matters |
|---|---|
| Fieldworker working hours | Helps prevent bookings from being offered outside the fieldworker’s usual available hours. |
| Blocked time and calendar availability | Reduces the risk of double-booking fieldworkers who already have work, leave, or unavailable time recorded. |
| Assigned services | Ensures the booking is offered to fieldworkers who are assigned to the required service type. |
| Skills, licence, or certification requirements | Helps prevent jobs from being assigned to fieldworkers who cannot perform the work safely or legally. |
| Service area and travel radius | Helps make sure the fieldworker can attend the job location without unreasonable travel. |
| Job assignment method | Controls whether the workflow is handled automatically or requires dispatcher approval. |
For best results, review fieldworker working hours, calendar availability, assigned services, and service area settings before relying on the workflow for live bookings.
Automatic Assignment Workflow
Use Automatic Assignment when you want OctopusPro to handle as much of the rescheduling and re-dispatch process as possible. This is suitable for businesses that send booking requests to multiple eligible fieldworkers and allow the first suitable fieldworker to accept the job.
In this mode, when the job request timer expires and one or more fieldworkers have suggested alternative times, OctopusPro can notify the customer and guide them through a self-service rescheduling flow.
1. Customer receives an email and/or SMS with suggested times
The customer receives a message explaining that the original booking request was not accepted, but that alternative availability has been provided. The message includes a secure link the customer can use to view and select from the suggested times.
2. Customer opens the secure rescheduling link
The link opens a mini-calendar or available-time selection page showing the suggested availability windows. The customer can review the available options and choose the time that suits them best.
3. Customer chooses an exact appointment time
If the suggested availability is a window, the customer may be prompted to choose an exact start time inside that window. After selecting the time, they continue with the rescheduling process.
4. OctopusPro re-broadcasts the job request
OctopusPro can send the updated booking request to eligible fieldworkers based on your dispatch rules. Eligibility may include fieldworker availability, assigned services, required skills, service area, travel radius, location, and other configured assignment conditions.
5. First acceptance confirms the appointment
When a suitable fieldworker accepts the updated request, the booking can be assigned according to your automatic assignment settings. The customer, dispatcher, and fieldworker are then updated, and the booking record reflects the new appointment time and assignment status.
Setup path: Go to Settings > General Settings > Job Assignment & Dispatch, then choose Automatic assignment under your job assignment method.
Related guide: Job Assignment & Dispatch
Manual Assignment Workflow
Use Manual Assignment when your dispatch team needs to review suggested availability before confirming a new appointment time or assigning the job. This is suitable for businesses that handle complex routing, VIP customers, high-value jobs, multi-fieldworker jobs, or jobs that require office approval before confirmation.
1. Suggested availability appears in the booking record
After a fieldworker declines a booking and submits alternative availability, the suggested time windows appear in the booking record. Admin users can review the fieldworker’s decline reason and suggested availability before taking action.
2. Booking remains unassigned until an admin acts
The booking can remain unassigned or flagged for action until an admin applies a suggested time, contacts the customer, sends a reschedule message, or assigns the job manually.
3. Admin applies one of the suggested time windows
The dispatcher can click Apply beside a suggested availability window. OctopusPro opens the scheduling popup with the selected date and time range, allowing the admin to confirm or adjust the appointment details before saving.
4. Admin notifies the customer
After confirming the new appointment time, the admin can notify the customer by email and/or SMS. If required, the message can be edited before sending.
5. Admin sends updated job requests to fieldworkers
The dispatcher can send the rescheduled job request to all suitable fieldworkers or selected fieldworkers. This is useful when more than one fieldworker may be able to complete the job or when the office wants to confirm who can attend the updated appointment time.
6. Fieldworkers receive and respond to the updated request
Fieldworkers receive an in-app notification or push notification with the updated booking request. They can review the job details, route, schedule, and requirements before accepting or declining.
If the fieldworker accepts, the booking may move into an accepted or pending assignment state, depending on your job assignment configuration. The office can then complete the final assignment if required.
7. Office receives real-time response alerts
Every accept or decline response can create a notification for the office team. This helps dispatchers monitor which jobs still need action and which fieldworkers have responded.
8. Dispatcher completes the final assignment
The dispatcher can assign the booking from the booking screen or from the available fieldworkers panel. Once assigned, the booking status, fieldworker schedule, customer communication, and linked calendars can be updated according to your settings.
What Happens After the Customer Selects a Time
Once the customer selects one of the suggested time windows, OctopusPro continues the booking workflow according to your assignment settings.
| Stage | What happens | Who needs to act |
|---|---|---|
| Customer confirms a time | The selected time is recorded against the booking or used to start the rescheduling workflow. | Customer |
| Booking is checked against assignment rules | OctopusPro can consider availability, services, skills, service areas, travel radius, and your job assignment method. | OctopusPro |
| Job request is sent or re-broadcast | Eligible fieldworkers can receive the updated job request, depending on your configuration. | OctopusPro or dispatcher |
| Fieldworker accepts | The booking can move toward assignment or confirmation, depending on whether your workflow is automatic or manual. | Fieldworker |
| Booking is assigned | The customer, fieldworker, booking record, and linked calendars can be updated according to your settings. | OctopusPro or dispatcher |
This step is important because selecting a suggested time does not always mean the booking is instantly completed in every business workflow. In automatic workflows, OctopusPro can continue the assignment process with minimal admin involvement. In manual workflows, the dispatcher may still need to review the selected time, confirm the booking details, and assign the job to the appropriate fieldworker.
Fallback Workflow When No Suggestions Are Provided
Fieldworker Reschedule Assist should be supported by a fallback workflow for cases where no fieldworker accepts the original request, or where fieldworkers decline without providing alternative availability.
When no suggested availability is available, OctopusPro can still help move the booking forward by sending the customer a rescheduling link that allows them to choose from available appointment times based on your configured working hours, booking rules, and availability settings.
| Scenario | What OctopusPro does | Why it matters |
|---|---|---|
| No fieldworker accepts | The booking can be flagged as unassigned or action required. | Dispatchers can quickly identify jobs that still need attention. |
| No alternative times are suggested | The customer can receive a fallback reschedule email or SMS. | The customer still has a self-service path to choose a new time. |
| Customer selects a new time | OctopusPro can re-run the assignment workflow based on the new requested time. | The job can be re-broadcast to eligible fieldworkers instead of being abandoned. |
| Customer does not respond | The booking remains visible for dispatcher follow-up. | The office team can call, message, reschedule, or cancel based on business policy. |
For jobs that remain unassigned after the customer or fieldworker does not take action, dispatchers should monitor the Unassigned Tasks Manager so the booking can be followed up, reassigned, rescheduled, or cancelled according to your business process.
Automatic vs Manual Rescheduling: Which Mode Should You Use?
| Workflow mode | Best for | How it works | Office control |
|---|---|---|---|
| Automatic assignment | High-volume businesses that want faster self-service rescheduling. | The customer receives suggested times, selects a new slot, and OctopusPro can re-broadcast the job to eligible fieldworkers. | Lower manual effort; dispatchers monitor exceptions. |
| Manual assignment | Businesses that need dispatcher approval before confirming changes. | The admin reviews suggested availability, applies a slot, notifies the customer, and assigns the booking manually. | Higher control; more dispatcher involvement. |
| Fallback rescheduling | Cases where no fieldworker accepts or no suggested times are provided. | The customer can be sent a reschedule link to choose from available appointment times. | Dispatcher visibility remains important. |
Recommended Configuration by Workflow
| Business workflow | Recommended configuration | Notes |
|---|---|---|
| Mostly automatic dispatch | Use Automatic Assignment, enable reschedule suggestions on time-related decline reasons, and keep service/area/availability rules accurate. | Best when your team wants OctopusPro to recover bookings with minimal dispatcher involvement. |
| Dispatcher-controlled bookings | Use Manual Assignment and let admins review suggested availability before notifying the customer or assigning the job. | Best for high-value, complex, VIP, commercial, or multi-fieldworker jobs. |
| Mixed workflow | Use automatic assignment for standard jobs and manual review for selected services, locations, or booking types that require more control. | Best when some services are simple and repeatable, while others require dispatcher approval. |
| Fallback recovery | Use fallback reschedule messages and monitor unassigned bookings when no fieldworker accepts or no suggested availability is submitted. | Best for preventing declined or expired requests from being forgotten. |
Configuration Steps
1. Choose your job assignment method
Go to Settings > General Settings > Job Assignment & Dispatch and choose whether your business uses Manual assignment or Automatic assignment.
For more details, see Job Assignment & Dispatch.
2. Enable fieldworker accept and decline permissions
Go to Settings > General Settings > Fieldworker Permissions and make sure fieldworkers are allowed to accept and decline booking requests.
This permission is required because Fieldworker Reschedule Assist is triggered from the fieldworker’s decline workflow. If fieldworkers cannot decline requests, they cannot submit decline reasons or suggested availability through this process.
For more details, see Fieldworker Permissions & Access Control.
3. Open Forms & Checklists settings
Go to Settings > General Settings > Forms & Checklists. Find the form used for declining booking requests, then click Edit.
For more information about forms, see Forms & Checklists Setup.
4. Add or edit the decline reason field
The decline form should include a structured question such as Why are you declining this job request?. A multiple-choice field is usually best because it creates clean reporting data and lets you enable Fieldworker Reschedule Assist on specific options.
5. Create clear decline reason options
Add options that are specific, mutually exclusive, and easy for fieldworkers to choose quickly. Avoid vague options where possible because unclear decline data is harder to act on later.
Recommended decline reason examples include:
- Requested time not suitable
- Schedule conflict
- Outside my service area
- Required licence or certification not held
- Required tools or equipment unavailable
- Required parts or materials unavailable
- Safety concern at job site
- Job scope or information unclear
- Customer unreachable
- Personal emergency or illness
- Other reason
6. Enable Fieldworker Reschedule Assist on relevant decline reasons
Enable Fieldworker Reschedule Assist beside any decline reason that should require or prompt the fieldworker to provide alternative availability. This is usually most useful for time-related reasons, such as Requested time not suitable or Schedule conflict.
7. Make the field mandatory if needed
If you want every declined job request to include a reason, enable the Mandatory setting for the decline reason field. This improves visibility and helps managers understand why jobs are not being accepted.
8. Save and test the workflow
After saving the form, test the workflow from the Fieldworker App by sending a booking request to a test fieldworker, declining the request, selecting a reschedule-enabled reason, and submitting suggested availability.
9. Configure communication templates
Review the email and SMS templates used for rescheduling, declined booking requests, not accepted requests, and customer notifications. Clear templates help customers understand what happened, why they are receiving the message, and what action they need to take next.
Related template guides:
- Email Templates & Canned Responses
- SMS Templates
- Template Placeholders for Email, SMS & WhatsApp Templates
Suggested Template Wording
When notifying customers about alternative appointment times, keep the message clear, polite, and action-focused. The customer should immediately understand that the original requested time was not accepted, alternative times are available, and they need to choose a new time using the link.
Example customer email/SMS wording:
Hi {customer_first_name}, unfortunately your original booking request for {booking_number} at {original_booking_time} could not be accepted. We have alternative appointment times available. Please use the link below to choose a new time that works for you: {reschedule_link}
Recommended wording tips:
- Do not blame the customer or fieldworker.
- Clearly state that the original time was not accepted.
- Explain that alternative times are available.
- Include one clear call to action.
- Use template placeholders so the booking number, date, time, customer name, and rescheduling link are automatically inserted.
- Keep the subject line specific, such as Choose a New Appointment Time for Booking {booking_number}.
What Information Is Recorded?
Fieldworker Reschedule Assist creates a useful audit trail for operational visibility. Depending on your configuration, OctopusPro can record:
- The original booking request time
- The fieldworker who declined the request
- The selected decline reason
- Any comments submitted by the fieldworker
- The suggested availability dates and time windows
- Customer email and SMS notifications sent
- Customer link clicks and selected reschedule time
- Fieldworker accept or decline responses after re-broadcast
- The final assigned fieldworker
- Booking status changes and assignment changes
This information helps managers identify scheduling problems, coverage gaps, common decline reasons, fieldworker responsiveness, and customer rescheduling patterns.
For more information, see Booking History & Audit Log.
Testing Checklist Before Going Live
- Send a test booking request to a test fieldworker.
- Decline the request from the Fieldworker App.
- Select a decline reason that has Fieldworker Reschedule Assist enabled.
- Add more than one suggested availability window.
- Check that the suggested times appear correctly in the booking record.
- Send the customer notification email and SMS using your configured templates.
- Open the customer rescheduling link and confirm that the suggested times are displayed clearly.
- Select a new time as the customer and check how the booking updates.
- Confirm that eligible fieldworkers receive the updated booking request.
- Accept the updated request as a fieldworker and confirm the final booking status.
- Check that the booking history records the decline, suggestion, notification, customer action, and assignment.
- Test the fallback workflow where no fieldworker suggests availability.
- Test the manual workflow and automatic workflow separately if your business uses both.
Practical Examples
Example 1: Fieldworker has a schedule clash
A fieldworker receives a booking request for 9:00 AM but already has another commitment. They decline the request, choose Requested time not suitable, and suggest 2:00 PM–4:00 PM on the same day. The customer receives the alternative option and chooses a new start time inside that window.
Example 2: No one accepts the original booking request
A booking request is sent to multiple fieldworkers, but none accept before the response timer expires. One fieldworker has suggested an alternative time. OctopusPro can send that suggested time to the customer and, once selected, re-broadcast the updated request to eligible fieldworkers.
Example 3: Dispatcher wants control before confirming
A high-value commercial job requires office approval before the appointment time is changed. The fieldworker suggests alternative availability, but the booking remains unassigned until the dispatcher reviews the suggestion, confirms it with the customer, and manually assigns the job.
Example 4: Fieldworker is outside the service area
A fieldworker declines because the job is outside their preferred service area. Since this reason may not require alternative time suggestions, your settings can record the reason without launching the availability wizard. Dispatch can then adjust service areas, widen the fieldworker pool, or send the request to a more suitable fieldworker.
Example 5: Customer needs flexibility
A customer cannot attend the original time, and the office needs to offer realistic alternatives. The dispatcher can use suggested fieldworker availability to offer the customer appointment times that are more likely to be accepted and fulfilled.
Example 6: A fieldworker can do the job, but only on another day
A fieldworker receives a request for Monday but is only available on Wednesday or Thursday. They decline the original request and suggest both days. The customer can choose the better option, and the job can continue through the normal assignment workflow.
Best-Practice Recommendations
- Use clear decline reasons: Keep options specific enough to support reporting. For example, separate Required tools unavailable from Required licence not held.
- Enable Reschedule Assist only where it makes sense: Use it for time-related reasons, not necessarily for every decline reason.
- Make decline reasons mandatory: This improves visibility and helps managers understand why jobs are not being accepted.
- Encourage multiple suggested windows: More options increase the chance that the customer can choose a suitable time.
- Review booking assignment settings: Make sure your automatic or manual assignment workflow matches how your dispatch team actually operates.
- Keep customer messages simple: Tell the customer what happened, what their options are, and what they need to do next.
- Monitor recurring decline patterns: If certain fieldworkers often decline because of distance, availability, skills, or equipment, review service areas, working hours, training, or job matching rules.
- Test the full customer journey: Always test the fieldworker app, admin screen, email, SMS, customer link, rescheduling page, and final booking assignment before relying on the workflow in production.
- Keep fieldworker calendars updated: Fieldworker Reschedule Assist is a safety net, but it should not replace accurate working hours, blocked time, and real-time availability management.
- Review templates regularly: Make sure customer messages still match your business process, tone, and cancellation/rescheduling policy.
Common Setup Mistakes to Avoid
- Using vague decline reasons: Options like “Can’t do it” do not help dispatchers understand the problem or improve future job matching.
- Enabling Reschedule Assist on every reason: Some reasons, such as missing licence or outside service area, may not be solved by suggesting another time.
- Forgetting to test customer links: Always test the email/SMS link from the customer’s perspective before using the workflow live.
- Not reviewing assignment rules: If service areas, fieldworker services, or availability settings are outdated, the re-broadcast workflow may not reach the right fieldworkers.
- Using unclear customer messages: Customers should know exactly why they received the message and what they need to do next.
- Relying only on manual follow-up: The feature works best when suggested times are captured immediately, while the fieldworker still has the booking details in front of them.
- Ignoring repeated decline patterns: Frequent declines for the same reason may indicate a deeper issue with service areas, pricing, skills, calendar accuracy, or booking rules.
Related Settings and Help Guides
- Job Assignment & Dispatch
- Dynamic Real-Time Fieldworker Availability Scheduling
- Fieldworker Working Hours & Availability
- Fieldworker Calendar & Availability
- Fieldworker Availability Finder
- Assign Services to Fieldworkers
- Fieldworker Service Areas & Locations
- Fieldworker Permissions & Access Control
- Fieldworker Job Decline Reason Form
- Unassigned Tasks Manager
- Forms & Checklists Setup
- Email Templates & Canned Responses
- SMS Templates
- Template Placeholders
- Booking History & Audit Log
FAQs
Q: What is Fieldworker Reschedule Assist?
A: Fieldworker Reschedule Assist is a rescheduling workflow that lets fieldworkers suggest alternative availability when they decline a booking request. The suggested times can then be used by customers, admins, or the assignment engine to rebook the job.
Q: Does the feature automatically reschedule every declined job?
A: Not always. The result depends on your job assignment settings, decline reason settings, communication templates, and whether the fieldworker provides suggested availability. You can use it in automatic or manual workflows.
Q: When does the fieldworker get asked to suggest alternative times?
A: The fieldworker is prompted when they select a decline reason that has Fieldworker Reschedule Assist enabled in the decline booking request form.
Q: Can fieldworkers suggest more than one time?
A: Yes. Fieldworkers can suggest multiple time intervals and, where supported, multiple dates. This gives the customer or dispatcher more flexibility when choosing a new appointment time.
Q: What happens if multiple fieldworkers suggest different times?
A: Suggested times can be reviewed by the admin or shown to the customer depending on your workflow. In automatic workflows, the job can be re-broadcast after the customer selects a new time. In manual workflows, the dispatcher can choose which suggested window to apply.
Q: What if two fieldworkers suggest overlapping availability?
A: Overlapping suggestions can give the customer or dispatcher more choice. The final assignment still depends on your job assignment method, fieldworker response, eligibility, and dispatcher approval where required.
Q: Can customers choose from the suggested times themselves?
A: Yes, when the workflow is configured to notify customers, they can receive an email or SMS with a secure link to choose a suitable time.
Q: Can admins review suggestions before the customer is notified?
A: Yes. In manual assignment workflows, suggested availability appears in the booking record so dispatchers can review, apply, edit, notify, or manually assign the job.
Q: What happens if no fieldworker suggests alternative availability?
A: OctopusPro can use a fallback workflow, such as sending the customer a reschedule link or flagging the booking as unassigned or action required for dispatcher follow-up.
Q: Are suggested times checked against working hours and availability?
A: Suggested times should be used together with your configured working hours, fieldworker availability, service matching, and assignment rules. For best results, keep fieldworker schedules and availability settings accurate.
Q: Can OctopusPro send updated job requests after the customer chooses a new time?
A: Yes. Depending on your assignment settings, OctopusPro can send or re-broadcast the updated booking request to eligible fieldworkers.
Q: Does the customer selecting a time mean the job is automatically assigned?
A: Not always. In automatic workflows, the system can continue the assignment process automatically. In manual workflows, an admin may still need to review the selected time, confirm the appointment, and assign the job.
Q: Can administrators override the automated workflow?
A: Yes. Admin users can review booking details, change appointment times, contact customers, send job requests, and manually assign fieldworkers where permissions allow.
Q: Does this work with service areas and skill-based assignment?
A: Yes. The workflow should be used with your assigned services, skills, service areas, and travel radius settings so the booking is sent to fieldworkers who are suitable for the job.
Q: Does this work with Google Calendar or Outlook calendar sync?
A: When calendar integrations are enabled, accepted or assigned booking updates can sync with linked calendars according to your calendar integration settings.
Q: Is the rescheduling link secure?
A: Customer rescheduling links are designed to take the customer directly to the relevant booking action. Your final security behaviour depends on your portal, communication, and booking settings.
Q: Can I customise the customer email and SMS text?
A: Yes. You can customise the relevant templates from your email and SMS template settings. Use clear wording so customers understand that the original time was not accepted and that they can choose a new time.
Q: Can I report on fieldworker decline reasons?
A: Yes. Decline reasons and booking history records can help managers understand why jobs are declined and where scheduling or fieldworker coverage may need improvement.
Q: Should Fieldworker Reschedule Assist replace fieldworker calendar management?
A: No. It should be used as a recovery workflow. Fieldworkers should still keep their working hours, blocked times, and real-time availability accurate so unsuitable booking requests are reduced in the first place.
Conclusion
Fieldworker Reschedule Assist helps field service businesses turn declined booking requests into organised rescheduling opportunities. By collecting alternative availability at the moment a fieldworker declines, OctopusPro gives customers and dispatchers clearer options, reduces manual coordination, and keeps jobs moving through the assignment workflow.
Use this feature together with accurate fieldworker working hours, real-time availability, clear decline reasons, assigned services, service area settings, well-written email and SMS templates, and a job assignment method that matches your dispatch process. This creates a smoother experience for customers, fieldworkers, and office staff while helping your business recover more bookings that might otherwise be lost.
To stay updated, please subscribe to our YouTube channel.