SleekView reads the WS Form Pro custom database tables directly: forms, submissions, and field values. Indexed queries on the clean schema make aggregations fast. No postmeta sprawl, no joins to wp_posts, no slowdowns even on high-volume sites.

Yes for low-cardinality field types (dropdowns, status fields, radios). Pivoting from the WS Form field-values table at query time exposes per-field values as chartable dimensions. Free-text fields produce too many distinct values to chart usefully.

No. SleekView Charts is read-only on WS Form Pro's tables. The form builder, conditional logic, integrations, and confirmations all continue to work unchanged. Inline edits routed through the Table tab use WS Form's own update functions and fire hooks normally.

Yes. Save views and scope per WordPress role or capability. Marketing sees source-page attribution, support sees per-assignee workload, ops sees status mix. Each view persists per user with role-scoped defaults.

Aggregations use indexed columns on WS Form's submissions table. Performance scales with index coverage on the group-by column, so hundreds of thousands of submissions stay responsive when grouping by form, status, source URL, or date_added.

Each card exports its aggregated rows as CSV with group-by labels and aggregate values. Useful for handing marketing the campaign-summary numbers behind a chart or feeding ops a status-mix breakdown they can use in their own reporting.

Yes. WS Form's CRM, email, and webhook integrations fire on submission, not on display, so charts reading the data don't change integration behavior. Edits through the Table tab run through the same update hooks the integrations listen to, so external systems stay in sync.

Yes. Status and any spam-score field both become chart dimensions. Count spam-flagged submissions per form, distribute spam scores, or rank sender domains driving the most spam — all on the same dashboard as the volume cards.