Simple Job Board Pro registers a jobpost custom post type for listings and adds the taxonomies jobpost_category, jobpost_job_type, and jobpost_location for category, employment type, and city or region. Job details live in wp_postmeta under keys like jobpost_salary, jobpost_company_name, jobpost_email, jobpost_expiry_date, and jobpost_apply_url. Applications submitted through the front-end form are stored as a separate post type or table depending on configuration.

SleekAI maps that post type, the three taxonomies, and the meta keys into the chatbot's system message. A visitor asking about senior marketing roles in Berlin gets a filtered answer from real listings, with company name, salary, and how to apply. Single-job pages auto-inject the current listing's data, so the bot already knows what the visitor is reading.

Generic chatbots see jobpost as opaque post data and can't read the taxonomy or salary meta. They invent companies, miss closing dates, and never link to the apply URL. SleekAI's display conditions let an employer-facing bot run on the resume/applicant management screen with a different scope than the visitor-facing bot on the jobs archive.

Simple Job Board Pro is one of the more flexible commercial job board plugins for WordPress, with strong support for resume uploads and front-end submissions. The visitor-facing problem is the same as every other plugin in this category: the data is rich, but the default filters require the seeker to know what they're looking for. A natural-language chatbot fills that gap, but only if it can read the jobpost custom post type, the three taxonomies, and the salary/location/expiry meta.

SleekAI does, by mapping those exact sources into the system message. A seeker asks for senior marketing in Berlin and gets a filtered list from real listings, with company name, salary, and apply URL. On single job pages the bot auto-injects the current listing, so visitor questions get answered without retyping titles.

Employer-side, a separate bot scoped to the admin applicant screen reads applications and resumes for triage queries, completely isolated from the visitor bot. Display conditions and multibot make that separation a single setup step. Token usage stays low because both bots return short factual answers against indexed columns, and bring-your-own-key means HR can pick a cheap model like GPT-4o-mini or Claude Haiku for high-volume use without watching the bill.

Conversation logs show where seekers drop off, which is data the board owner usually never sees.