I downloaded a Trial Org to test out the functionality, but I was hoping that someone with experience using this product could let me know if my business scenario is something that could be made easier by using the Scheduler before I spend too much time testing.
I am working with a client that hosts product pickups at different locations. There is only 1 product, but each location has a different capacity for this product and different hours of operation. The customers would need to be able to access the company's Website to schedule a pickup at one of these locations, and if they are a first time customer, create a new Contact record.
Currently, they use custom code and Visualforce for this, and I am hoping to replace this code and interface with the scheduler, as the historical code is a mess and causing issues all over the Org. Based on the Salesforce Help pages and other resources, I believe the Scheduler should be able to work for this business case, but I want to make sure before suggesting this solution to the client. Any help with understanding limitations or considerations would be appreciated. Thanks in advance
Hi Thomas,
Based on the description of your use case, Scheduler would seem to be a very good fit for your customer.
The basic building blocks for Scheduler are:
1. Appointment topic (work type group object)would seem to be simply product pickup.
2. Appointment details (work type) would seem to be pretty consistent regardless as to the pickup location (service territory).
3. The Service Territory definition can include operating hours.
4. The Service Resources could likely be defined as assets as opposed to individuals/users. I am assuming that any available person at the location can help the customer with the pickup.
5. You could likely allow for concurrent scheduling.
The only item/issue that would require a bit of further discussion is how to account for the different capacity at each pickup location. I will reach out to you offline to discuss this further.
