SliceWP stores its program data in custom tables prefixed with slicewp_. The slicewp_affiliates table holds the affiliate record with status and rate, slicewp_commissions captures each earning with status flags like pending, unpaid, and paid, and slicewp_visits tracks every click attributed to an affiliate ID. SliceWP also stores per-affiliate rates and payout details in companion tables and options. SleekAI maps those rows through its data-source wizard so the system message exposes the current affiliate's slug, balance, and recent activity as variables resolved at request time.

That changes how affiliates use the program page. When a logged-in affiliate asks how much they have earned this month, the bot reads slicewp_commissions filtered by their ID and a date range and quotes the real total. When they ask why a visit did not turn into a sale, the bot reads slicewp_visits for the matching click and explains attribution. When they ask which payout method is on file, the bot reads the affiliate record without exposing sensitive credentials.

Display conditions keep the support bot scoped to the affiliate role, multibot lets a separate signup bot answer commission and cookie questions on the public program page, and conversation logs capture each question with model and token use so program managers tighten the prompt or the dashboard copy as common questions surface.

A SliceWP program is built on per-affiliate trust. The questions that drive churn out of the program are concrete and personal. How much did I make this month.

Why is this one commission still pending after three weeks. What is my actual rate today. A generic widget bolted onto the affiliate dashboard cannot see slicewp_commissions, has no idea who is logged in, and will cheerfully invent a payout window that doesn't match what the program manager set.

That single wrong number is the start of a thread on Twitter that pulls top performers somewhere else. SleekAI flips the dynamic. The bot reads the same tables the dashboard reads, so the answers it gives match the numbers the affiliate already sees.

Earnings questions resolve in seconds, attribution disputes get explained against the actual cookie window the program runs, and tier nudges happen with real gaps instead of guessed percentages. Program managers stop fielding the same five questions over and over and start using the log to tune the program copy, the creative library, and the cookie length. Marketing teams see which links pull, which categories pay, and where the conversion gap actually lives.

Because SleekAI never writes to SliceWP's tables, the plugin stays the source of truth, payouts run through SliceWP's batch, and audits hold. The chatbot guides while the program executes. Combined with multibot, the same install pitches prospects on the public program page and supports active affiliates inside the dashboard, all on an LLM key the program owner pays for directly.

That is why programs outgrow rented widgets.