FluentCRM Automations defines funnels in wp_fc_funnels with conditions stored in wp_fc_funnel_sequences for the ordered steps. Per-subscriber enrolment progress lives in wp_fc_funnel_subscribers with a status column, current step id and a last-executed timestamp. The default automation UI shows funnel-level stats and a per-funnel report, which is useful for one funnel and limited the moment a marketer needs to see all stuck enrolments across every active automation.

SleekView reads wp_fc_funnel_subscribers directly and joins wp_fc_subscribers for the contact email plus wp_fc_funnels for the funnel title and wp_fc_funnel_sequences for the step label. The result is a single table where status, funnel, current step and last activity are first-class columns. Filters can combine "status is waiting", "current step is wait 3 days" and "last activity older than 7 days" to surface enrolments that need a manual nudge.

Inline edits route through FluentCRM hooks where supported, so cancelling an enrolment or moving a subscriber to a different step writes through the plugin's own functions and the automation logs in wp_fc_meta stay consistent. Bulk operations across a filtered view stay safe because every write goes through the same code path the default UI uses.

FluentCRM made an intentional decision to keep automation state in dedicated tables rather than postmeta, which is exactly why funnels can scale to tens of thousands of enrolments on a single WordPress install. The default automation UI focuses on per-funnel reporting because that is the most common need when building or tuning one automation. The cost is that cross-funnel operational questions are hard to answer in the same screen.

"Which subscribers are stuck on any wait step for more than seven days" and "which lifecycle stages are over-represented in cancellation funnels right now" need a different shape of view. SleekView gives that shape by reading wp_fc_funnel_subscribers with joins, exposing the columns and filters marketers actually want, and routing inline edits through FluentCRM's own enrolment functions so audit logs stay correct. Marketing ops can audit a funnel rebuild in minutes.

Support can resolve an over-eager renewal flow with one click. Lifecycle marketers can find and unstick the rows that quietly drag conversion. The tables are already there, and the schema was always intended to support this kind of work.