LeadChat Booker — conversational lead capture that schedules

Real Working Demo https://crmaiinsight.com/leadbot How It Works (High-Level) 1) Chat > Capture LeadBot greets, collects Full Name → Email → Mobile (optional) → Product interest via friendly chat (no forms). - Validates email/phone, confirms inputs, supports corrections. 2) De-dupe Checks Salesforce for an existing lead by Email. - If found → updatelead. If not → createlead. 3) Product Selection Pulls your FeatureProductc list (Name + one-line Description) and lets the user choose by number or name. 4) Demo Booking (Optional) If the user says Yes: - Detect/ask Time Zone (IANA). - Reads Salesforce Events for the next 14 days. - Computes free 30-min weekday slots (09:00–17:00 UTC) strictly after now. - User picks a slot → creates a Salesforce Event (30 min) linked to the Lead. 5) Notifications & Follow-ups - Slack DM to your team (concise summary). - Email confirmation to the prospect (local date/time included). - Ends with a polite confirmation message. --- Setup at a Glance - Effort: Most teams finish the base setup in ~45–90 minutes (credentials, field mapping, test). - What you’ll configure: Salesforce OAuth, SMTP (or your ESP), Slack, OpenAI key, and the web chat widget. > Tip: Start with the provided FeatureProductc object. You can switch to your own product catalog with a few tweaks (see below). --- Prerequisites - Salesforce - Connected App + OAuth (API enabled). - Lead fields: FirstName, LastName, Email, MobilePhone, and one product lookup/text field (e.g., InterestedProductc or FeatureProductc). - (Recommended) Custom object FeatureProductc with fields: Name, Descriptionc, Featuresc, Tagsc. - n8n Credentials - salesforceOAuth2Api (to read/write Leads & Events). - smtp (or use your email provider node). - slackApi (for internal notifications). - openAiApi (for the chat agent). - Widget Embed (optional) - A place on your site/app to embed the chat launcher. --- Step-by-Step Setup 1) Import the flow into n8n - Verify nodes: Chat Trigger → AI Agent → checkduplicatelead → update/create lead → getproducts → getscheduledevents → createdemoevent → Slack/Email. 2) Add/Bind Credentials - Salesforce OAuth: authorize org with API scope. - SMTP: sender, domain, and authentication (verify SPF/DKIM). - Slack: ensure bot can DM users/channels. - OpenAI: drop in your API key. 3) Map Product Field on Lead - Pick one field to store the selection (e.g., InterestedProductc). - Ensure AI Agent and Salesforce nodes reference the same field. 4) (Option A) Use FeatureProductc - Confirm fields exist: Name, Descriptionc (used in the numbered list). - In getproducts, make sure Id is returned; pass it as customFieldsValues0Value. 5) (Option B) Use Your Own Catalog - Swap customObject: FeatureProductc → Product2 (or your object). - Update fields to at least: Id, Name, and a short description field. - Keep the variable contract the same (AI expects to store Id, name, description). 6) Configure Demo Booking - getscheduledevents uses a SOQL search window (today → +14 days). - Ensure your Event permissions allow read/write. - Confirm createdemoevent URL points to your Salesforce domain & API version. 7) Customize Widget (optional) - Set title, brand colors, and initial message in the Chat Trigger options. - Limit reply length (≤100 words) is already set. 8) Test End-to-End - Run a full path: enter name/email/phone, pick a product, select a time slot. - Verify: Lead/Update in Salesforce, Event creation, Slack DM, Prospect Email. --- Switching to Your Own Products (Quick Tweaks) - Replace Data Source: - In getproducts: - customObject: Product2 (or your object API name). - Fields: ensure Id, Name, and a short description are returned. - Update Lead Field Mapping: - Set InterestedProductc (or your chosen field) to the returned Product Id. - Copy Text Logic: - Keep the AI’s “numbered list” output; it supports both number and name replies. --- What Users Experience - No forms. A friendly AI asks one thing at a time, confirms details, and offers a live c