✨ 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 Event Espresso Pro

SleekView Kanban reads Event Espresso Pro registrations straight from the WordPress database, groups them into status columns for registered, waitlist, attended, and no-show, and lets your event team drag cards across lanes to update attendance without opening every record.

♾️ Lifetime License available

SleekView Kanban board for Event Espresso Pro

Why Event Espresso Pro attendance needs a kanban

Event Espresso Pro stores each signup as a row inside wp_esp_registration, with a status column that the plugin updates as people register, move to a waitlist, get checked in at the door, or fail to show. The default admin list paginates these rows by event and hides the status field behind filters, so staff end up sorting, scrolling, and clicking into individual registrations just to count who is coming. For a single small event that is fine; for ten events a week it stops being workable.

SleekView Kanban groups the same wp_esp_registration rows by STS_ID and renders one card per attendee. Each card shows the event name pulled from wp_esp_event, the attendee name from ATT_fname, the email from ATT_email, and the ticket type or session if the row carries one. Lane counts sit next to each column heading so the room capacity check is a glance instead of a query.

Dragging a card from waitlist to registered writes the new value of STS_ID back to the same row in wp_esp_registration, so Event Espresso's own admin views, exported CSVs, and any connected email automations stay in sync. Bulk drags update every row inside a single SQL transaction, which means a 200-card check-in queue clears in one pass and the page refresh that used to take a minute now finishes in

Workflow

From Event Espresso table to kanban in four steps

1

Point SleekView at Event Espresso

Install SleekView, then pick Event Espresso Pro from the data source picker. The plugin auto-detects wp_esp_event and wp_esp_registration, including every custom column the plugin writes. No SQL to copy, just confirm...
2

Pick the status column

Open the view config and set the group-by column to STS_ID. SleekView reads every distinct value the plugin uses for registered, waitlist, attended, and no-show, then turns each one into a kanban column with the row c...
3

Choose what shows on each card

Decide which fields appear on the card front. Most teams pick the event name, the attendee name, the ticket type or session label, and the registration date. Hidden fields stay queryable from the card detail panel wit...
4

Turn on drag-and-drop writes

Flip the drag-and-drop switch and SleekView starts writing STS_ID updates back to wp_esp_registration on drop. Permissions follow WordPress capabilities, so only event managers can move cards into attended while volun...

Sample board

Sample Event Espresso attendance board

A live SleekView Kanban grouping Event Espresso Pro registrations by STS_ID, with card fronts showing event name, attendee name, and ticket type. Drag updates the row instantly.
Registered
182
Annual Members Conference
3-day pass, 412 sold
Spring Gala Dinner 2026 Edition
Single seat, 187 sold
Workshop: Knife Skills 2026 Edition
12-person cap, 11 sold
Waitlist
34
Charity 5K Run 2026 Edition
Solo entry, 642 sold
Wine + Cheese Pairing 2026 Edition
Pair ticket, 84 sold
Photography Field Day 2026 Edition
Solo, 47 sold (door check-in active)
Attended
147
VIP Roundtable Lunch 2026 Edition
Premium tier, 18 sold
Public Lecture Night 2026 Edition
Free RSVP, 312 sold (door check-in active)
Day Pass: Maker Faire 2026 Edition
Family bundle, 96 sold
No-show
21
Family Bake-along 2026 Edition
Group of 4, 28 sold (door check-in active)
Private Studio Tour 2026 Edition
Small group, 14 sold
Member-only Workshop 2026 Edition
Members-only, 22 sold

Comparison

Default Event Espresso list vs SleekView Kanban

Default Event Espresso list

  • Flat WordPress table that lists every Event Espresso registration in created-at order
  • No grouped view of who is registered, on the waitlist, attended, or no-show
  • Status changes need clicks into each row instead of a single drag and drop
  • Lane counts and capacity checks happen in a spreadsheet, not the dashboard
  • Bulk attendance updates rely on CSV exports and risky search-and-replace edits

SleekView Kanban

  • Reads wp_esp_registration rows live with no extra cron or sync job
  • Group by STS_ID turns each status into a lane with row counts
  • Drag-and-drop writes the new status back to wp_esp_registration in one query
  • Card fronts pull event name from wp_esp_event and attendee from ATT_fname
  • Capability checks gate writes to STS_ID by WordPress role

Features

What SleekView Kanban gives you for Event Espresso Pro

Live attendance lanes

Every distinct value of STS_ID becomes a kanban column, so registered, waitlist, attended, and no-show rows always appear in their own lane. Counts update the second a card is dropped, with no manual page refresh.

Drag updates the row

Drop a card into a new lane and SleekView writes the new STS_ID value straight to wp_esp_registration. Event Espresso's own admin views, CSV exports, and connected email automations all see the change immediately with no resync...

Card fronts staff can scan

Show event name, attendee, ticket type, and date on the card front and keep everything else queryable from the detail panel. Volunteer staff scan a hundred cards in seconds instead of opening every row in the admin table.

Audience

How event teams use a kanban on top of Event Espresso

Door-staff check-in

Volunteer staff at the door open the kanban on a phone and drag attendees from registered to attended as they scan tickets. The count next to each lane works as a live capacity check.

Waitlist promotion

Event managers drag cards from waitlist to registered as cancellations come in, and Event Espresso fires its own confirmation emails because the underlying STS_ID column changed.

No-show follow-up flow

After the event, staff filter the no-show lane to trigger a polite check-in email or refund flow. The card history shows who was promoted from waitlist and when, which makes the audit clean.

The bigger picture

Why a kanban beats the Event Espresso list for events

Event teams live and die by the lane count next to each status. Event Espresso Pro stores all of that in wp_esp_registration, but the plugin's own admin renders the rows as a flat table that staff have to filter, sort, and click through to make sense of. That works for a single small workshop.

It stops working the moment one person is running three concurrent events, a waitlist, and a check-in queue at the same time. A kanban grouped by STS_ID flips the problem on its head. Registered, waitlist, attended, and no-show each get a column, the row count sits in the heading, and a drag writes back to the same database row Event Espresso already manages.

Volunteer staff at the door scan a phone, drag a card, and the official admin record updates in the same instant. Connected email automations and any payment integrations see the change because the underlying row changed; there is no second source of truth to keep aligned. That is why event organisers running paid ticketing, multi-datetime events, and detailed registration forms pick a kanban view over the default list.

The data does no...

Questions

Common questions about SleekView Kanban for Event Espresso Pro

Yes. SleekView updates the same wp_esp_registration row that Event Espresso Pro already manages, inside a single SQL transaction, so the plugin's own admin views, exports, and any connected email automations see the change immediately with no second source of truth.

 

Yes. The group-by column is configurable per view. Most teams pick STS_ID because it maps cleanly to registered, waitlist, attended, and no-show, but you can group by event_id, ticket type, payment status, or any other column the plugin stores on the same row.

 

You control that. Capability checks gate every drag-and-drop write, so you can grant the move-to-attended permission to a custom volunteer role while keeping the move-to-cancelled action restricted to event managers and administrators. Logs record who moved which card.

 

Yes. Rendering uses keyset pagination per column with a virtualised card list, so a single event with 500 attendees stays snappy on a laptop or phone. Drag writes use a single update query rather than per-row REST calls, so bulk lane moves do not stall.

 

Yes. You can save multiple views, each filtered to a different event_id pulled from wp_esp_event, and switch between them with a tab bar. Door staff at a multi-venue festival keep one board open per stage and never see registrations from another event.

 

SleekView reads the current wp_esp_registration schema at render time rather than caching it, so a new column appears in the card detail panel automatically. If a column is renamed, the view config flags the missing field and lets you remap it without rebuilding the board.

 

Yes. The no-show lane is just another value of STS_ID, so dragging a card there writes that value back to wp_esp_registration and any Event Espresso automation hooked to the no-show event fires as normal. Follow-up emails and refund flows behave exactly as if you used the plugin admin.

 

Yes. The board reflows to a single-column carousel on small screens and supports touch drag for one-handed use. Volunteer staff scan a ticket QR code, drag the card from registered to attended, and the row updates without opening the WordPress admin app.

 

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