The short version: A Microsoft Forms quote request with a photo upload, an address field and a timing question does the scoping before you ring anyone back. Power Automate can file the photos and details straight into a job folder and let you know the moment it lands, using tools already inside the Microsoft 365 you pay for.
One form instead of three phone calls
Build the quote request as a Microsoft Form with the details made required, not optional: a photo of the job, the address, roughly how big or how many, and when they want it done. A photo upload field takes an image straight from a phone camera, so a customer standing in front of the heat pump they want replaced or the wall they want painted can attach it in the same minute they fill in the form, no separate email with an attachment to chase.
Making the fields required is the whole trick. A phone call skips whatever the customer forgets to mention or you forget to ask under pressure; a form field with a red asterisk cannot be submitted blank.
Photos and files land where the job needs them
A Power Automate flow on the form's response can file the photo straight into a SharePoint folder named for that job, add the address and timing to a shared quotes list, and notify you in Teams or email with everything attached. Built on Forms and SharePoint, both standard connectors already inside Microsoft 365, this costs nothing extra. The callback you make afterwards is a confirmation of price and timing, not a discovery call where you are asking the same three questions you have asked forty times this month.
Once the photo is filed against the job rather than sitting in a text thread, it is also there when you invoice, which is the same habit the job-photo workflow post covers from the other end.
When it is not worth building
If you get a couple of quote requests a week and you are already good at asking the right three questions on the phone, a form is solving a problem you do not have, and the customer might prefer to just talk to you anyway. Build it once the volume means the same back-and-forth is eating an evening, or once a wasted trip to a job that turned out to need different gear has actually cost you money.
Common questions
How do I stop going back and forth just to get basic details for a quote?
Make the details required fields on the form itself rather than questions you ask on a callback. A photo, an address and a rough size or count cover most of what you need to price the job, and a required field cannot be skipped the way a rushed phone call can be.
What's a good way to scope a job before I call the customer back?
Have the photos and details land in a job folder before you dial. A Power Automate flow can file everything from the form into a SharePoint folder named for the job and notify you once it's ready, so the callback is a confirmation, not a discovery call.
How do I get the site address and timing upfront with a quote request?
Add both as required fields on the form: an address field and a simple timing question, this week, next month, no rush. Neither needs a premium connector, and both save the callback where you ask the two questions that decide whether you can even take the job.
Still asking the same three questions every call?
Tell me what you currently ask before you can quote. Book a free 30-minute call and I will build the form and the flow behind it.