It works best with logged-in employees because the bot can pre-fill building, floor, and contact details from user_meta. Guests can still file tickets, but the bot will ask for building and floor explicitly, and any anonymous submission is flagged for a quick sanity check by the duty officer before it routes to a queue.

Yes, that is how the intake works. You define a facilities_request custom post type with the fields you care about, expose a small REST or WP-CLI endpoint, and SleekAI calls it with the validated answers. The ticket appears in the WordPress admin like any other post and slots into your existing edit and assignment workflows.

You map keywords and answer patterns to a priority taxonomy. Words like leak, smoke, locked out, no power, and accessibility trigger P1. Flickering, slow drain, stuck blind, and squeaky door land on P3. The bot can also ask one direct question about safety and impact, then pick a priority and explain its reasoning in the chat so the reporter can challenge it.

Photos and short videos drop straight into the conversation and end up as media attachments on the ticket. The bot summarises what it sees if you enable vision on your chosen model, which lets it suggest a probable category before the technician arrives. Heavy files can be routed to a private upload bucket if you do not want them in the WordPress media library.

Yes. If your asset list lives as posts, postmeta rows, or a custom table, you map those fields into the prompt and the bot can resolve 'the AC in the third-floor conference room' to a specific asset ID. The same mapping powers reporting later, since each ticket carries the asset reference and you can chart failure rates per asset over time.

Routing is driven by issue category and building. Electrical issues in Building C go to the electrical team for that campus; plumbing in the same building goes to plumbing. The bot writes the team assignment as a taxonomy term on the ticket, and your existing notification rules in WordPress, Slack, or email pick it up from there.

Adoption is high because the alternative is a portal form with twelve fields, half of which the employee cannot answer. Chat lets them describe the issue in plain language and have the bot fill in the structure. Most facilities teams see ticket completion rates rise sharply within a month, with the bot capturing tickets that would have been muttered to a colleague and forgotten.

Yes. SleekAI multibot lets you scope a bot by URL pattern, user role, or building taxonomy. A campus in Berlin can have its own bot with German prompts and the local maintenance vocabulary, while the New York campus has its own with the right vendor names. All tickets still flow into the same WordPress install for global reporting.