Yes. Groundhogg stores contacts in gh_contacts with metadata in gh_contactmeta, tags in gh_tags, and funnel runs in gh_funnel_events. SleekAI reads them through the standard Groundhogg API and includes the matched contact's data in the bot's prompt. You pick which fields enter the context, so private notes stay out while name, tags, and funnel step flow in.

Through two signals. Groundhogg sets a gh_contact tracking cookie when a tracked email link is clicked, identifying that visitor as a specific contact even if they never log in. Separately, when a WordPress user is logged in and their email matches a Groundhogg contact, the record loads. SleekAI uses whichever signal is available; if neither exists, the visitor stays anonymous.

It can describe what should happen and call a webhook or REST endpoint that lands in a Groundhogg benchmark. Groundhogg owns the actual funnel run, including delays, conditional logic, and email sends. Letting the bot fire emails directly would bypass benchmark logic and risk double-touches, which is why SleekAI guides into a benchmark rather than emulating the funnel itself.

Yes. Pro fields and meta live in the same gh_ tables, so any custom field you add through Pro is readable. The base integration treats core and Pro identically; what differs is what data exists in your install, not what SleekAI can ingest. Pro features like advanced search and 2FA on the contact CRM side do not block the bot's read access.

Yes. Use SleekAI's multibot feature with display conditions on Groundhogg tags or funnel position. A typical setup is one bot for untagged or cold-tagged visitors that focuses on plan education, plus a second bot for warm-lead and customer tags that picks up the funnel and references the contact's actual nurture history.

Inside WordPress with full message history per session. Sales managers review the logs, refine the bot prompt, and feed back the recurring objections to the funnel email copy itself. Logs stay on your server; the LLM provider only sees the request payload at inference time, not a stored copy of the chat history.

Only if you remove the expired code from the prompt. SleekAI does not have a campaign-expiry concept; it answers from whatever is in the system message. The cleanest pattern is to keep an active-offers block in the prompt and rotate it when a campaign ends. The bot only quotes what it sees, so once the code leaves the prompt, it stops appearing in replies.

Yes. Groundhogg's optin status, marketability, and unsubscribed flags are part of the contact record SleekAI reads. Filter the lookup to exclude unsubscribed contacts before exposing CRM context, or strip the personalization for that group. The bot's job is to honor the same deliverability and consent rules your funnels already enforce, not to route around them.