Microsoft Dynamics 365
on 7/9/2019 11:56:33 PM
Thank you for your feedback.
Currently this is not in our roadmap; however, we are tracking it and if we get more feedback and votes, we may consider it in the future. As you're likely aware, all of our data is associate to service accounts so this would be a significant shift, however, if there's enough demand, we would consider making this change.
Having limited to having only account, the whole B2C line of business is completely impacted in the retail industry.
We really need this capability as Work orders should be about the contact. We can derive the Account from that but we are trying to service individuals, not orgs.
Indeed a much needed feature. Having a limitation of creating work orders only for accounts essentially limits the applicability of Field Service to B2B scenarios only. B2C scenarios are so common though where field service is applicable. There are many examples where a companies service individuals in their premises such as installation and servicing of HVAC appliances.
As with previous posters, I feel this is an absolute must have to convince most retail customers to actually use MS Field Service. Otherwise they simply purchase other solutions. Up-voted this one.
Yes, it seems strange they didn't use the customer field and instead opted for the Account Entity instead. We have 2 clients now with B2C requirements - A large wholesaler of cleaning and steam iron products and a solar company that sells to residential addresses. Both of these require the use of contact or customer entities and this short-sightedness causes us to create contacts as accounts and then map that way.
With over 2,000 solar installations to date and 50,000 retail customers for Steam Irons and cleaning products, this is going to put a lot of bad data in to our system. It also makes universal search more convoluted because staff see duplicate entries when searching.
Microsoft, we need a solution!
In our case, most of the times Work Orders are getting associated with Contacts rather than Accounts. Since, Field Service is not providing feature to associate Contact with Work Order, our client is not happy with this behavior. Kindly look into it and do the needful. Thanks.
I think this is one of the most common requirements. All new projects I am working with require this scenario and we have to handle Accounts as Contacts as a workaround at some point. This is not efficient and I can see a rise in the demand for Field Service solution in MENA region at least. I hope Microsoft will tackle this issue soon before the customers start looking for alternate solutions.
B2C field service is more common than B2C in my experience. The current account fields should definitely be customer fields rather than lookups to accounts.
In any scenario where the service is provided to private customers, without this option Field Service is not operational. It is a very serious problem ...
I dont really understand the reason why you did choose the account lookup on the work order instead of using the customer lookup to be able to choose between company OR contact. I am also having a customer looking for a B2C scenario where the contact and his personal address does matter for the job do be executed. Please consider quickly to implement this feature as well to be able to do offer the solution for a larger number of customers.