The WP Job Manager Bookmarks add-on lets candidates save jobs and lets employers save resumes, with each bookmark stored against the user and the underlying job_listing or resume post. Candidates and employers ask the same recurring questions: how to unbookmark, how to add notes, why a bookmarked job no longer appears, and which saved jobs are still open versus expired or filled.

SleekAI maps the bookmark table and the parent listing or resume into named variables the system message can reference. The bot can list a candidate's currently saved jobs with their open or expired status, sort them by closing date, and flag the ones that have been filled. For employers, the same pattern surfaces saved resumes with last-updated dates and skill tags from resume_skill.

Generic bots fail because bookmarks are a two-table join: the bookmark row plus the parent post. Without that mapping, the bot answers with a vague paragraph about saving items. SleekAI's data sources make the join a one-time configuration and resolve it at request time, so a candidate's new bookmark or a removed listing is reflected in the next chat.

Bookmarks look like a small feature but they are where engaged candidates and active employers spend a lot of time. A candidate who has bookmarked 12 jobs over a month wants to know which ones are still open, which close this week, and which have already been filled. An employer who has bookmarked 30 candidates over a quarter wants to know who has updated their resume since the last review.

Generic chatbots cannot answer either question because the data lives in a join between the bookmarks table and the parent post. SleekAI does that join via mapped variables and resolves it on every request, so the answers reflect the current state of both the bookmark and the listing or resume. Multibot mode keeps the candidate and employer experiences separate, which matters because the privacy boundaries are sharp.

Conversation logs reveal which clean-up flows repeat, which is usually a sign the dashboard UI needs to make those flows more obvious. Bring-your-own-key keeps a routine feature cheap to operate.