schedule

CustomerVisitLogsView

AI-ready execution log view for tracking customer visits performed by sales representatives, including success/failure status and visit duration.
visit-log execution salesforce activity-tracking
Purpose

This view records actual visit activities performed by sales representatives. It provides detailed logs of each visit attempt including time, outcome, and failure reasons when applicable.

Business Rules
  • Each record represents a single visit attempt (AID is unique).
  • A salesperson can visit the same customer multiple times in a single day.
  • Multiple visits per customer per day are allowed and tracked separately.
  • NotOrderCouse = 0 indicates a successful visit that resulted in an order.
  • NotOrderCouse <> 0 indicates a failed visit with a reason code.
  • Actual order details are stored in order-related views, not in this log.
Relationships

This view represents the field execution layer of customer visits. It captures actual sales activities performed by representatives and connects them to planning, sales outcomes, and downstream business processes including financial performance, logistics, and customer behavior analysis.

Related View Join Keys Description
SellerVisitPathCustomersView SellerID, CustID, VisitDate Compares planned vs actual visits to measure execution accuracy, route adherence, and field productivity.
CustAssignToSeller SellerID, CustID Validates whether executed visits align with assigned territories and ownership structure.
SalesInvoiceView SellerID, CustID (indirect via Visit outcome) Measures conversion impact of visits on actual sales generation (visit → order pipeline relationship).
OrderFinancialSummaryView CustID (indirect), SellerID Analyzes financial impact of customer visits including revenue generation and order value trends.
OrderCollectionAnalyticsView CustID (indirect) Evaluates whether visit frequency improves payment behavior and reduces overdue balances.
OrderReturnSummaryView CustID (indirect) Correlates visit activity with return behavior and product dissatisfaction signals.
CustomerPotentialAnalyticsView CustID Measures how execution intensity influences customer potential score and engagement level.
DeliveryOperationAnalyticsView SellerID, CustID (indirect chain) Links downstream logistics performance with customer engagement patterns and visit outcomes.
InventoryView Indirect via SalesInvoiceView Connects visit outcomes to demand generation and resulting inventory consumption patterns.
CustomerVisitLogsView (Current) AID, SellerID, CustID Core execution fact capturing real customer visits, outcomes, timing, and success/failure reasons.
Primary Execution Intelligence Strategy
  • SellerID → Field force performance and productivity measurement
  • CustID → Customer engagement and interaction history
  • VisitDate → Temporal alignment with planning and sales cycles
  • AID → Unique visit execution identifier (event-level grain)
  • NotOrderCouse → Conversion efficiency signal (visit → order success rate)
Key Definitions
  • AID: Unique identifier for each visit record.
  • SellerID: Sales representative identifier.
  • CustID: Customer identifier.
  • SCID: Sales channel identifier.
  • VisitDate: Visit date (string format YYYY/MM/DD).
  • StartTime: Visit start time (HH:MM:SS).
  • EndTime: Visit end time (HH:MM:SS).
  • NotOrderCouse: Status code (0 = success, non-zero = failure reason).
  • CouseDesc: Description of failure reason.
Date & Time Format
schedule
Important

VisitDate is stored as a STRING in format YYYY/MM/DD (not DateTime). StartTime and EndTime are stored as STRING values in format HH:MM:SS.

Usage
  • Sales performance tracking
  • Visit success rate analysis
  • Customer engagement monitoring
  • Sales force productivity measurement
  • Route execution analysis
  • AI-based visit outcome prediction
Important Notes
warning
Execution vs Planning

This view represents actual executed visits. It must be used together with visit planning views to compare planned vs actual performance.