Before anyone is hired to bring you estimates, ask whether those requests are local jobs you can schedule. A busy stream of names is not the same as a nearby household move your crew can run. The page they send people to, the request that arrives, and the work you book have to describe the same job, or you will spend the week declining work you accidentally invited.
This guide covers the estimates you can still take, what the helper must know, questions about fit, requests you will not chase, how a trial would start, and what you still book yourself.
Takeaways
- Define the local jobs you can still take before you ask anyone to send requests.
- Make the helper learn that definition, including what a request must contain.
- Refuse requests that are not local, not ready, or not a job you do.
- Start with a short trial, and keep the booking decision with you.
The Estimates You Can Still Take
The estimates you can still take are local household jobs you have room to talk about and, if they fit, to put on the schedule. Write that down before you talk to a helper. A nearby job, in this trade, means a local move: the crew treats it as local, the home is the job, and you are not being asked to invent a long-distance shipment or a storage contract out of a short form. If you cannot describe that job in a few sentences, you are not ready to have someone bring you more of it.
Include the edges. Stairs you will discuss, packing that is a choice, homes you need to see, and dates you will not pretend to hold all belong in the description. So do the jobs you like and the jobs that wreck a week. A helper who does not know the second list will send you exactly those files, because they often look like urgent opportunities.
Capacity is part of the definition. If the next open conversation is already far out, more requests do not help. They create a pile you will answer late, which teaches households that the page lied about a callback. Hire for requests only when a real request can still become a real conversation in the time your page implies.
This is a filter, not a wish. It should match the week you can run, not the week a helper's pitch assumes you want. Read it to the person who schedules, and fix any line they would not use.
What the Helper Must Know
The helper must know the filter, the page a household will see, and what a complete request looks like. Complete means you can tell it is a local job, you can reach a person, and you know the open facts that decide whether to call. A name and a cheerful note are not complete. If the helper's tool cannot hold the facts you need, the requests will arrive as puzzles.
They must know what you will not let them say. They are bringing a request, not giving an estimate: no figure, no promise that a date is held, and no claim that packing or a hard item is included. If their usual message says you are all set for an estimate, rewrite it until it says a request was passed to you and you will decide whether it fits. The household should not think the estimate already happened.
They must know the difference between your local offer and everything else you might do. A request for a long haul, an office, or a unit is not a failed local form. It is a different door. Tell them where those requests go, even if the answer is that you do not want them. Silence gets filled with a guess, and the guess lands in your local pile.
Triwave Consulting treats that briefing as Initial Contact: the situation and the challenge, said so a stranger could repeat them. The Detailed Discussion is where you test the briefing against real requests. Implementation is you booking the jobs that fit, not the helper declaring them booked.
Questions About Fit
Ask whether they can restate your filter without adding a job you did not include. If they immediately widen it to any move, they will widen the requests. Fit is narrow on purpose, and a helper who is proud of volume before they can say what your job is has the wrong goal.
Ask where the household thought they were. Did they see your page, or a page the helper controls that describes a different company? If the household arrives expecting services you do not offer, the request is already a mismatch. You can still talk to them, but you should know you are correcting an invitation, not continuing one. Ask to read the page that sits in front of the form, and if you would not sign it, do not let it send you people.
Ask what happens to a request you decline. A good answer returns the household to an honest next step, or closes the loop without inventing a reason you did not give. A bad answer keeps selling you after you said no, or drops the person with no word at all. Either one becomes your reputation, because the household remembers the company named in the note.
Ask how fast a request reaches you, and what fast means on a day you are on a job. A helper who needs a live reply from the truck in order to look competent is not bringing estimates. They are borrowing your attention. Fit includes a pace you can keep while the crew is working.
Requests You Will Not Chase
You will not chase a request that is not the local job you defined, not complete enough to know that, or already promised something you did not say. Chasing those files feels diligent and trains the helper to send more of them. Declining them consistently is the work that keeps the stream honest.
| Request in front of you | Chase it | Leave it |
|---|---|---|
| A local household move with a person to call and the open facts listed | Yes, if you still have room for the conversation | When the schedule cannot hold another real callback |
| A story with no picture of the home | Only to ask for the missing picture, once | When the same blank comes back and the helper keeps forwarding it |
| A long-distance shipment, an office, or storage dressed up as local | Only to point to the right door, if you have one | When you would have to pretend it is a local booking |
| A note that already quotes a figure or holds a date | Never, until the promise is corrected | Always, if the helper will not retract what the household was told |
| A household that wants a different job than your page names | Only after you restate the real job and they still want it | When they wanted the promised version, not yours |
Use the table as a desk rule, not as a speech for the household. The helper should be able to sort a request into a row before it reaches you. If every file lands in the you-decide pile, they are not filtering. They are forwarding, and forwarding is the job you already had.
Say the refusals out loud in the hiring conversation. People who bring requests often hear a refusal as a temporary objection, so repeat that the left column is the job and the right column is not a negotiation. A trial that ignores the right column is a failed trial, however busy it looked.
How a Trial Would Start
A trial should start small enough that you can read every request beside your filter. The point is to learn whether this help brings local jobs you can schedule, not to discover that in a flood. Agree the filter, the words they may use, and the rows you will not chase before the first household is contacted.
- Write the local job you can take, and the requests you will not chase, on one page you both keep.
- Agree the note a household will see, with no figure, no held date, and no extra included work.
- Send a few requests through, and read each one against the table the same day.
- Mark which requests you could schedule, which you declined, and which arrived already promised the wrong job.
- Stop the trial if the declined pile is the real product, or if you cannot tell what the household was told.
- Continue only if the requests that remain are local jobs you would have wanted without the helper.
During the trial, you still make the callback and you still decide the fit. The helper does not save you time by estimating. If the trial only works when they talk households into staying, it is not a source of estimates. It is a second sales pitch, and you should end it.
If you want the page and the request path built to match, Initial Contact with Triwave Consulting starts with this same filter. The Detailed Discussion checks the path against the jobs you can schedule, and Implementation follows that agreement. A helper bolted onto a fuzzy page will bring fuzzy requests, and the trial will show it quickly.
What You Still Book
You still book the job. A request is permission to talk, not a place on the schedule. The household should hear the booking decision from you, in the same words as the page, after you have confirmed the local job. If the helper's note already sounded like a booking, correct it before you talk about dates, because leaving the confusion in place books two different stories.
You still decide that a request belongs on the Local Movers offer and not somewhere else. That page is the offer for this work, and this article is the list of questions to ask before someone else starts filling the inbox. When a request is really about the wider trade, Moving & Storage is the door that keeps it from masquerading as a local estimate.
Keep a simple tally in words, not as a scoreboard: requests you could schedule, requests you refused, and requests that arrived with a promise you had to undo. If the first group is the one that grows, the help fits. If the other two grow, stop, because more activity on the wrong rows will not turn into a calendar you can run.
The page, the request, and the job you book have to agree. Hiring someone to bring estimates does not relax that rule. It makes the rule more important, because another person is now inviting households into it. Ask the questions first, then let a short trial show you whether the answers were true.
Questions
Should You Hire Before You Know Which Jobs You Can Take?
No. Hiring first buys a stream aimed at a guess. Write the local jobs you can still schedule, and the ones you will not chase, before anyone sends a household your way. If you cannot say that list out loud, you are not hiring yet. You are hoping a helper will define the company for you.
What If the Requests Look Busy but None Will Schedule?
Treat that as the result, not as a slow start you must endure. Busy and unschedulable means the filter and the invitation disagree. Stop the send, compare what households were told with what you can book, and change the invitation or end the help. More of the same week will not become a better week.
Can the Helper Promise a Callback Window?
Only if you can keep it on a day when the crew is out. A promised window you miss becomes the story of the company. If you cannot name a window you will actually meet, the note should say you will be in touch without dressing that up as a held time. Ask this before the trial, not after the first angry reply.
Do You Have to Take Every Request in a Trial?
No. A trial that requires you to accept bad fits is not a trial. It is a quota. Decline the rows you said you would decline, and judge the help by whether those rows shrink. Taking them to be polite teaches the helper that the filter was theater.
Where Should a Request That Is Not Local Go?
To the offer it actually is, if you have that door and the household still wants it, or back to a clear no if you do not. Do not relabel it as a local estimate so the file stays in one pile. A long-distance job, an office move, or storage has its own conversation, and stuffing it into the local book is how the schedule lies.
Conclusion
Ask whether the requests are local jobs you can schedule before you hire anyone to bring them. The page, the request, and the booking have to name the same work, and you still make the booking. A short trial will show you whether that is true, which a pitch about activity never will.
When you want estimate requests that match the local jobs you can still book, Speak With Us.
