WP ERP's CRM module stores contacts, companies, leads and customers in the shared wp_erp_peoples table with a type column distinguishing each role. Activities log to wp_erp_crm_customer_activities, schedules to wp_erp_crm_customer_schedules and contact ownership lives on wp_erp_crm_contact_owner. The default CRM UI splits each type onto its own tab which works for finding one record and limits cross-type operations.

SleekView reads wp_erp_peoples directly and joins wp_erp_crm_customer_companies for company affiliation, wp_erp_crm_customer_activities for last activity timestamp and wp_erp_peoplemeta for typed custom columns. Filters combine contact type, lifecycle stage, owner and last activity into saved views. Lead pipelines surface as a sortable workspace instead of a tab walk.

Inline edits go through WP ERP's CRM functions where supported, so activities, owner reassignments and stage moves trigger the same hooks the default UI fires. Activity logs in wp_erp_crm_customer_activities remain the audit trail; SleekView is the working layer that lets account managers and sales ops use them.

WP ERP shares the people store across CRM, HR and Accounting modules because contacts, employees and customers are often the same people in a small-business operation. The default CRM UI splits the work by type onto separate tabs, which is appropriate for finding one record and limiting accidental edits across modules. The cost is that cross-type operational questions need a different view shape than the per-tab UI provides.

Account managers want one filter that combines stage, owner and last activity. Sales ops wants a top-N view across leads and customers. Customer success wants schedules by owner and due date with contact context inline.

SleekView reads wp_erp_peoples directly with the joins those questions need, exposes custom wp_erp_peoplemeta as typed columns, and routes inline edits through WP ERP CRM's own functions. Activities, owner reassignments and stage moves keep firing the same hooks the default UI uses. The shared schema is already designed for this kind of view; SleekView is the table layer that uses it.