Fil

If you already have experience with the Salesforce platform, you're probably aware that Marketing Cloud Engagement is a rather unique product.  

The first thing I would be concerned about is whether you actually have access to a Marketing Cloud Engagement environment. Since there is no generally available demo environment, your learning progress will be extremely slow if you don't have access to a hands-on environment where you can practice. 

If you want to start with the integration points between Service Cloud and Marketing Cloud Engagement, I would recommend beginning with the following Trailhead module: 

That said, very few people start their learning journey from there. In most cases, it's better to begin with the fundamentals of Marketing Cloud Engagement itself. 

For beginners, Kaelan Moss has put together an excellent Trailmix. I would highly recommend starting with the following: 

Kaelan is also a great mentor within the Marketing Cloud Engagement community. He has written some very valuable guidance on the mindset and approach that anyone learning Marketing Cloud Engagement should have. I recommend reading it when you have some time: 

In addition, the resource collection he compiled is one of the best available. I strongly recommend using it to find learning materials that match your current skill level: 

Hi , 

I think it's already enabled. 

@Abbey Aucoin @Kyle Hetherington

If you see an unstructured GUID or string instead of an email address, those records were likely created by a bot attack.  

Their source is probably the data extension used for a cloud page—specifically, a publicly accessible "preference" or "contact us" page. And they will appear in your all contacts if you have automated journey that gets triggered based out of these DEs.

.

Hi @Yash Gosara

 Please see below: 

1. Field Service – Maximum Travel From Home rule always uses aerial routing calculations regardless of whether point-to-point predictive routing or SLR has been enabled on the org. See product documentation here.

.  

2. When Maximum Travel From Home Type is set to Travel Time, the system calculates the distance using the Default Travel Speed defined under Field Service Settings -> Scheduling -> Routing (see product documentation here for more details).  

This setting strictly considers one-way travel time/distance to reach the service appointment. In the example provided by you, the rule would ensure that a resource doesn't drive more than 120 minutes from their home base to get to their first appointment or any individual appointment, ensuring that they are routed within a 120 minutes travel radius from their home base. It does not aggregate the round-trip or return travel, or does not restrict travel time between individual appointments. 

The other two settings (assuming you referred to these available under Field Service - Service Resource Availability rule) - Travel From Home (minutes) and Travel To Home (minutes) control how much travel time will be in resource's personal vs. company/scheduled time. For example, if the travel time to the first appointment is 60 mins, and Travel from Home (minutes) is set to 20 mins, the system will schedule 20 mins in resource's non-working hours, and 40 mins in resource's working hours. See more details in product documentation here

. 

The settings above are not buffers. If you want to add buffers (additional travel time for parking etc.) for each ServiceAppointment, you can configure travel time buffers at the org, service territory, or individual service appointment level to improve the precision of your scheduling operations. 

For your question on using both Max Travel time constraint using distance and travel time in a single scheduling policy, could you explain the use case? If the need is to use different logic for different group of resources, you can leverage relevance groups to create more than 1 Max Travel from home base rule in the same scheduling policy. 

Lastly, Point to point predictive routing does not use the static travel speed. It calculates travel speed dynamically using real road layouts, road types and historical time-of-day traffic patterns. You can setup Travel Modes per territory, resource, or both for accurate routing calculations based on transportation type, toll road preferences, and the presence of hazardous materials. The default travel mode is set to car, using toll roads, and not carrying hazardous materials. 

Default Travel Speed under Field Service settings is used during aerial routing calculations only - when calculating Max Travel from Home base rule, or falling back to aerial routing when ESO cannot calculate predictive travel (for example - coordinates too far from an officially mapped road).

Hope this helps!