✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount

SleekView Kanban for WS Form Pro

SleekView reads your WS Form Pro submissions directly from the submit tables, groups them by submit status or any field you choose, and lets your team drag each card between columns to move triage forward without ever opening the default WS Form submit list view.

♾️ Lifetime License available

SleekView Kanban board for WS Form Pro

Why WS Form Pro submissions need a board on top

WS Form Pro stores submissions in wp_wsf_submit with field values broken out to wp_wsf_submit_meta, indexed by form ID and tagged with a submit status field that supports publish, draft, and trash plus a custom status mechanism for advanced workflows. The default submit admin shows a paginated list with filter tabs across the top.

SleekView reads the same wp_wsf_submit table, joins meta on demand for whatever fields you put on the card face, and surfaces every form field as a valid grouping axis. The natural starting point is the submit status with the four core values, but most teams take advantage of WS Form Pro custom statuses feature to add workflow stages like Awaiting review, In progress, and Closed, and group on the custom status field instead.

Dragging a card writes back through WS Form Pro own submit update API and fires the wsf_submit_save action so any Mailchimp, Slack, Zapier, or webhook integrations wired to submit updates run exactly as if the change came from the standard admin. Trashed submissions are filtered out of default boards with a dedicated trash review board available for restore and permanent delete decisions.

Workflow

From WS Form Pro submissions to a board in four steps

1

Connect WS Form Pro

Pick the WS Form Pro form to visualize from the SleekView source picker. Every field defined in the form builder, including hidden admin fields and meta written by integrations like Mailchimp and Salesforce, is auto-detected as a possible card field or grouping axis for the board.
2

Pick the column to group by

Choose any field as your grouping key. The default is the built-in submit status field with Published, Draft, and Trash, but most teams use WS Form Pro custom statuses to model their workflow with values like Awaiting review, In progress, and Closed and group on that field instead.
3

Choose what shows on cards

Drag up to six fields onto the card face. Common picks are name, email, subject, payment amount when the Stripe or PayPal action is used, and submit date. Cards stay compact at a glance and expand on click to reveal every field captured on the submission record itself.
4

Enable drag and drop

Flip on write-back so each card drag calls the WS Form Pro submit update API and fires wsf_submit_save, which means Mailchimp, Slack, Zapier, and webhook integrations wired to submit updates run exactly as if the change came from the standard WS Form Pro admin submit screen.

Sample board

Sample WS Form Pro submit board

A live preview of a sales lead capture board grouped by custom submit status, with submitter name and company on each card and per-column counts visible in the header for context.
Awaiting review
44
Demo request from large agency
Eli Brooks, 1h ago
Pricing question on annual plan
Rita Almeida, 2h ago
Integration with Asana ask
Owen Pratt, 3h ago
In progress
26
Refund query for invoice 5563
Yusuf Demir, assigned
Bug report on mobile signup
Polly West, assigned
Quote in legal review
Hannah Reed, assigned
Closed
118
Onboarding scheduled for client
Closed today
Quote signed by legal team
Closed yesterday
Refund processed via Stripe
Closed today
Trash
9
Duplicate signup from same IP
Trashed by admin
Spam mass outreach blast
Auto trashed today
Empty submit from staging URL
Trashed by user

Comparison

Default WS Form submit list versus SleekView Kanban

Default WS Form submit list

  • Submits land in a paginated table that lacks any visual sense of stage or queue depth
  • Custom statuses can be defined but only as a filter, not a visual board with drag support
  • Status changes need opening each submit individually, no bulk drag between states allowed
  • Custom dropdown fields cannot become the grouping axis from the default submit list screen
  • Team handoffs depend on internal notes that are invisible from the submit list view itself

SleekView Kanban

  • Reads directly from wp_wsf_submit and meta with no duplicate storage layer
  • Drag-and-drop fires wsf_submit_save so integrations stay in sync correctly
  • Group by built-in submit status, custom statuses, or any form field defined on the form
  • Card face accepts up to six fields including totals from the Stripe or PayPal action
  • Works with Mailchimp, Salesforce, Zapier, and webhook actions without breaking hooks

Features

What SleekView Kanban gives you for WS Form Pro

Group by any field or custom status

Submit status is the default grouping but WS Form Pro custom statuses are also recognized as a grouping axis. Any dropdown, radio, or checkbox field on the form is valid too, so you can build boards that model workflows beyond just the built-in submit status values.

Drag-and-drop writes back to submits

Moving a card calls the WS Form Pro submit update API and fires wsf_submit_save, which means Mailchimp, Salesforce, Zapier, and webhook actions wired to submit updates run exactly as if the change came from the standard WS Form Pro admin submit screen with full action fidelity.

Per-role column visibility

Hide the Trash column from sales reps, hide In progress from public-facing roles, or expose admin-only columns to managers. Permission rules read from the standard WordPress role and capability map you already configured for WS Form Pro submit list access today.

Audience

Common WS Form Pro boards teams build

Contact form triage

Group inbound contact submits by custom status so support sees what is waiting, what is in progress, and what was closed yesterday at a glance instead of scrolling the default paginated submit list view.

Lead pipeline tracking

Group quote request submits by sales stage to mirror your pipeline directly inside WordPress. Drag a card from Awaiting review to Quote Sent once you reply, then to Won or Lost once the prospect responds.

Bug report intake

Group bug report submits by engineering stage so developers can see what is in triage, what is in flight, and what needs verification before being marked as fixed and shipped to production users.

The bigger picture

Why a board beats the default WS Form Pro list view

WS Form Pro is a powerful form builder with a deep action system and custom status support, but its admin still assumes you will read submits one at a time. That assumption holds for low-volume forms and breaks down the moment a form becomes part of a workflow with multiple stages and multiple teammates handling triage at the same time. A kanban board fills the missing layer: queue visibility.

You see at a glance how many submits are sitting in each stage, which ones have been waiting longest, and what the team closed since yesterday. Status changes happen with a single drag instead of opening each submit edit screen, which compounds into real time savings once volume picks up. Because every column maps back to a real field on the submit, the board is not a parallel system that drifts.

Everything you see is exactly what Mailchimp, Salesforce, Zapier, and your other action-driven integrations already read from the same submit table. New teammates onboard in minutes because the board itself documents the workflow visually. The result is a WS Form Pro admin that finally matches how operations and sales teams actually run their day-to-day work.

Questions

Common questions about SleekView Kanban for WS Form Pro

The drag calls the WS Form Pro submit update API and fires wsf_submit_save, so the change is persisted directly to wp_wsf_submit and any Mailchimp, Salesforce, Zapier, or webhook actions wired to submit updates run exactly as if the change had come from the standard admin submit screen.

 

Yes. WS Form Pro supports custom statuses out of the box, and SleekView recognizes them as a valid grouping axis. Any dropdown, radio, or checkbox field on the form is also a valid grouping axis, so boards can model workflows beyond the built-in submit status values.

 

Custom statuses defined on a form appear as a groupable field in SleekView with each defined status becoming a board column. Dragging a card writes the new custom status to the submit record through the standard API so the change is reflected everywhere WS Form Pro reads the status.

 

Yes. Payment actions write payment status onto the submit meta when they run. SleekView surfaces that as a groupable field so you can build a board with Pending, Paid, Failed, and Refunded columns reading directly from the payment action meta on each submit row in the table.

 

Yes. Boards are saved as named views and each view scopes to specific WordPress roles. Sales can see a pipeline board, support can see a triage board, and admins can see a trash review board, all reading from the same underlying WS Form Pro submit table with no extra config.

 

Yes. Any submit stored in wp_wsf_submit appears on the board regardless of how it was created. Submits pushed in via Zapier or other automation tools using the WS Form Pro submit endpoints are indistinguishable from native form fills as far as the board is concerned.

 

Yes. The same role and capability rules that gate the default WS Form Pro submit list screen also gate SleekView. A user who cannot view submits in the standard admin cannot view them on the board, and read-only roles get a board they can view but cannot drag cards on.

 

Trashed submits have a status of trash and are filtered out of every default board because the query excludes that status. A dedicated Trash review board can be built that flips the filter to surface only trashed submits for restore decisions or permanent deletion review.

 

Pricing

More than 1000+
happy customers

Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.

Starter

€79

EUR

per year

  • 3 websites
  • 1 year of updates
  • 1 year of support

Pro

€149

EUR

per year

  • Unlimited websites
  • 1 year of updates
  • 1 year of support

Lifetime ♾️

Most popular

€249

EUR

once

  • Unlimited websites
  • Lifetime updates
  • Lifetime support

...or get the Bundle Deal
and save €250 🎁

The Bundle (unlimited sites)

Pay once, own it forever

Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.

What’s included

  • SleekAI

  • SleekByte

  • SleekMotion

  • SleekPixel

  • SleekRank

  • SleekView