Currently Enquiry's Follow-up date can be changed either manually or based on the Enquiry's status change. And Enquiry's status can be changed by changing Job's status.
thank you for your reply. We are currently applying both methods as you described. I'd like to go further than that and was hoping someone might know a nifty SQL to that extent.?
Hello Juana. What's the driver behind trying to get the Enq Follow Up date to match the Job Est Completion Date? Is it to assist customer services quickly provide updates if people call back?
you've hit it. ?That's my main reason. Furthermore, reporting on enquiries using follow-up dates would also make more sense.
I wouldn't rely on the Enquiry follow-up date for this as this could get changed as a result of any other Enquiry status update. Enquiry Commitments might be the way to go with this. You could get the Job status to trigger an Enquiry status that generates a commitment, which could get resolved when the Job is completed.
This still wouldn't handle your requirement to use the Job Priority to generate a follow up date though, but you can configure different commitment follow ups per Subject so that might give you enough flexibility, as presumably your follow up time will roughly depend on the nature of the enquiry?
I appreciate your ?input. The commitments only work to a certain point. Once an enquiry had been inspected and requires action according to our asset service plans, it follows the same scenario as a defect logged during a proactive (scheduled) inspection, which means that at the time of logging the defect it will be assigned a response time derived from the priority (defect severity & asset classification). For most of our defect types a job will be raised immediately with an estimated/target completion date. We re linking the statuses for enquiries and jobs when a job is raised, committed and completed. The job target completion time is not allowed to be changed from the day is was logged to its actual completion (for auditing purposes - Road Management Plan for instance).
In summary, our enquiry resolution time is dependent on the asset classification. I believe it would be to onerous to try and create that many enquiry statuses for each of the service subjects to capture all possible events.
Hi Juana, to follow on from John's earlier point storing this information in that field would always be risky. I think the best way to give customer facing staff access to this information is to create a linked data source or report that they can easily run from the List button. This way you can present this key date, and any other useful Job information, in an easy to digest format. Drop me an email if you want to talk this through in more detail.