Salesforce Maps Advanced object setup for Consumer Goods routes
Key Takeaway
In the Agentforce Consumer Goods enhanced data model, new visits need a Place ID and a Visit Template. A custom setting stores the default values. A fast (before-save) record-triggered flow assigns them before the visit is created.
Salesforce Maps Advanced builds optimized routes, called visit plans, that schedule field reps for store visits. Maps Advanced schedules reps for in-person visits only. Salesforce Maps doesn't know Agentforce Consumer Goods objects by default, so you tell it three things: which object holds store locations, where to save scheduled visits, and how to tell when a visit is done. The enhanced data model also needs a custom setting and a flow so that new visits get their required fields.
The objects a visit plan needs
A visit plan depends on four choices:
| Purpose | In Agentforce Consumer Goods | |
|---|---|---|
| Routable object | The stores to visit, with their location data | Retail Store |
| Calendar or output object | Where scheduled stops are saved | Visit |
| Visit object | Where completed visits are recorded | Visit, or another object such as an assessment task |
| User lookup | Assigns stores to reps | A user lookup field on Retail Store |
The Visit object can fill two different roles. As the output object, Visit is where Salesforce Maps writes scheduled stops. As the visit object, Visit is where Salesforce Maps reads whether a visit was completed.
Rep Ana has four stores on Thursday's route. Salesforce Maps writes four Visit records for those stops, so Visit is acting as the output object. Later, Salesforce Maps checks those Visit records to see whether Ana completed each visit, so Visit is now acting as the visit object.