Yes, through the Omnisend API and what the WordPress integration exposes. SleekAI reads the matched contact's segments, lifecycle stage, custom properties, and recent automation activity, then injects the selected fields into the prompt. You decide what enters context, so unrelated properties and notes stay out while shopper-relevant signals flow in.

Two signals. Omnisend sets a tracking cookie when a contact clicks a tracked link in an email or SMS, identifying that browser as a known contact. Separately, logged-in WordPress users whose email matches an Omnisend contact load automatically. If neither signal is present, the visitor stays anonymous and no Omnisend context enters the prompt.

Indirectly. The bot can describe the next step and fire a webhook that triggers an Omnisend custom event, which then drives the automation. Omnisend owns the actual channel selection and message send, so cadence and consent stay enforced. Letting the bot send messages directly would bypass those rules, which is why SleekAI calls into your event listeners instead.

Yes, if your Omnisend account uses those channels. SleekAI reads which channel last reached the contact and which message triggered the click. The prompt can match the chat to the channel, so a shopper arriving from an SMS sees a bot that references the SMS code, not a different campaign that went out by email.

Yes. SleekAI's multibot feature runs separate bots with their own prompts and display conditions on the same install. A typical setup is a public bot for cold traffic focused on shipping and size questions and a recovery bot for cart-abandoner segments that opens with the real recovery code from the last Omnisend message.

Inside WordPress, with full session history per chatbot, model name, token usage, and page URL. Store owners review the logs to spot recurring objections, refine the prompt, and feed common answers back into automation copy. Logs live on your site; the LLM provider sees only the request payload at inference time.

Only if the code is still in the prompt. SleekAI answers from whatever is loaded into the system message. Keep an active-offers block in the prompt and rotate codes as recovery windows end. Once the code is out of the prompt, the bot stops offering it on the next request.

Yes. Omnisend's email and SMS consent flags are part of the contact record SleekAI reads. Exclude non-consented contacts from SMS-channel context or strip channel-specific personalization for that group. The bot honors the consent rules your automations already enforce, not the other way around.