There is no first-party Freshsales WordPress plugin maintained by Freshworks today. Integration runs through the official Freshsales REST API. SleekAI's data-source wizard can call that API with your API key to read the matched contact's record, or you can route through a community connector that already syncs Freshsales contacts into WordPress and have SleekAI read the local data.

Two paths. A logged-in WordPress user with an email that matches a Freshsales contact loads the matched record automatically. Or a tracking cookie set by a form or a sales tag identifies the contact across visits. When neither signal exists, the bot defaults to a stranger mode with no CRM context exposed.

No, by design. When the bot promises a note, a stage move, or a tag, it triggers a webhook into your automation that uses the Freshsales API to apply the change. That keeps Freshsales the source of truth for deal pipeline and contact records, and prevents a chat from skipping deal-stage validation that your sales-ops team relies on.

Yes. The wizard picks specific properties: first name, deal stage, owner, last activity, deal value, and any custom field. Sensitive internal notes stay out by default. Only the matched contact's own data enters the prompt, so a logged-in contact cannot read another contact's record through the chat.

Yes for read context. SleekAI can pull marketing engagement scores, sales sequences, and recent email opens if those properties are exposed by your Freshsales API token. Practical filtering matters more than feature parity: most teams expose a curated subset rather than the full record so the prompt stays tight and the responses stay relevant.

Inside WordPress, with model name, token usage, page URL, and matched Freshsales contact ID per session. A webhook can also push the full chat back to Freshsales as a contact activity, so reps see the conversation in the CRM timeline without leaving their main workflow.

Yes through a webhook to your sales automation. When the bot has captured enough information (email, intent, company), it fires the create-contact API and the new record lands in Freshsales with a tag identifying it as bot-sourced. Your sales-ops rules then route it to the right owner or sequence.

Treat Freshsales consent and subscription fields like any other CRM read. Filter the matched contact by consent before exposing details in the prompt, and only personalize for contacts who agreed to marketing or sales chat. Anyone without consent gets the stranger bot, with no personal data exposed in the system message.