Carbon Fields is a developer-first framework, registered in PHP rather than a UI. Each field is defined in code with Container::make() and stored in standard WordPress meta tables with an underscore prefix on the meta key, so price becomes _crb_price by default. Containers can attach to post types, taxonomies, users, comments, options, theme options, or widgets, which means Carbon Fields handles almost any extension point a developer reaches for.

That broad storage model usually trips up chatbots. Underscore prefixes are hidden from the admin meta list by WordPress convention, so generic tools assume they do not exist. SleekAI's Wizard knows otherwise. It maps any underscore-prefixed key into a named variable that the chatbot's system message references. The bot can read complex Carbon Fields values like Association fields (which store related post IDs), Map fields (lat and lng plus zoom), and Complex fields (a serialized group of repeating sub-fields). Each value is the live one the developer wrote.

For sites with deep Carbon Fields libraries, push relevant meta plus titles plus permalinks into an OpenAI Files vector store so the model retrieves only matching entries per query. Conversation logs save the question, the matched fields, and the page URL. Developers and editors see which code-defined fields visitors ask about most. That signal often justifies surfacing a hidden field on the template, or retiring a field that nobody uses.

Carbon Fields takes a different route from UI-driven plugins like ACF or Meta Box Lite. Developers register fields in code, version-control the field definitions, and ship the schema as part of the theme or plugin. That makes the schema portable and reviewable, which suits teams that care about CI and reproducibility.

The underscore-prefix storage is the trade-off. Most third-party tools that scan wp_postmeta skip leading-underscore keys by convention, on the assumption that hidden meta is private. Carbon Fields is private only from the WordPress admin UI, not from the database, and certainly not from a chatbot that the team explicitly maps.

SleekAI reads the same keys the developer wrote and answers questions from the live values. Visitors get accurate replies even when the field has no front-end UI. Developers and editors get a quick reference.

Conversation logs become a usage map of the schema. Fields that drive most chat traffic deserve a stronger spot on the template. Fields that no visitor ever asks about can be retired in the next release.

The Carbon Fields code is the source of truth, and SleekAI keeps the chatbot anchored to it without parallel duplication.