Are you charging for estimates? How do you handle it in FieldPulse?

been seeing a lot of talk about this lately. in my experience charging for estimates is a whole thing.

we started doing diagnostic fees about 3 years ago. $89 to show up and figure out what's wrong. if they hire us, it rolls into the job. if they don't, we're not eating the cost of the truck roll and my guys' time.

problem is FieldPulse doesn't really have a clean way to handle this. we been creating a "job" for the estimate then converting it if they bite. but that clutters up the schedule and my dispatchers hate it.

anyone figured out something better? or you just not charging for estimates at all and dealing with the tire kickers?
Parents
  • so we actually do it a little different and basically what i did was set up a separate "estimate" status in the workflow so it's not mixed in with actual jobs but still trackable and the way it works is we start with that status and then move it to scheduled if they book and my dispatcher can filter them out when she's looking at real workload if that makes sense?

    been working pretty good for us anyway. customers seem to get it when you explain it's basically paying for our expertise to figure out what they actually need
Reply
  • so we actually do it a little different and basically what i did was set up a separate "estimate" status in the workflow so it's not mixed in with actual jobs but still trackable and the way it works is we start with that status and then move it to scheduled if they book and my dispatcher can filter them out when she's looking at real workload if that makes sense?

    been working pretty good for us anyway. customers seem to get it when you explain it's basically paying for our expertise to figure out what they actually need
Children