Wherever you store it today. Most teams keep PDFs in the WordPress media library or a private S3 bucket and store the URL on each guide CPT. The bot reads that URL field at conversation time and either renders a public link, a signed S3 URL, or a magic-link redirect that requires confirming the email.

Yes. Configure the delivery step to send a confirmation email through your ESP instead of returning the link directly. The bot still acknowledges in chat and explains that the link is on its way. The advantage over a generic modal is that you can also queue a polite nudge in the same chat if the email seems to have gone to spam.

Yes. SleekAI fires a webhook with the captured email, requested guide, tags, and any other variables you collect. Native or near-native paths exist for Mailchimp, ConvertKit, Brevo, HubSpot, ActiveCampaign, and any tool that accepts a JSON POST. The same payload is also written to a WordPress lead post so the data survives even if the ESP webhook fails.

Each guide CPT has fields for topic, audience, and reading level. The system prompt is generated from the live library at request time, so a visitor asking about a topic that has no matching guide gets a candid "we do not have a guide on that yet" answer instead of a hallucinated recommendation. Conversation logs surface those gaps so editorial can prioritize the next asset.

The same flow works for video, Notion docs, Airtable views, private repo invitations, or templates served from a CDN. The delivery step is just a URL or a webhook, so as long as the asset has an addressable endpoint, the bot can hand it over in chat and tag the lead in your CRM accordingly.

In practice yes, more than a modal, because the bot has already shown competence by recommending a specific asset. The capture step feels like a continuation of the conversation rather than an interruption. Conversion rates from our customers' A/B tests typically land 20 to 40 percent above the equivalent modal on the same content.

Yes. Add a question about role, company size, or use case before the email request and the bot can route a freelancer to a free guide and an enterprise prospect to a sales-led conversation with the same library. The qualification fields write to the lead record, so sales sees a richer profile than a bare email capture.

By default the lead sees only their current session. The admin sees the full transcript next to the lead record, with the requested guide, the matched topic tags, and any handoff signals. Most teams use those transcripts to refine the library over time, dropping guides that are never requested and commissioning new ones for the topics the bot keeps having to decline.