SleekAI inspects the WordPress user object: user role, capabilities, and any custom user meta. You can also map external signals like a CRM-synced tag, a membership-plugin tier, or a lifetime-spend threshold computed from order history. The bot reads these as variables in the system prompt, so the same conversation flow can branch on tier without forking the bot.

Yes. The cleanest pattern is multibot: a 'concierge' bot scoped to logged-in users with the VIP role, and a 'support' bot for everyone else. Both can share a knowledge base while running different system prompts, models, and presets. Conversation logs stay separate so reporting matches the audience.

Storage lives in WordPress user meta or in your CRM, not inside the chatbot itself. The bot reads those fields as mapped variables and includes them in the system prompt. That keeps the personal data inside systems you already govern, and means a preference change in the CRM shows up in the next conversation without a sync step.

Both. SleekAI supports function-call style actions that trigger webhooks against your booking system, your reservations plugin, or a third-party API. The bot collects the required fields conversationally, confirms before submitting, and logs the resulting confirmation id back into the transcript so there is an audit trail.

Every VIP has a named account manager in our suggested setup. The bot can drop a transcript and a structured request into a Slack channel, email the manager directly, or open a Help Scout conversation tagged with the member's id. The bot tells the member exactly who will follow up and by when.

Concierge work rewards a stronger model. Claude Sonnet 4.5 or GPT-4.1 are sensible defaults because tone, judgement, and refusal behavior matter more than raw cost. For low-stakes lookups you can switch a sub-bot to Haiku or Gemini Flash. SleekAI lets you change model per bot without rewriting prompts.

Conversation logs include every message, the resolved variables, the model, token count, and the timestamp. For compliance-sensitive industries you can also pipe logs into your data warehouse via webhook. That gives legal and ops a defensible record of what the chatbot offered, especially for time-bound perks or upgrades.

The bot handles the boring middle of the conversation: when can I come, do you have my preferred room, is my membership current. Humans take over for the moments that matter: a recovery after a problem, a custom request, a sensitive change. Most VIPs prefer a fast accurate bot for the routine asks and a real person for the rest, rather than waiting twenty minutes for the human to do both.