Yes, through the Drip API and what the Drip for WordPress integration exposes. SleekAI reads the matched subscriber's email, tags, current workflows, and recent ecommerce events, then injects the fields you select into the bot's prompt. You decide what enters context, so private notes and unrelated tags stay out while shopper-relevant signals flow through.

Two signals. Drip sets a tracking cookie when a subscriber clicks a tracked link in a workflow email, identifying that browser as a known subscriber. Separately, when a WordPress user is logged in and their email matches a Drip subscriber, the record loads. If neither signal is present, the visitor stays anonymous and Drip context never enters the prompt.

It can describe the next step and fire a Drip event through a webhook. Drip owns the actual workflow entry, exit, and email sends, so cadence and consent rules stay enforced. Letting the bot fire workflows directly would bypass entry conditions and risk duplicate emails, which is why SleekAI calls into your existing event listeners instead of emulating them.

Yes, if your Drip account is wired to receive ecommerce events from your store. SleekAI reads the events Drip has stored for the matched subscriber (cart-created, cart-abandoned, order-placed) and includes the relevant ones in the prompt. The bot only sees events for the current subscriber, not your full store volume.

Yes. Use SleekAI's multibot feature with display conditions on Drip tag presence, workflow membership, or logged-in state. A typical setup is one bot for cold shoppers focused on size and shipping questions, plus a second bot for cart-abandoned subscribers that opens with the real recovery code from the workflow email.

Inside WordPress, with full session history, model name, token usage, and page URL per conversation. Store owners review the logs to spot recurring objections, refine the prompt, and feed reusable answers back into the workflow email copy itself. Logs stay on your site; LLM providers only see the request payload at inference time.

Only if you remove the expired code from 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 a code is out of the prompt, the bot stops quoting it, which prevents a stale Tuesday code from being honored a week later.

Yes. Drip's subscriber status and unsubscribed flag are part of the record SleekAI reads. Exclude unsubscribed subscribers from the lookup or strip personalization for that group before exposing tags and workflow history. The bot honors the deliverability and consent rules your workflows enforce, rather than routing around them.