> For the complete documentation index, see [llms.txt](https://docs.talkfurther.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.talkfurther.com/integrations/crm-integrations/salesforce.md). # Salesforce The **Salesforce CRM integration** is by default a one-way sync between Further and Salesforce, where Further pushes Leads (and optionally message/phone tasks). Custom development via your CSM can be done to create a bi-directional exchange. *** ### CRM Integration Support The **Salesforce** integration supports: * **Lead Push** * Push leads from Further sources (VSA, phone, web forms, chat). * **Activities Push (not by default)** * Push in SMS, messaging, and phone activity as **Tasks**, with configurable subjects, activity types, and subtypes for reporting * **Activities Pull (not by default)** * Further can implement tour pulling per client for scheduled/completed tours * **Move-In Data (is this done by default?)** * Pull in move-in events from Salesforce. * Enables complete analytics from **first click → lead → activity → move-in**. *** ### Configuration Options The Salesforce integration offers flexible configuration options: * **Activities Push** * Push in SMS, messaging, and phone activity as **Tasks**, with configurable subjects, activity types, and subtypes for reporting * **Activities Pull** * Further can implement tour pulling per client for scheduled/completed tours * **Move-In Data (is this done by default?)** * Pull in move-in events from Salesforce. * Enables complete analytics from **first click → lead → activity → move-in**. * **Mapping Rules** * **"Who is this for" Map** - based on VSA question * **Care Type Map** – map selected care type into Salesforce (e.g., IL, AL, MC). * **Lead Score Map** – push Further’s lead score into Salesforce's lead score field (either a mapped grade or raw digital score). * **Call Tracking Metrics Map** - Further’s native Salesforce integration can pass CTM attribution (campaign, referring webpage, paid search keyword, landing page, and Google Ads click ID) directly into custom Lead fields --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.talkfurther.com/integrations/crm-integrations/salesforce.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.