map

SellerVisitPathCustomersView

AI-ready operational planning view that defines which customers should be visited by each salesperson on scheduled dates.
visit-plan routing salesforce coverage
Purpose

This view represents the daily visit planning structure for sales representatives. It defines which customers are scheduled to be visited by each salesperson on specific dates.

Business Rules
  • Each record represents a single planned customer visit.
  • A salesperson can have multiple customers scheduled on the same date.
  • A customer may appear in multiple visit dates.
  • Being listed in this view does not guarantee that the visit was performed.
  • Actual visit execution data is stored in separate operational views.
  • SellerID + CustID + PathDate forms the logical unique key.
Relationships

This view represents planned sales visit routes and acts as a scheduling layer for salesperson-customer interactions. It can be connected to execution, sales, and performance views to compare planned vs actual activity.

Related View Join Keys Description
CustAssignToSeller SellerID, CustID Validates customer ownership and assignment rules against planned visit routes.
CustomerPotentialAnalyticsView CustID Helps prioritize visit planning based on customer potential score, churn risk and opportunity value.
CustomerVisitLogsView SellerID, CustID Compares planned visits with actual visit execution logs to measure route effectiveness.
SalesInvoiceView SellerID, CustID Links visit planning with actual sales performance and invoice generation outcomes.
OrderFinancialSummaryView CustID, SellerID Analyzes financial impact of planned customer visits on order value and revenue generation.
OrderReturnSummaryView CustID, SellerID Evaluates whether visited customers generate higher return rates or product issues.
OrderCollectionAnalyticsView CustID Correlates visit planning with payment behavior and collection efficiency.
SellerVisitPathCustomersView (Current) SellerID, CustID, PathDate Core planning dataset defining which customers are assigned to each salesperson per scheduled date.
Primary Join Strategy
  • SellerID → Salesperson ownership, routing and performance tracking
  • CustID → Customer targeting, segmentation and engagement analysis
  • PathDate → Temporal planning vs execution comparison
  • SellerID + CustID → Behavioral consistency between planning and actual sales
Fields
Field Type Description
SellerID int Identifier of the sales representative.
CustID int Identifier of the customer scheduled for visit.
PathDate string Planned visit date in YYYY/MM/DD format.
Date Format
schedule
Important

PathDate is stored as a string in the format YYYY/MM/DD. It is not a DateTime type and must be converted before performing date operations or filtering.

Usage
  • Daily route planning
  • Coverage analysis
  • Planned vs actual visit comparison
  • Sales force scheduling
  • Route optimization
  • AI-based visit recommendation systems
Important Notes
warning
Planned Visit ≠ Actual Visit

This view represents planned activities only. Actual execution and visit outcomes are stored in separate operational datasets.