Yes. Secure Custom Fields is a fork of ACF that uses the same storage model: a value row plus an underscore-prefixed field-key row in wp_postmeta. SleekAI reads both, so the same Wizard mapping works whether the site runs the WordPress-maintained Secure Custom Fields or the original ACF Free or Pro. Repeaters, groups, flexible content, and options pages all behave the same way.

It uses the underscore-prefixed key pattern that ACF and Secure Custom Fields share. For a field named price, the value lives in postmeta under price and the linked field key lives under _price. The Wizard reads field-group definitions to resolve key to human label, so when the system prompt references price the bot sees the friendly value rather than a raw key identifier.

Yes. Repeater rows are stored as numerically suffixed meta entries, for example ports_0_name, ports_0_count, ports_1_name. The Wizard expands them into an ordered list the model can iterate over, useful for product specs, team bios, pricing tables, and any field group that holds multiple rows of the same shape under a single parent.

Options page values live in wp_options rather than wp_postmeta. SleekAI's Wizard can map options page fields by name, so the bot can quote site-wide settings like a support email, a shipping cutoff time, or a default warranty period that the same field group reuses across hundreds of templates without duplicating the value into each post.

No. SleekAI reads fields on the chat request, not on the initial page render, and the read is a single bounded postmeta query against the mapped keys. The bot widget itself is lazy and only initializes when the visitor opens it. Page LCP and TTFB stay unchanged from the SCF-only baseline regardless of how many fields are mapped.

Yes. Multibot mode runs several chatbots on one site with independent system messages, data sources, and display conditions. A common SCF setup is one bot for the product post type using its spec fields and another for the team post type using bio and credential fields, both coexisting under the same SleekAI install with their own mappings.

Yours. SleekAI is bring-your-own-key, so message costs are billed directly by your provider with no SleekWP markup. Use OpenAI, Anthropic, Google, or OpenRouter, and pick a fast model for routine product questions and a stronger one for complex spec reasoning under the same chatbot without changing the integration.

Yes. Because SleekAI reads postmeta at chat-request time, any field value updated in the editor or via REST API is reflected in the next conversation. There is no embedding step, no vector index to refresh, and no parallel training set. Editors update a spec field and the bot's answers move with the data without a separate sync workflow to coordinate.