Yes. FluentCRM stores its data in custom tables (fc_subscribers, fc_subscriber_pivot, fc_lists, fc_tags, fc_campaigns, fc_funnels, fc_funnel_subscribers and a handful of supporting tables). SleekView queries them directly, joining fc_subscriber_pivot for list and tag columns and fc_subscriber_meta for typed custom fields.

Yes. Custom fields are stored in fc_subscriber_meta. SleekView pivots them into typed columns so date, currency and select fields render natively. The agent samples meta keys present in your install so column setup picks from a real list instead of guesswork.

Yes. SleekView writes through FluentCRM's CRUD layer where supported, so adding a tag fires the corresponding fc_funnels automation trigger, changing status updates the contact log, and list membership changes propagate through fc_subscriber_pivot the same way the contacts screen handles them.

Yes. Subscriber, list, tag and campaign views work identically on both free and Pro because the same fc_subscribers, fc_lists and fc_campaigns tables back both versions. Funnel-enrolment views depend on fc_funnels and fc_funnel_subscribers which FluentCRM Pro populates, so the automation angle needs the Pro license.

Yes. Join fc_campaign_emails to fc_subscribers on subscriber_id and filter by campaign_id and event_type (opened, clicked, unsubscribed). The resulting view lists every contact who opened a specific broadcast, with the standard subscriber columns alongside the engagement context.

Yes. FluentCRM Pro indexes fc_subscribers on email, status, type and timestamp columns the automation engine queries during sends. SleekView reuses those indexes for filters and sorts, and pagination is keyset where the table allows it. Large bases render and filter in well under a second.

Yes. SleekView supports multi-axis joins, so a subscriber view can show comma-separated tag and list columns from fc_subscriber_pivot with each one independently filterable. "Pro list and VIP tag and status subscribed" is one saved view, not three nested filter clicks.

No. The default FluentCRM admin stays where it is for marketers who like its inbox-style UI. SleekView adds a row-level admin surface for the operations that work better as a sortable, filterable, inline-editable table. The two coexist on the same fc_subscribers tables without conflict.