Verify Subcontractor Booking Requests Before Promising a Slot

Why Requests and Confirmed Appointments Are Different Things

A booking request is a statement of intent from a vendor: they have a customer who needs work, they want a slot, and they are asking whether you can take it. It carries no guarantee that the customer has actually committed, that the job details are complete, or that the price has been agreed. Treating it as a confirmed appointment before you have verified those three things creates problems in both directions — you block a slot that might not materialize, or you leave a real customer unbooked while waiting on a vendor who never follows up.

The practical distinction matters most when you are running a tight schedule. A solo operator or two-person team has very little buffer for a job that shows up underspecified. If a vendor tells you a customer wants a full interior detail and you arrive to find a cargo van that needs a decontamination wash too, you are either turning work down or running two hours over. That gap starts at the request stage, not the day of the job.

Related resource: Detailing Team Handoffs: What the Next Person Needs

What to Collect Before Accepting Any Vendor Request

Before you touch your schedule, you need four things confirmed in writing: the vehicle details, the exact service scope, the customer-facing price or your agreed payout, and a contact who can authorize changes on the day. Anything missing from that list means the request is incomplete and should not be accepted yet. Asking for these details up front also signals to vendors that you run a tight operation, which tends to self-select for more professional partners.

Vehicle details matter because they drive time and product cost. A Toyota Camry sedan and a lifted crew-cab truck are not the same job even if both are listed as an interior detail. Service scope matters because vendors sometimes summarize loosely — 'full detail' can mean anything from a wipe-down to a two-stage paint correction depending on who is using the phrase. Getting the scope in writing before you confirm protects you from scope creep and from disputes over what was included.

• Year, make, model, and condition notes (pet hair, heavy soiling, modifications that affect access)
• Exact service list, not a package name unless you defined that package with this vendor
• Customer-facing price or your agreed payout, whichever applies, confirmed in writing
• Location, access instructions, and whether a customer or fleet contact will be present
• Vendor contact who can authorize scope changes if something unexpected comes up on-site

Related resource: A Detailing Subcontractor Work Order That Prevents Guesswork

The Verification Task: Assign It Before Moving On

Once a request comes in, the single most useful thing you can do is treat verification as an assigned task with a deadline, not a mental note. If you own the business solo, that task is assigned to you. If you have a coordinator or office person, it goes to them. The task should include which details are still missing, who needs to respond, and when you will close the request as accepted or declined if you have not heard back.

Setting a response deadline matters because vendor requests have a tendency to sit in inboxes. If you do not hear back within your stated window — say, 24 business hours — you should treat the slot as available again rather than holding it indefinitely. Vendors who send requests and then go quiet are a real scheduling hazard. A deadline turns that hazard into a clear process: you follow up once, and if there is no response, the slot opens.

VENDOR REQUEST VERIFICATION TASK

Vendor name:
Request received (date/time):
Requested appointment date/time:
Vehicle: Year / Make / Model / Condition notes
Service scope requested:
Customer price or your payout confirmed? Y / N
Location and access confirmed? Y / N
On-site contact confirmed? Y / N

Missing items to resolve before accepting:
1.
2.
3.

Follow-up sent to vendor (date/time):
Response deadline:
Decision: ACCEPTED / DECLINED / NO RESPONSE - SLOT RELEASED
Decision recorded (date/time):
Customer or vendor notified of decision (date/time):

Worked Scenario: A Fleet Vendor Sends an Incomplete Request

Hypothetical: A local fleet management company you have worked with twice sends a message on a Tuesday morning asking you to book a full detail for one of their vehicles on Thursday at 9 a.m. They give you a name and a pickup location but no vehicle description and no service scope beyond 'full detail.' Your Thursday morning currently has one opening.

Using the verification task above, you note two missing items: vehicle type and confirmed service scope. You send a short reply asking for the year, make, model, condition level, and exactly which services they want completed. You set a response deadline of Wednesday at noon. The vendor responds Wednesday morning with a full-size SUV in fair condition, interior vacuum and wipe-down only, no exterior work because the fleet washes in-house. That changes your time estimate from three hours to about ninety minutes. You confirm the payout rate you both agreed to previously, create the appointment, and notify the vendor. If they had not responded by Wednesday noon, you would have released the slot and sent a single follow-up message. The key point is that Thursday's 9 a.m. slot was never blocked during verification — it stayed available until you had enough information to make a real decision.

How to Decline a Request Without Burning the Relationship

Declining a vendor request is a normal part of managing subcontracted work. You might be fully booked, the job might be outside your service area, the scope might not be worth the payout, or the details might never come in clean enough to accept. A decline delivered quickly and clearly is better for the relationship than a slow maybe that leaves the vendor unable to find another detailer in time.

Keep declines short and specific. Tell the vendor whether the issue is timing, scope, location, or payout, because that gives them something to work with for future requests. If timing is the only problem, say so — the vendor can try a different date. If the payout does not work for the scope they are describing, say that too, because it opens a negotiation rather than leaving the vendor guessing why you keep declining.

VENDOR REQUEST DECLINE MESSAGE

Hi [Vendor name],

Thank you for the request for [date/time]. I am not able to take this one because [choose one: I am fully booked that day / the location is outside my current service area / the scope as described does not fit the payout we discussed / I did not receive the vehicle details by the deadline].

[Optional: I have availability on [alternative date] if that works for your customer.]

[Optional: If the payout for this scope is flexible, I am happy to revisit.]

Let me know on future requests and I will get back to you within 24 hours.

[Your name]

Related resource: Measure Profit on Subcontracted Detailing Work

Tradeoffs and Failure Cases to Know

The main tradeoff in running a verification step is speed. A vendor who works with detailers who confirm instantly may push back on a 24-hour review window. That pressure is real, especially with fleet or dealership partners who have internal scheduling systems. The answer is to make your process fast, not to skip it. If you can review a complete request in ten minutes and confirm immediately, do that. The verification step only takes time when details are missing, which is exactly when you need it.

The most common failure case is accepting a request verbally or over the phone and only trying to collect written details afterward. By then the vendor considers the job confirmed, the customer may have been told a time, and walking it back creates friction even if the details never materialize cleanly. A second failure case is holding a slot open through a long back-and-forth without setting a deadline, which can cost you a paying retail customer who inquires about the same window. Set the deadline at the start, not after the slot has already been soft-blocked for two days.

Request Status Tracking: A Simple Reference Table

If you are managing more than one or two vendor relationships, it helps to keep a running status log so you can see at a glance which requests are pending, which are verified and confirmed, and which have been declined or released. The table below gives you a format you can copy into a notes doc, spreadsheet, or task list. Update it each time the status changes so you always know what is actually on your schedule versus what is still pending a decision.

Using Your Scheduling Tools to Support the Process

Whatever scheduling system you use, the goal is to keep incoming vendor requests separate from confirmed appointments until verification is complete. If your tool supports a request or unscheduled state, use it. If a vendor submits through a partner link, treat that submission as the start of verification, not the end. Only move the job to a confirmed appointment slot once all required details are in and you have made an explicit decision to accept.

Weavr's workflow supports this distinction: vendor partner links generate requests that sit in a pending state requiring your review and office verification before they become scheduled appointments. You can assign a verification task linked to the request, which gives whoever handles your scheduling a clear action item rather than a message sitting in an inbox. Once you confirm the details and accept, the appointment is created and visible on your calendar. That separation between request and confirmed appointment is the operational boundary this whole process depends on.

Continue reading

• Detailing Team Handoffs: What the Next Person Needs
• Measure Profit on Subcontracted Detailing Work
• A Detailing Subcontractor Work Order That Prevents Guesswork
• Reconcile Completed Vendor Jobs Before Approving Payouts