Groundhogg Pro adds SMS sends logged in wp_gh_sms_log, lead score values stored as meta on wp_gh_contactmeta, and advanced segment definitions persisted alongside funnels. Each Pro feature ships an appropriate admin screen for setup and lookup, but cross-feature questions like "which high-score leads with SMS opt-in have not received a broadcast this month" need a different shape of view than the per-screen UI provides.

SleekView reads wp_gh_contacts directly and joins wp_gh_contactmeta for the lead score column, wp_gh_contact_tag_relationships for tag joins and wp_gh_sms_log for last SMS status. The contact view becomes a single sortable workspace with status, score, tags, SMS opt-in and last activity as first-class columns. Advanced segment definitions in Groundhogg are read as filter presets that can be combined with extra ad-hoc filters in SleekView.

Inline edits route through Groundhogg's contact functions where supported, so optin status changes, tag updates and score recalculations call the same plugin hooks the default UI uses. The Pro tables stay the source of truth; SleekView is the working layer that lets ops, marketing and support read and edit them in shape.

Groundhogg Pro turns a self-hosted automation platform into something that competes with hosted suites by adding SMS, lead scoring and advanced segmentation on top of the same wp_gh_contacts tables. Each Pro feature gets a focused admin screen because that is the right shape for setup and one-off investigation. The shape becomes a limitation when marketers want to combine lead score with SMS deliverability and tag membership in one cohort view, or when ops want to find every contact with optin confirmed but a recent SMS failure.

SleekView reads the Pro tables directly with the joins those questions need, exposes the right columns and filters, and routes inline edits through Groundhogg's own contact functions. Funnel triggers, score recalculations and suppression events keep firing because nothing bypasses the plugin's data layer. Lifecycle marketers stop exporting CSVs.

Compliance gets a clean GDPR view per contact. The Pro schema is already built for cross-feature questions; SleekView is the table layer that asks them.