AWP Classifieds (formerly AWPCP) stores listings in a custom table, traditionally wp_awpcp_ads, and links each ad to fee plans, regions (via the Regions module), and image uploads. Categories live as a custom taxonomy. Listing fields include title, contact name, city, state, country, ad price, posted date, expiry, plan ID, and whether the ad is featured. With the Extra Fields module, additional custom fields per category get stored alongside.

SleekAI maps the awpcp_ads rows, the category taxonomy, and the fee-plan and region tables into the chatbot's system message. A buyer asking for cars under $10k within 25 miles of a ZIP code gets a filtered answer pulled from real rows, including image previews and contact channel (blind email or direct). On single ad pages the current listing's data is auto-injected.

Generic chatbots can't read the custom awpcp_ads table at all because it lives outside wp_posts. They miss every listing on the site, hallucinate fake ads, or refuse to answer. SleekAI's data mapper supports arbitrary tables, so AWPCP's storage model is a first-class source, not a workaround.

AWP Classifieds is one of the longest-running classifieds plugins on WordPress, with a quirk that throws off most modern AI tools: listings live in a custom table outside wp_posts. A generic chatbot reads wp_posts and finds nothing, so it either refuses to answer or hallucinates ads that don't exist. SleekAI's data mapper supports arbitrary tables as first-class sources, so awpcp_ads, the Regions module table, and the fee-plan table all get mapped into the system message.

Buyers asking for used Hondas under $10k near a ZIP get a filtered answer from real rows, with prices, locations, and posted dates pulled live. The Extra Fields module's category-specific custom data comes along too, so questions about transmission, bedrooms, or any other custom field work without custom code. Featured ads get surfaced first when relevant, giving paying sellers the boost they paid for.

The blind email system stays intact because the bot points buyers to Contact seller on the listing instead of leaking addresses. Display conditions let a poster-side bot run separately on the user dashboard for plan and expiry questions, fully isolated from the public bot. Token usage stays low because most queries are short factual reads against indexed columns.

Bring your own OpenAI, Anthropic, Google, or OpenRouter key and a small classifieds operator pays nothing extra for a chatbot that actually knows the catalog.