# Phenoble Software > Phenoble is the AI-native Salesforce partner for real estate. We implement Salesforce and Agentforce for brokerages, property developers, and property managers across the US, GCC, and India: faster lead-to-close, lower cost per transaction, and AI scoped to pay for itself. 40+ implementations, AppExchange 5.0 rating. Content may be cited and summarized with attribution to Phenoble Software (phenoble.com) under CC BY 4.0. ## About Phenoble Software Pvt Ltd is a Salesforce consulting partner specializing in real estate on Salesforce, delivered AI-native with Agentforce, Data Cloud, and the real estate ISV stack (AscendixRE, REthink). We hold 30+ certifications across 7 certified professionals and serve clients in the US, GCC, and India, with select work in financial services, healthcare, and manufacturing. ## Industries - [Real Estate](https://phenoble.com/industries/real-estate): Salesforce for CRE brokerages (deal and listing pipeline, commission and GCI tracking, AscendixRE and REthink), property developers in India and the GCC (lead-to-booking, unit inventory, channel partners, WhatsApp, RERA and DLD context), and property management (work orders, tenant experience, Agentforce service agents). - [Financial Services](https://phenoble.com/industries/financial-services): Agentforce + Financial Services Cloud for banks, wealth managers, and insurance firms. - [Healthcare & Life Sciences](https://phenoble.com/industries/healthcare): HIPAA-aware Agentforce and Health Cloud implementations. - [Manufacturing](https://phenoble.com/industries/manufacturing): ERP integration, field service automation, and CPQ with Agentforce. - [Retail & Consumer Goods](https://phenoble.com/industries/retail): Unified shopper profiles with Data Cloud, plus Agentforce agents for order status, returns, and personalization. - [Information Technology](https://phenoble.com/industries/information-technology): Agentforce for software companies, MSPs, and IT services firms: support triage, renewals, and CPQ quoting. ## Services - [Agentforce for Real Estate Operations](https://phenoble.com/services/agentforce): 24/7 lead qualification, listing inquiry, lease document intelligence, and tenant service agents, scoped with fixed pilots and defined resolution metrics. - [Data Cloud & Integration](https://phenoble.com/services/data-cloud): Unified data platform implementation connecting CRM, ERP, and marketing data sources. - [Agentforce Contact Center](https://phenoble.com/services/agentforce-contact-center): AI-powered contact center automation using Agentforce and Service Cloud Voice. - [Agentforce Pilot and Launch](https://phenoble.com/services/seven-day-agentforce): Fixed-price Agentforce packages. Pilot $1,500 (7 days, sandbox, one topic, scripted tests). Launch $4,500 (2 weeks, production, up to three topics, 30 days of fixes). Implementation only; licenses from Salesforce. - [Phenoble Agent](https://phenoble.com/ai/salesforce): Our own AI assistant product for Salesforce: conversational querying of org data, dashboards, role-based access, and token tracking. A product page, not a consulting service. - [Salesforce Development](https://phenoble.com/services#salesforce-development): Custom Apex, LWC, and integration development for complex Salesforce orgs and PropTech products. - [Strategy & Advisory](https://phenoble.com/services#strategy-advisory): Salesforce roadmap planning, org health assessments, and AI readiness reviews. - [Real Estate Salesforce Quickstart](https://phenoble.com/services#quickstart): Fixed-scope Sales Cloud or Service Cloud implementation for one real estate team, from $8,000. - [Pricing](https://phenoble.com/pricing): Every fixed price on one page: free Real Estate AI Audit, Agentforce Pilot $1,500, Agentforce Launch $4,500, Real Estate Salesforce Quickstart from $8,000, retainers $1,800 to $6,500 per month, custom development scoped per project. Implementation only; licenses from Salesforce. - [Managed Services & Support](https://phenoble.com/services#managed-services): Bronze ($1,800/month), Silver ($3,500/month), and Gold ($6,500/month) retainers for ongoing administration, prompt optimization, and new agent capability rollouts. - [ServiceNow ITSM Implementation](https://phenoble.com/services/service-now): ServiceNow ITSM and Salesforce integration for incident, problem, and change management automation. ## Resources - [Blog](https://phenoble.com/blogs): 120+ Salesforce tutorials and Agentforce guides. - [Case Studies](https://phenoble.com/case-studies): Client results and implementation success stories, real estate first. - [Real Estate AI Readiness Assessment](https://phenoble.com/resources/real-estate-ai-assessment): Free interactive 10-question assessment that scores a real estate business's AI readiness out of 20 and returns a personalized gap list. - [Real Estate AI Readiness Guide](https://phenoble.com/resources/real-estate-ai-guide): Free PDF checklist for brokerages, developers, and property managers preparing Salesforce for AI. - [Agentforce Readiness Guide](https://phenoble.com/resources/agentforce-readiness-guide): Free PDF guide for organizations evaluating Agentforce. - [llms-full.txt](https://phenoble.com/llms-full.txt): Full text of the commercial pages, case studies, and evergreen guides in one plain-text file. ## Company - [About Us](https://phenoble.com/about): Team, certifications, and company background. - [Salesforce Company in India](https://phenoble.com/salesforce-company-india): Trusted Salesforce consulting company in India specializing in real estate; 30+ certifications, 5.0 on AppExchange and Google, senior-led delivery for India, US, and GCC clients. - [Salesforce Company in Jaipur](https://phenoble.com/salesforce-company-jaipur): Salesforce company headquartered in Jaipur, Rajasthan; office address, contact details, and services delivered from the Jaipur hub. - [Careers](https://phenoble.com/career): Current openings are internships: Sales and Digital Marketing, Graphic Design, and Salesforce. Open applications accepted year round. - [Contact](https://phenoble.com/contact): Book a free 30-minute Real Estate AI Audit. US East mornings are live team hours; coverage windows are agreed per engagement. A 24/7 AI sales agent answers +1 (720) 915-9211 and explains Phenoble's offerings. - [Website](https://phenoble.com) - [AppExchange Listing](https://appexchange.salesforce.com/appxConsultingListingDetail?listingId=d6d7fe0e-62e3-46a9-95bf-16309f0d25ff) - [YouTube](https://www.youtube.com/@Phenoble) --- # Full content This file expands llms.txt with the full text of Phenoble's commercial pages, case studies, and evergreen guides. Content may be cited and summarized with attribution to Phenoble Software (phenoble.com) under CC BY 4.0. ## Real Estate (lead practice) URL: https://phenoble.com/industries/real-estate AI-Native Salesforce for Real Estate. Salesforce and Agentforce for brokerages, property developers, and property managers: listings, bookings, and work orders on one system. No AI agent ships until it is scoped to pay for itself. ### Salesforce for CRE Brokerages (US Commercial Real Estate) Phenoble implements Salesforce for mid-market CRE brokerages, 20 to 500 agents, that need deals and listings on one system instead of spreadsheets and inbox threads. We have delivered on the real estate ISV stack, AscendixRE, REthink, and Propertybase, not just core Sales Cloud. - Deal and Listing Pipeline: Listings, deals, and comps as first-class Salesforce objects with stage gates your brokers actually follow. Built on AscendixRE, REthink, or Propertybase where a managed package fits, custom objects where it does not. - Commission Tracking and GCI: Commission splits, GCI reporting, and agent production dashboards inside Salesforce, so the back office stops reconciling spreadsheets at month end. - Back-Office Integrations: MLS and RESO-standard listing data, accounting, and e-signature connected to the org, so a closed deal is entered once, not three times in three systems. - TCPA-Aware Outreach: Campaigns and dialer integrations configured with consent tracking, so prospecting scales without compliance exposure. ### Lead-to-Booking for Property Developers (Property Developers) For property developers, Phenoble builds one funnel from portal lead to booked unit to handover, with channel partners managed and attributed instead of leaking inventory. - Lead-to-Booking Funnel: Portal, walk-in, and channel partner leads scored and routed in minutes, with every unit hold, booking, and cancellation tracked back to its source. - Inventory and Unit Management: Towers, floors, and units modeled in Salesforce with live availability, pricing, and hold expiry. No more double-booked units at launch. - Channel Partner Management: Partner registration, lead attribution, and payout tracking on one system, so channel disputes stop consuming your sales leadership. - WhatsApp Integration: WhatsApp as a first-class channel for site visit scheduling, document collection, and post-sales updates, connected to the Salesforce record. - RERA-Compliant Reporting (India): Project and receivables reporting aligned to RERA disclosure requirements, generated from live CRM data instead of quarter-end scrambles. - Escrow and DLD Context (Dubai): Booking and payment milestone tracking structured around Dubai escrow account rules and DLD registration steps, so finance and CRM finally agree. ### Service Operations for Property Managers (Property Management) Phenoble puts work orders, tenant requests, and renewals on Service Cloud, with Agentforce service agents handling the routine volume your team should not. - Case and Work-Order Flows: Tenant requests become cases with SLAs, vendor dispatch, and cost tracking, from first report to closed work order. - Lead-to-Lease Pipeline: Inquiry to application to signed lease on one pipeline, with owner and unit context attached at every step. - Tenant Experience: Self-service portals and proactive status updates, so tenants stop calling to ask what happened to yesterday's ticket. - Agentforce Tenant Service Agents: A tenant service agent that resolves routine requests 24/7, logs work orders, and hands complex cases to your team with full context. Scoped to defined resolution metrics before it ships. ### Offers and pricing - Real Estate AI Audit: A free working session on your pipeline, data readiness, and where an AI agent pays for itself first. You leave with a scoped pilot plan whether or not you hire us. Price: Free. - Real Estate Salesforce Quickstart: Fixed-scope Sales Cloud or Service Cloud implementation for one real estate team: core objects, pipeline, reporting, and training. Price: From $8,000. - Managed Services Retainers: Bronze, Silver, and Gold retainers for admin, development, and release management, with senior-led delivery and defined response times. Price: Bronze $1,800 · Silver $3,500 · Gold $6,500 per month. - Custom Development: Apex, Lightning Web Components, and integrations for PropTech products and complex org requirements. Estimated per scope, senior-led. Price: Scoped per project. ### AI That Has to Pay for Itself The next decade of real estate belongs to firms whose systems act, not just record. Most AI projects still miss their ROI targets, so ours are scoped differently: data first, fixed pilots, and a metric we commit to before we build. - 01 Data Readiness Check: We audit your listing, lead, and transaction data before any AI work. If the data will not support an agent yet, we tell you and fix that first. - 02 Fixed-Scope Pilot: One agent, one workflow, a defined resolution metric, and a fixed price. No open-ended AI programs. - 03 Senior-Led Build: Objects, automations, integrations, and the agent itself, built and tested against real scenarios from your pipeline. - 04 Measure and Expand: We report against the metric we committed to. Expansion happens because the pilot paid for itself, not because a roadmap said so. ### Real estate FAQ Q: Do you work with AscendixRE, REthink, or Propertybase? A: Yes. Phenoble's team has hands-on delivery experience with the real estate ISV stack on Salesforce, including AscendixRE, REthink, and Propertybase, alongside core Sales Cloud, Service Cloud, CPQ, and custom Apex and LWC. We recommend a managed package when it fits your brokerage and custom objects when it does not. Q: What does the free Real Estate AI Audit include? A: A 30-minute working session with a certified Salesforce architect covering three things: where leads leak in your current pipeline, whether your listing and transaction data is ready for AI, and which single workflow an agent should automate first. You leave with a scoped pilot plan, including a fixed price and a resolution metric, whether or not you hire Phenoble. Q: What does a real estate Salesforce implementation cost with Phenoble? A: The Real Estate AI Audit is free. The Real Estate Salesforce Quickstart, a fixed-scope implementation for one team, starts at $8,000. Managed services retainers run $1,800 (Bronze), $3,500 (Silver), and $6,500 (Gold) per month, and the Agentforce Pilot is $1,500 for 7 days in your sandbox ($4,500 for the 2-week production Launch). Custom development is estimated per scope. Q: We are skeptical of AI ROI. How do you scope Agentforce so it pays off? A: Most AI projects on Salesforce miss their ROI targets, so we scope differently: a data readiness check first, then a fixed-scope pilot with a defined resolution metric, such as the share of inquiries qualified without a human touch. If a pilot cannot be measured, we do not propose it. Q: Can you support US business hours from India? A: Yes. US East mornings are live working hours for our delivery team, so you get real overlap for standups and escalations, plus overnight progress on the backlog. Q: Do you understand RERA and DLD requirements? A: We build reporting aligned to RERA disclosure requirements for Indian projects and structure booking and payment tracking around Dubai escrow account rules and DLD registration steps. Your legal and finance teams remain the authority; the CRM stops being the bottleneck. Q: How fast can a brokerage or developer go live? A: The Real Estate Salesforce Quickstart is fixed scope by design, and our Agentforce Pilot proves a working agent in your sandbox in 7 days. Exact timelines depend on data readiness, which we check before we commit to a date. ## Other industries (select work) ### Financial Services & FinTech URL: https://phenoble.com/industries/financial-services Turn Compliance Into a Competitive Advantage. Phenoble architects secure, compliant AI agents for banks and wealth management firms using Financial Services Cloud (FSC) and Data Cloud. Automate KYC, onboarding, and service workflows without risking data sovereignty. Phenoble implements Salesforce Agentforce and Financial Services Cloud for banks, wealth managers, and insurance firms: autonomous AI agents for KYC, compliance workflows, and client service that respect your security boundaries. Modern financial institutions need speed; we close the execution gap without adding compliance risk. Challenges we address: - Manual Wealth Ops: Advisors lose significant time manually compiling meeting prep and generating portfolio reports instead of advising clients. - KYC & Compliance Bottlenecks: Account opening processes are delayed by manual document verification spread across fragmented back-office systems. - Siloed Client Data: Mortgage, retail banking, and wealth data sit in separate databases, preventing cross-selling and unified client experiences. How Phenoble approaches it: - Autonomous FSC Service Agents: Deploy Agentforce on Financial Services Cloud to instantly resolve Tier-1 inquiries (balance checks, wire statuses, account lookups) while remaining fully within enterprise security boundaries. (Impact: Faster Tier-1 Resolution) - Agentic Account Onboarding: Automate KYC document extraction and risk scoring using AI. Agents interact with clients directly via portal to collect missing documents and push completed cases to compliance review. (Impact: Faster KYC Onboarding) - Unified Financial Graph (Data Cloud): We use Data Cloud to unify retail banking and wealth profiles, triggering proactive alerts when clients hit major life events (mortgage payoff, inheritance, retirement), enabling your advisors to reach out at exactly the right moment. (Impact: Proactive Cross-Sell Signals) Capabilities: - Compliance-Aware AI: Every Agentforce action is logged to the Einstein Trust Layer with FSC-specific guardrails. Audit trails are automatically generated for every AI decision. - KYC Document Agents: Autonomous agents extract identity documents, run sanctions screening, and flag high-risk applicants for human review, compressing onboarding from weeks to days. - Portfolio AI Summaries: We build agents that generate personalized meeting prep summaries by pulling holdings, activity, and market data directly from FSC into a concise brief. - Life Event Triggers: Using Data Cloud identity resolution, we configure automated alerts when a client hits a major life event, triggering proactive advisor outreach workflows. - Data Sovereignty Controls: Agents operate within strict data residency boundaries. We configure field-level security and role-based AI access so agents only see what they're permitted to. - Client 360 for Teams: Advisors and bankers share a unified client view. When a retail banking customer shows wealth potential, the system flags a cross-sell opportunity automatically. FAQ: Q: Is Agentforce compliant with financial services regulations? A: Yes. Agentforce runs natively on the Salesforce Einstein Trust Layer, which provides data masking, audit trails, and zero-retention guarantees for LLM calls. We configure Financial Services Cloud to meet SOC 2 and GLBA requirements specific to your institution. Q: Can Agentforce integrate with our core banking system? A: Yes. We build custom Apex-backed Actions that connect Agentforce to core banking platforms, loan origination systems, and wealth management tools via REST or SOAP APIs, allowing agents to retrieve and update records in real time. Q: How long does a Financial Services Cloud + Agentforce implementation take? A: A focused engagement scoped around a single AI agent (e.g. KYC automation or client onboarding) typically runs 6 to 10 weeks. Broader FSC implementations with multiple agent workflows range from 14 to 20 weeks. Q: Can AI agents handle KYC document review workflows? A: Agentforce agents can orchestrate KYC workflows, prompt clients to submit missing documents, run risk scoring logic, and route completed cases to human compliance reviewers, dramatically reducing manual processing time. Real estate is Phenoble's lead practice. Financial services is select work we take when Financial Services Cloud depth and compliance discipline are the deciding factors. ### Healthcare & Life Sciences URL: https://phenoble.com/industries/healthcare Deliver Better Outcomes with Autonomous Healthcare AI. Empower your care teams by automating triage, scheduling, and patient engagement using Salesforce Health Cloud and HIPAA-aware Agentforce deployments built for clinical compliance. Phenoble implements Salesforce Agentforce and Health Cloud for health systems and life sciences firms: HIPAA-aware AI agents for patient triage, scheduling, and engagement. The technology should support the caregiver, not burden them; we use AI to remove administrative roadblocks and restore focus to patient care. Challenges we address: - Clinical Staff Burnout: Intake coordinators and nurses spend excessive hours handling routine scheduling, insurance FAQs, and referral follow-ups instead of patient care. - Fragmented Patient 360: EHR data, insurance claims, and communication history are entirely disconnected, causing friction in care delivery and duplicated tests. - Slow Care Coordination: Manual referral management and pre-authorization workflows delay critical treatments and erode patient satisfaction scores. How Phenoble approaches it: - HIPAA-Aware Triage Agents: We deploy Agentforce agents connected to Health Cloud to automatically handle appointment rescheduling, basic symptom routing, and facility FAQs, all within strict HIPAA guardrails. (Impact: Faster Inbox Resolution) - EHR + Data Cloud Unification: By integrating Epic or Cerner via MuleSoft into Salesforce Data Cloud, we give care teams a real-time unified patient view, enabling proactive outreach and eliminating chart chasing. (Impact: True Unified Patient 360) - Automated Care Pathways: We design workflows where AI agents trigger post-discharge follow-ups via SMS, monitor patient-reported outcomes, and escalate directly to human nurses only when risk factors are detected. (Impact: Proactive Care Gap Alerts) Capabilities: - Pre-Visit Triage: AI agents chat with patients before appointments to collect chief complaints, verify insurance, and surface relevant history to the care team before the visit. - HIPAA-Aware Interactions: Every agent interaction respects minimum necessary standards. PHI is only surfaced when directly relevant to the patient's current care context. - Remote Monitoring Alerts: Data Cloud ingestion from RPM devices triggers automated check-in workflows when vital signs drift outside thresholds, before a crisis occurs. - Prior Auth Automation: We build agents that draft prior authorization requests by pulling clinical notes and procedure codes, reducing the manual lift for care coordinators. - Referral Follow-Up Agents: Autonomous agents track open referrals, remind patients of pending specialist appointments, and alert care coordinators when referrals go unfulfilled. - Clinical Note Drafting: Post-visit, Agentforce drafts summary notes structured to your specialty templates, reducing documentation time and improving EHR completeness. FAQ: Q: Is Agentforce HIPAA-compliant? A: Agentforce operates within Salesforce's HIPAA-eligible infrastructure. We configure Health Cloud with the Einstein Trust Layer to enforce zero-retention on PHI in LLM calls, implement audit trails, and sign BAAs as required. Every deployment follows our HIPAA configuration checklist. Q: Can Agentforce automate patient scheduling and triage? A: Yes. Agentforce agents can handle appointment scheduling, insurance FAQs, referral follow-ups, and symptom triage within defined clinical guardrails. The agent escalates to clinical staff for anything outside its defined scope. Q: How does Agentforce integrate with EHR systems like Epic or Cerner? A: We build custom Apex Actions that connect Agentforce to EHR APIs, allowing agents to read relevant patient context (appointment history, care plans) without storing PHI in the LLM context window beyond the session. Q: How long does a Health Cloud + Agentforce implementation take? A: A focused patient engagement agent (scheduling, FAQs, referrals) typically takes 6 to 10 weeks. Full Health Cloud implementations with multiple agents and EHR integrations range from 14 to 20 weeks depending on complexity. Real estate is Phenoble's lead practice. Healthcare is select work we take when Health Cloud experience and HIPAA-aware delivery are the deciding factors. ### Manufacturing & Distribution URL: https://phenoble.com/industries/manufacturing Connect the Factory Floor to Autonomous Sales. Phenoble helps manufacturers deploy Salesforce Manufacturing Cloud and Agentforce to automate B2B quoting, integrate ERPs, and deflect logistics inquiries, so your sales team can focus on closing. Phenoble implements Salesforce Agentforce and Manufacturing Cloud for manufacturers and distributors: AI agents for B2B quoting, ERP-integrated order visibility, and logistics inquiries. The biggest bottleneck in manufacturing sales isn't demand, it's fragmented data; we automate the middle layer so your team sells at market speed. Challenges we address: - Slow, Manual Quoting: Complex RFQs take days to process due to disconnected ERP systems and volatile raw material pricing, causing lost deals and frustrated buyers. - Logistics Blockers: On one B2B metals marketplace we worked with, reps spent 60% of their day answering tier-1 tracking, shipping, and BOL questions instead of closing deals, a pattern we see across manufacturing sales teams. - Siloed Operations: Order management, sales CRM, and supply chain data live in completely separate databases, preventing cross-department visibility and accurate forecasting. How Phenoble approaches it: - Instant AI Quotations: Connect Agentforce to real-time spot market APIs and ERP data via Data Cloud so agents instantly analyze negotiated tiers, inventory levels, and raw material costs to generate valid quotes in seconds instead of days. This is the exact fix we shipped for a B2B metals marketplace: quote turnaround dropped from 48 hours to under 3 seconds, and win rates rose 27%. (Impact: 48hrs to 3sec, verified case study) - Autonomous Service Portals: Deploy an Agentforce service bot directly in your B2B commerce portal to autonomously retrieve BOLs, resolve tracking issues, and process basic returns, without touching human support. On the same metals marketplace project, this deflected half of all inbound tier-1 support requests. (Impact: 50% case deflection, verified case study) - Manufacturing Cloud Visibility: Unify run-rate forecasting and actual order volume using Salesforce Manufacturing Cloud, giving leadership a unified view of inventory, demand, and pipeline accuracy across all channels. (Impact: Unified Demand-vs-Capacity View) Capabilities: - Instant Quote Generation: Agents pull live ERP pricing, inventory levels, and BOM data to generate RFQ responses in seconds, not days. No more lost deals to slow turnaround. - Logistics & Tracking Agents: B2B buyers ask the portal chat agent for shipment status, BOL downloads, and delivery ETAs. Agents pull directly from your logistics APIs to resolve without human involvement. - Inventory Auto-Replenishment: When Data Cloud detects inventory falling below reorder thresholds, agents trigger purchase orders and alert account managers, closing the supply loop automatically. - Production Status Updates: Agents give real-time production run updates to customer-facing teams, eliminating the back-and-forth between sales, ops, and the plant floor. - Demand Forecasting: We unify Sales Cloud pipeline data with Manufacturing Cloud run rates to give leadership a live demand-vs-capacity view for smarter production planning. - Distributor Self-Service: Your distributor network gets a 24/7 AI agent for order management, credit checks, and returns processing, reducing distributor support overhead dramatically. FAQ: Q: Can Agentforce integrate with our ERP like SAP or NetSuite? A: Yes. We build custom Apex Actions that connect Agentforce directly to SAP, NetSuite, Oracle, and proprietary ERPs via REST or SOAP APIs. Agents can retrieve inventory levels, pricing rules, and order status in real time to generate accurate quotes and resolve logistics inquiries. Q: How does Agentforce speed up the RFQ process? A: Agentforce agents can process incoming RFQ emails or portal submissions, pull pricing and availability from your ERP, apply your configured discount rules, and generate a draft quote for rep review, compressing 48-hour manual processes to minutes. Q: Is Salesforce Manufacturing Cloud required for Agentforce? A: Not necessarily. Agentforce can run on Sales Cloud or Service Cloud for manufacturers. Manufacturing Cloud adds value for account-based forecasting and rebate management. We'll recommend the right cloud mix based on your specific use cases in the discovery call. Q: How long does a Manufacturing Cloud + Agentforce implementation take? A: A focused quoting or logistics automation agent typically takes 6 to 10 weeks. Full Manufacturing Cloud implementations with ERP integration and multiple agents run 14 to 20 weeks depending on data complexity. Real estate is Phenoble's lead practice. Manufacturing is select work we take when ERP integration and CPQ depth are the deciding factors. ### Retail & Consumer Goods URL: https://phenoble.com/industries/retail Turn Every Shopper Interaction Into Revenue. Phenoble helps retailers deploy Salesforce Agentforce and Data Cloud to unify shopper data across stores, ecommerce, and loyalty, then automate order support and personalization at scale. Retail teams don't lack customer data; they drown in it. POS, ecommerce, loyalty, and support all hold a different version of the same shopper. We unify that data and put AI agents to work on it. Challenges we address: - Siloed Channel Data: In-store POS, ecommerce, marketing, and loyalty systems each hold a partial shopper profile, so no team sees the full customer and personalization stays generic. - WISMO Ticket Overload: "Where is my order?", returns, and exchange requests dominate the support queue, tying up agents on lookups that need no human judgment. - One-Size-Fits-All Marketing: Without a unified profile, campaigns blast the same message to every segment, wasting spend and training shoppers to ignore your brand. How Phenoble approaches it: - Autonomous Order Support: Deploy an Agentforce service agent on your storefront and WhatsApp that resolves order status, returns, and exchange requests directly from your order management data, around the clock. (Impact: 24/7 Order Support) - Unified Shopper Profile: Use Data Cloud to merge POS, ecommerce, loyalty, and service history into one real-time shopper profile that agents, marketers, and store associates all work from. (Impact: One Profile, Every Channel) - Personalization That Converts: Segment on real behavior, not guesswork. Agents and journeys use the unified profile to recommend products, time offers, and win back lapsed shoppers automatically. (Impact: Right Offer, Right Time) Capabilities: - Order Status & WISMO Deflection: Shoppers ask the chat agent where their order is; the agent pulls live data from your OMS and carrier APIs and answers without a human touching the case. - Returns & Exchange Processing: Agents validate return eligibility against your policy, issue labels, and create the exchange order, escalating only the edge cases to your team. - Inventory & Availability Queries: "Is this in stock near me?" gets answered from live inventory data across stores and warehouses, keeping the sale in your channel instead of a competitor's. - Loyalty & Win-Back Journeys: Agents enroll shoppers, answer points questions, and trigger win-back offers when Data Cloud detects a lapsing customer. - Segment-Level Insights: We unify transaction and engagement data so merchandising and marketing see which segments, products, and channels actually drive margin. - Store Associate Assist: Associates get an internal agent that surfaces the shopper's history, sizes, and open orders at the counter, turning service moments into upsell moments. FAQ: Q: Can Agentforce connect to our ecommerce platform and OMS? A: Yes. We build custom actions that connect Agentforce to Shopify, Salesforce Commerce Cloud, Magento, and custom order management systems via their APIs, so agents can look up orders, check inventory, and process returns in real time. Q: Do we need Data Cloud before deploying a retail agent? A: Not always. A focused order-status agent can run on Service Cloud data alone. Data Cloud becomes essential when you want personalization, loyalty journeys, or a single shopper profile across store and online channels. We recommend the right sequence in the discovery call. Q: How do you keep the agent from making promises we can't keep? A: Agent responses are grounded in your actual policy documents and live system data, and every action (refunds, exchanges) runs through Apex logic with your business rules. Anything outside the defined scope escalates to a human with full context. Q: How long does a retail Agentforce implementation take? A: A focused order-support agent typically takes 6 to 10 weeks. Adding Data Cloud unification and personalization journeys extends the roadmap to 12 to 16 weeks depending on how many source systems we integrate. Real estate is Phenoble's lead practice. Retail is select work we take when Data Cloud unification across store, ecommerce, and loyalty data is the deciding factor. ### Information Technology URL: https://phenoble.com/industries/information-technology Scale Your IT Business With Autonomous Agents. Phenoble helps software companies, MSPs, and IT services firms deploy Salesforce Agentforce to automate support triage, speed up quoting and renewals, and give every team one real-time view of the client. IT businesses sell expertise, yet their senior people spend hours on tier-1 tickets, quote paperwork, and status updates. We automate that layer so your engineers and sellers work at the top of their skill. Challenges we address: - Tier-1 Ticket Overload: Password resets, access requests, and how-to questions consume your service desk, pushing real incidents and SLA-bound work to the back of the queue. - Leaky Renewals & Upsells: Contract renewals, license true-ups, and expansion signals live in spreadsheets and inboxes, so revenue quietly walks out the door at term end. - Disconnected Client Data: CRM, PSA, ticketing, and billing systems each hold part of the client story, leaving account managers blind to health, usage, and open issues. How Phenoble approaches it: - Autonomous Service Desk: Deploy an Agentforce agent that resolves tier-1 requests directly from your knowledge base and ITSM data, and triages the rest with full context to the right engineer. (Impact: Tier-1 Resolved Autonomously) - Renewal & Expansion Automation: Agents watch contract end dates, usage, and support health, then open renewal opportunities, draft quotes, and alert account managers before churn risk becomes churn. (Impact: No Renewal Left Behind) - Unified Client 360: Connect CRM, ticketing, and billing into one real-time client view so sales, support, and delivery stop working from different versions of the truth. (Impact: One Client View, Every Team) Capabilities: - Support Triage & Deflection: Agents classify incoming tickets, resolve known issues from your knowledge base, and route the remainder by skill and SLA, cutting first-response time to seconds. - SLA & Escalation Monitoring: Agents track SLA clocks across open cases and escalate proactively before breach, instead of after the client complains. - Renewals & License Management: Agents surface upcoming renewals, usage overages, and true-up opportunities, and prepare the paperwork so account managers just review and send. - Quote & Proposal Acceleration: Connected to CPQ, agents assemble quotes from your product catalog and pricing rules, compressing multi-day proposal cycles into same-day turnaround. - System Integrations: We connect Salesforce to Jira, ServiceNow, Zendesk, and your billing stack via APIs so agents can act across the tools your teams already use. - Client Self-Service Portal: Clients get a 24/7 agent for ticket status, license questions, and documentation, reducing inbound volume without reducing service quality. FAQ: Q: Can Agentforce integrate with Jira, ServiceNow, or Zendesk? A: Yes. We build custom Apex actions that connect Agentforce to Jira, ServiceNow, Zendesk, and other ITSM or PSA tools via their REST APIs, so agents can read ticket status, create issues, and sync updates in real time. Q: We already have a chatbot on our help desk. Why is Agentforce different? A: Traditional chatbots follow scripted flows and hand off as soon as a question deviates. Agentforce agents reason over your live Salesforce data and knowledge base, and can take real actions (create a case, update a renewal, draft a quote) with guardrails you define. Q: How do you handle security and access control for agents? A: Agents run inside Salesforce's trust layer and respect your existing sharing rules, profiles, and permission sets. Every action is logged, and anything outside the defined scope escalates to a human with full context. Q: How long does an Agentforce implementation take for an IT services firm? A: A focused support-triage agent typically takes 6 to 10 weeks. Adding renewal automation and CPQ-connected quoting extends the roadmap to 12 to 16 weeks depending on how many systems we integrate. Real estate is Phenoble's lead practice. IT is select work we take when support triage and renewal automation on Salesforce are the deciding factors. ## Homepage FAQ Q: Is AI safe to connect to our listing and client data? A: Yes. Salesforce's Einstein Trust Layer ensures your data is never retained outside your org and never used to train global LLMs. We add strict field-level security and data masking so an agent only sees what it is authorized to see, whether that is listing data, tenant records, or commission information. Q: How is Agentforce different from the chatbots real estate portals already use? A: Portal chatbots follow rigid, pre-programmed decision trees. Agentforce agents reason over your live Salesforce data, so they can qualify an inquiry, check unit availability, schedule a site visit, or log a work order as native Salesforce actions, and hand off to a human with full context when needed. Q: Do we need Data Cloud before implementing Agentforce? A: Not always. Agentforce can run on standard Salesforce CRM data, but if your listings, leads, and transactions live across portals, spreadsheets, and property management tools, Data Cloud unifies them into a single real-time view. That unified view is what keeps agent answers accurate and reduces hallucinations. Q: How long does a typical implementation take for a brokerage or developer? A: Phenoble's standard deployment cycles range from 6 to 10 weeks, depending on data readiness, the custom actions required, and the amount of integration needed. The Agentforce Pilot proves one agent in your sandbox in 7 days, the Agentforce Launch takes it to production in 2 weeks, and the Real Estate Salesforce Quickstart is fixed scope by design. ## Team URL: https://phenoble.com/about - Sachin Sharma, Co-Founder & CEO (AI Strategy · Agentforce · MCP · Cloud Infrastructure): https://www.linkedin.com/in/rksachin5 - Nand Kishore S., Co-Founder & CTO (Agentforce · Data Cloud · Apex · LWC): https://www.linkedin.com/in/nand-nand/ - Keshav Sharma, Sr. Salesforce Developer (Sales Cloud · Service Cloud · Integration· Agentforce) - Monika Sharma, Sr. Salesforce Developer (LWC · Flows · Platform Dev · Finance Cloud) - Dimple Sharma, Salesforce Developer (Agentforce · Data Cloud · Admin) - Kaushal Sharma, FullStack Developer (Next.js · Node.js · Salesforce API · Agentforce) - Mohit Sharma, Head of Sales (Client Relationships · Business Development) - Ankit Lohiya, Salesforce Developer (Apex · Triggers · SOQL · Platform Events) - Aaditya, Engineer - Yogesh, Engineer ## Case studies ### AI Operations Layer for a US Commercial Real Estate Brokerage URL: https://phenoble.com/case-studies/ai-operations-layer-for-us-cre-brokerage Industry: Real Estate | Region: USA --- - **📍 Location:** USA - **🏭 Industry:** Commercial Real Estate Brokerage and Advisory - **💼 Domain:** Brokerage Operations and AI Automation --- #### Challenge Brokers at a US commercial real estate advisory firm were spending the bulk of their day on operations instead of deals: - Site photos, business cards, and signed pages sat in phones and inboxes **waiting to be typed into the CRM**. - LOIs, NDAs, and proposals lived in Dropbox with **no link back to the deal record**. - Follow-up threads slipped because **nobody had time to scan the inbox for silence**. - Every deal touched five disconnected tools: Slack, REthink+ on Salesforce, Smartsheet, Outlook, and Dropbox. #### Solution We built Claude as the orchestration layer across the entire brokerage stack, using a hub-and-spoke pattern where every tool is an input, an output, or both. The build consists of 12 versioned Claude Skills grouped by broker activity (deal pipeline, document handling, outreach drafting, reporting) and 3 automated Routines that fire them. **Routine 1: image-driven CRM updates.** A broker drops a site photo, business card, or signed page into Slack. Claude extracts names, emails, addresses, and context, decides where the data belongs, and updates the REthink+ contact or activity record in Salesforce plus the Smartsheet tracker row. Photo to fully updated CRM in seconds, without leaving Slack. **Routine 2: document loop.** Claude pulls the source document from the correct Dropbox deal folder, runs the right Skill (summary, redline, proposal draft, or extraction), files the output back with correct naming, and writes the link to the Salesforce deal record so nothing gets lost. **Routine 3: outreach catch-up.** Claude scans Outlook on a schedule, flags threads with no broker reply past a threshold, re-reads the thread plus deal context from Salesforce, and stages a reply in the broker's own voice in the drafts folder. Brokers start the morning with ready-to-send follow-ups instead of missed threads. On top of the three Routines: daily and weekly pipeline summaries, stuck-deal alerts with next-step prompts to deal owners, and per-broker performance rollups. #### Stack Claude (Skills and Routines), Salesforce with REthink+ CRM, Slack, Outlook, Dropbox, Smartsheet. #### Outcome - Daily operations work per role went from roughly 8 hours to 15 to 20 minutes. The client confirmed the figure in July 2026. - Zero manual data entry from photos, business cards, and signed documents into the CRM. - Every generated document automatically filed and linked to its Salesforce deal record. - No follow-up thread left unanswered past the set threshold. ### Real Estate Sales: Salesforce CRM & Automation URL: https://phenoble.com/case-studies/transforming-real-estate-sales-with-salesforce-Powered-CRM-and-automation Industry: Real Estate | Region: USA --- - **📍 Location:** USA - **🏭 Industry:** Real Estate - **💼 Domain:** Property Dealership & Customer Relationship Management (CRM) --- #### Challenge The client, a real estate property dealer in the USA, faced multiple issues with their manual CRM processes and fragmented systems: - **Delayed** customer responses and poor communication. - Lost client opportunities due to **slow or missed follow-ups**. - **Increased transaction errors** and inefficiencies. - **Lack of centralized property** and customer data hindered decision-making and scalability. Needed a scalable solution to streamline property listings, improve engagement, and enhance operational productivity. --- #### Solution **Phenoble Software implemented a customized Salesforce-based CRM solution** tailored for real estate sales and property management workflows. The solution automated lead tracking, streamlined property matching, and integrated communication tools to improve customer engagement. ##### Automated Lead and Opportunity Management Phenoble Software configured Salesforce to automate lead capture, follow-ups, and opportunity tracking. Key features included: - Automated reminders for agents to follow up with prospects - Structured sales stages for tracking property deals - Centralized lead and opportunity management This ensured no potential client inquiry was missed. ##### Custom Property Matching System To improve client-agent alignment, Phenoble Software developed **custom Salesforce objects** to manage property listings and match them with client requirements. This allowed agents to: - Track both residential and commercial properties - Quickly match client preferences with available listings - Improve the speed and accuracy of property recommendations ##### Automated Listing and Transaction Workflows Phenoble Software streamlined listing and transaction workflows within Salesforce. This included: - Property listing management - Automated onboarding processes - Transaction tracking from inquiry to deal closure This significantly reduced manual administrative work. ##### Integration with Communication and Transaction Tools Phenoble Software integrated Salesforce with key platforms used by the client, including: - **SendGrid** for automated email communication - **WordPress** for capturing property inquiries from the website - **DocuSign and digital transaction systems** for streamlined document management These integrations enabled seamless communication and faster deal processing. --- #### Business Impact - Faster Customer Engagement - Automated workflows improved response times and customer communication. - Improved Sales Visibility - Agents gained full visibility into property pipelines and deal progress. - Reduced Manual Work - Automation minimized manual follow-ups and administrative tasks. - Higher Agent Productivity - Sales agents could focus more on closing deals rather than managing data. - Stronger Customer Experience - Better property matching and faster communication improved client satisfaction and brand reputation. --- #### Tech Stack - **Technology** - Salesforce CRM - API Integrations - Automated Workflows - Custom Objects - **Cloud** - Salesforce Cloud - Digital Transaction Cloud - **Tools** - VS Code - SendGrid - Workbench - DocuSign - Dialpad - WordPress #### Result ✔ Centralized CRM platform for managing clients, properties, and transactions ✔ Automated follow-up and opportunity tracking for real estate agents ✔ Faster property matching using custom Salesforce objects ✔ Integrated communication and document workflows ✔ Scalable CRM system supporting both residential and commercial property sales ### HubSpot to Salesforce Migration: Zero Data Loss URL: https://phenoble.com/case-studies/hubsot-to-salesforce-crm-migration-with-zero-data-loss Industry: Technology | Region: USA - **📍 Location:** USA - **🏭 Industry:** Tech - **💼 Domain:** Health --- ##### Challenge A growing B2B organization was using HubSpot as its primary CRM for marketing and early stage sales activities. As the sales team expanded, the company decided to migrate to Salesforce to support more advanced sales processes, reporting capabilities, and long-term scalability. However, migrating historical CRM data presented several challenges. HubSpot and Salesforce follow very different data models, which made direct migration complex. Key challenges included: - **Different CRM Data Models** HubSpot does not use a native Account object and instead stores company data in the Company object, while Salesforce uses Accounts to represent organizations. - **Contact Structure Differences** In HubSpot, contacts can represent both leads and customers, whereas Salesforce separates them into Leads, Contacts, and Accounts. - **Duplicate Record Risks** Existing duplicate rules in Salesforce could block imports and risk creating duplicate Leads and Contacts. - **Relationship Preservation** Historical relationships between companies and contacts needed to be maintained during migration. Future Integration Requirements HubSpot record IDs needed to be preserved to allow future integrations or synchronization if required. The client required a structured migration strategy that would ensure clean data, prevent duplicates, and align with Salesforce best practices. ##### Solution **Phenoble Software designed and executed a structured three phase CRM migration strategy** to ensure a smooth transition from HubSpot to Salesforce while preserving data integrity and relationships. Our approach focused on maintaining a clean Salesforce data model, preventing duplicates, and preserving historical references. ##### Data Architecture Principles Implemented Phenoble Software implemented the migration based on key CRM data governance principles: - Each individual must exist as **either a Lead or a Contact, never both** - Salesforce system fields must remain unchanged - **External ID** fields must be used to prevent duplicates - Data imports must follow the correct **object dependency order** **Phase 1: Account Migration** Phenoble Software migrated HubSpot **Companies** into Salesforce **Accounts**. **Approach** - HubSpot Company records were mapped to Salesforce Accounts. - A custom External ID field was created to store HubSpot Company IDs. - Salesforce system-generated fields were excluded from imports. **Outcome** - All company records migrated successfully. - A clean Account structure was established to support future relationships. --- **Phase 2: Contact Migration** HubSpot Contacts representing existing customers were migrated as **Salesforce Contacts**. **Approach** - Contacts were linked to Accounts using company relationships. - HubSpot Contact IDs were stored in Salesforce as External IDs. - Duplicate prevention was handled using Upsert logic. **Outcome** - Contacts were accurately associated with their respective Accounts. - No duplicate contacts were created. - HubSpot historical references were preserved. --- **Phase 3: Lead Migration** **Critical Decision** Phenoble Software migrated remaining HubSpot contacts as **Salesforce Leads**. **Approach** - Leads were imported only for individuals who did not already exist as Contacts. - HubSpot lifecycle stages were stored separately from Salesforce Lead Status. - Duplicate rules were respected during import. **Outcome** - A clean lead pipeline was established in Salesforce. - No Lead-Contact duplication occurred. - Sales teams could continue standard lead conversion processes. --- ##### Duplicate Management Strategy To ensure high data quality during migration: - Custom External ID fields were created on: - Accounts - Contacts - Leads - Salesforce imports were executed using Upsert mode (Add & Update). - Duplicate rules were temporarily relaxed during migration and re-enabled afterward. This ensured a controlled and error-free migration process. ##### Results ✔ Successfully migrated complete historical data from HubSpot to Salesforce ✔ Preserved company-contact relationships and HubSpot record references ✔ Zero duplicate Accounts, Contacts, or Leads created ✔ Clean Salesforce data structure aligned with best practices ✔ Sales team transitioned to Salesforce without operational disruption ✔ Established a scalable CRM foundation for future growth ##### Business Impact - **Faster Salesforce Adoption** - Sales teams were able to transition quickly without disruptions to their workflow. - **Reliable Reporting and Forecasting** - Cleanly structured Salesforce data enabled accurate reporting and pipeline visibility. - **Improved Data Integrity** - External ID mapping and controlled migration eliminated duplicate records. - **Scalable CRM Foundation** - The new Salesforce architecture supports future integrations and business growth. - **Reduced Data Maintenance Effort** - Well-structured data significantly reduced long-term administrative overhead. ##### Tech Stack - **Technology** - Salesforce CRM - Salesforce Data Import Wizard / Data Loader - External ID Mapping - Data Migration Strategy & CRM Data Architecture - **Cloud** - Salesforce Sales Cloud - **Tools used** - HubSpot CRM - Salesforce Data Loader - VS Code - Workbench ### Water Treatment: Salesforce & SquareUp Integration URL: https://phenoble.com/case-studies/transforming-water-treatment-operations-with-salesforce-and-squareUp-integration Industry: Field Service | Region: USA - **📍 Location:** Central Florida, USA - **🏭 Industry:** Water Treatment and Purification Services - **💼 Domain:** Water Treatment #### Challenge The water purifier company faced major operational challenges despite using a CRM system to store customer data. Many important processes, including customer data management, billing, and payment processing were still handled manually. This manual work created inefficiencies and frequent errors, which caused delays in customer service and invoice processing. In addition, issues related to quality control and inventory management affected customer satisfaction and overall sales performance. The company needed a scalable solution to automate workflows, improve data accuracy, reduce manual effort, and deliver a better customer experience #### Solution Phenoble Software implemented a Salesforce-based solution that automated customer management, billing, and payment processing by integrating Salesforce CRM with the SquareUp payment gateway. Key components of the solution included: **Salesforce-SquareUp Integration** Phenoble Software developed an integration that automatically generates payment links from Salesforce and sends them directly to customers via email. This removed the need for manual payment requests. **Custom Apex Development & API Integration** Our team built custom Apex classes and used Salesforce APIs to handle: - Customer search and creation - Order processing - Invoice generation - Invoice publishing via SquareUp APIs This created a fully automated billing and payment workflow. **Automated Reporting & Dashboards** Phenoble Software configured dashboards to provide real-time insights into: - New customer acquisition - Sales forecasting - Order tracking - Service performance - Strategic plan monitoring **Marketing Automation with Mailchimp** We integrated Salesforce with Mailchimp to improve audience segmentation and manage email campaigns for subscribed contacts. Through this implementation, Phenoble Software created a connected system where customer service, sales, and billing teams work from a single automated platform. #### Business Impact - **Reduced Errors:** Automation significantly reduced manual data entry mistakes in customer records and billing. - **Faster Billing Cycles:** Invoices were generated and sent instantly, reducing delays in payment processing. - **Improved Cash Flow:** Online payments through SquareUp accelerated collections. - **Enhanced Customer Experience:** Customers received faster service and convenient payment options. - **Better Data Quality:** Centralized and automated data improved decision-making. - **Sales Growth:** Improved operational efficiency and customer satisfaction led to increased sales. #### Tech Stack ###### **Technology:** - **Salesforce CRM** - **Apex development (API integration)** - **Web-to-Lead** - **Workflow Rules** - **Salesforce Flows** - **Approval Processes** - **Apex Batch Jobs** **Cloud:** Salesforce Sales Cloud **Tools:** VS Code, Workbench and SquareUp (Payment Gateway Service) **Result**: ### Lead & Appointment Automation with Salesforce URL: https://phenoble.com/case-studies/driving-business-growth-with-salesforce-powered-lead-and-appointment-automation Industry: Beauty & Wellness | Region: Australia - **📍 Location:** Australia - **🏭 Industry:** Beauty & Wellness - **💼 Domain:** Lead Management & Appointment Booking --- #### Challenge A beauty and wellness salon based in Australia was facing operational challenges in managing customer leads and appointment bookings. Most of their processes relied heavily on manual data entry, which created inefficiencies and data inconsistencies. Key challenges included: - **Manual Lead Management** Customer information collected from different channels was manually entered into the system, leading to data inaccuracies and security risks. - **Inefficient Appointment Booking Process** The existing booking process was prone to errors and difficult to scale, resulting in missed appointments and potential revenue loss. - **Lack of System Integration** The absence of integrated systems limited visibility into customer interactions, making it difficult to personalize services and manage leads effectively. The client needed a centralized and automated solution to capture leads in real time, streamline appointment management, and improve overall operational efficiency. --- #### Solution **Phenoble Software implemented a Salesforce-based solution** to automate lead capture, streamline appointment management, and improve customer engagement. Our solution focused on reducing manual work while ensuring real-time data capture and automated workflows. **Real-Time Lead Capture** Phenoble Software implemented Salesforce Web-to-Lead forms and API integrations to capture customer information directly from the website and other channels into Salesforce. This ensured: - Instant lead creation - Elimination of manual data entry - Real-time visibility for the sales and service teams **Automated Lead Validation and Processing** We developed automated workflows and validation processes to ensure data accuracy and proper lead assignment. This included: - Automated field mapping and validation - Lead tracking and status updates - Structured data management for better reporting **Trigger-Based Notifications and Alerts** Phenoble Software implemented Apex triggers and automated notifications to keep the team informed about new leads and appointment-related activities. Key features included: - Instant alerts for new leads - Automated follow-up reminders - Appointment notifications for staff This significantly improved response times and ensured no leads were missed. --- #### Business Impact - **Streamlined Lead Generation** - Automated lead capture improved the efficiency of the lead generation process. - **Reduced Manual Errors** - Automation eliminated most manual data entry errors and improved data reliability. - **Faster Customer Response** - Real-time lead capture and notifications allowed staff to respond quickly to new inquiries. - **Enhanced Customer Experience** - Better data visibility enabled more personalized service and improved client engagement. - **Scalable Operations** - The automated system allowed the salon to scale its operations without increasing manual workload. --- #### Tech Stack - **Technology** - Salesforce CRM - API Integrations - Workflow Automation - Web-to-Lead - **Cloud** - Salesforce Sales Cloud - Integration Cloud - **Tools** - VS Code - Workbench #### Results ✔ Automated lead capture and appointment management workflows ✔ Eliminated manual data entry for lead processing ✔ Improved response time to customer inquiries ✔ Increased operational efficiency and service quality ✔ Created a scalable CRM system to support future business growth ### IT Case & Asset Management with Salesforce URL: https://phenoble.com/case-studies/streamlining-IT-case-and-asset-management-with-salesforce Industry: IT Services | Region: USA - **📍 Location:** USA - **🏭 Industry:** IT Services - **💼 Domain:** Case Management & IT Asset Management --- #### Challenge An IT services company based in the USA was facing major operational inefficiencies in managing customer support cases and IT assets. The organization relied heavily on manual processes, which led to delays, poor visibility, and inconsistent service delivery. Key challenges included: - Inefficient Case Management - Support cases were handled through manual workflows, causing routing delays and inconsistent issue resolution. - No Standardized Escalation Process - The absence of a structured escalation framework resulted in slower response times and difficulty prioritizing critical issues. - Limited IT Asset Visibility - Poor asset tracking made it difficult for support teams to identify customer environments and manage documentation effectively. - Fragmented Communication - Communication between support teams and customers was not centralized, leading to confusion and delayed responses. - Manual Reporting - Service performance insights were difficult to generate due to dependence on manual reporting processes. The client needed a centralized service management system that could automate case workflows, improve asset visibility, and provide actionable insights into support operations. --- #### Solution **Phenoble Software implemented a customized Salesforce-based service management solution** to automate case workflows, centralize communication, and improve asset tracking. The solution was designed to streamline service operations and provide real-time visibility into support performance. **Automated Case Management** Phenoble Software implemented automated case routing, assignment, and escalation processes within Salesforce. This ensured: - Faster case distribution to the right support agents - Standardized escalation rules for critical issues - Improved tracking of case status and resolution times **Knowledge Base and Self-Service Portal** To reduce the volume of repetitive support requests, Phenoble Software implemented a knowledge base and customer self-service portal. This allowed customers to: - Access common troubleshooting resources - Submit support requests directly through the portal - Track case progress without manual follow-ups **IT Asset Integration with ITGlue** Phenoble Software integrated Salesforce with ITGlue to synchronize asset documentation and improve asset visibility. This enabled support teams to: - Access accurate asset data within Salesforce - Quickly understand customer infrastructure - Improve troubleshooting efficiency **Service Performance Analytics** Custom dashboards and reports were implemented to provide real-time visibility into service operations. These dashboards helped the client track: - Case resolution times - Agent performance - Support request trends - Service efficiency metrics **Business Impact** - **Faster Issue Resolution** - Automated case assignment and escalation significantly reduced case handling time. - **Reduced Manual Work** - Automation minimized manual intervention and reduced operational errors. - **Improved Asset Visibility** - Integration with ITGlue provided a centralized view of customer IT assets. - **Data-Driven Decision Making** - Real-time dashboards enabled management to monitor service performance and identify improvement areas. - **Enhanced Team Collaboration** - Centralized communication improved coordination between support teams. - **Higher Customer Satisfaction** - Faster support response and improved service transparency strengthened customer trust. **Tech Stack** - Technology - Salesforce CRM - API Integrations - Workflow Automation - Dashboards & Analytics - Cloud - Salesforce Service Cloud - Integration Cloud - Tools - ITGlue - VS Code - Workbench **Result** ✔ Automated and standardized case management workflows ✔ Reduced case resolution time through intelligent routing and escalation ✔ Improved IT asset visibility through ITGlue integration ✔ Enabled real-time service performance monitoring through dashboards ✔ Created a scalable service management system supporting long-term growth ### Lead Capture & Reporting: Salesforce Automation URL: https://phenoble.com/case-studies/streamlining-lead-capture-meetings-and-reporting-with-salesforce-automation Industry: Food-Tech | Region: USA - **📍 Location:** USA - **🏭 Industry:** Food & Beverage / Food-Tech - **💼 Domain:** Online Food Ordering & Delivery Automation --- #### Challenge A fast-growing food-tech company was experiencing operational inefficiencies in its sales workflow and customer engagement processes. The company used several tools for lead generation, meeting scheduling, and collaboration, but these systems were not fully integrated with Salesforce. As a result, the sales team faced multiple challenges: - **Lead Management Gaps** Leads generated through Amplemarket had to be manually added to Salesforce and sales sequences, which caused delays, data inconsistencies, and missed follow-ups. - **Missed Meeting Updates** Meetings scheduled through Calendly were not automatically reflected in Salesforce opportunities, making it difficult for sales representatives to track deal progress accurately. - **Manual Meeting Notes** Sales teams were required to manually add meeting notes into Salesforce after every call, which was time-consuming and often resulted in incomplete information. - **Limited Client Visibility** Customers wanted access to real-time dashboards but preferred not to log into Salesforce due to its complexity. The company needed an integrated automation solution that could connect multiple sales tools with Salesforce, reduce manual work, and provide real-time visibility into the sales pipeline. --- #### Solution **Phenoble Software designed and implemented an end-to-end Salesforce automation framework** integrating multiple sales tools to streamline lead management, meeting tracking, and client reporting. The solution connected Amplemarket, Calendly, Avoma, Slack, and Salesforce to create a unified and automated sales ecosystem. ##### 1. Automated Lead Capture (Ample Market → Salesforce) Phenoble Software integrated Amplemarket with Salesforce to ensure that all selected leads were automatically created in Salesforce as Lead records. Key capabilities included: - Automatic lead creation in Salesforce - Real-time synchronization of prospect data - Automatic enrollment of leads into sales sequences for immediate follow-up This eliminated manual data entry and ensured faster lead engagement. ##### 2. Calendly Integration with Salesforce Opportunities To improve pipeline tracking, Phenoble Software integrated Calendly with Salesforce. When a meeting was booked: - Calendly confirmation emails were detected - Salesforce Opportunities associated with the contact were automatically updated to “Meeting Booked” stage This ensured accurate and real-time pipeline visibility for sales teams. ##### 3. Automated Meeting Notes with Avoma Phenoble Software implemented an integration between Avoma and Salesforce to automatically sync meeting recordings and notes. This allowed: - Automatic storage of meeting insights in Salesforce - Elimination of manual note-taking - Improved visibility into sales conversations ##### 4. Client Dashboard Access via Slack To simplify reporting for clients, Phenoble Software integrated Salesforce dashboards with Slack channels. This allowed stakeholders to: - View real-time sales metrics directly in Slack - Access automated updates without logging into Salesforce - Improve transparency and collaboration between teams --- --- #### Business Impact - **Significant Time Savings** - Automation eliminated manual lead imports, data updates, and reporting preparation. - **Real-Time Pipeline Visibility** - Sales leadership gained instant insights into deal progress and pipeline health. - **Improved Sales Productivity** - Sales representatives could focus more on selling rather than updating CRM records. - **Higher Data Accuracy** - Integration across Amplemarket, Calendly, Avoma, and Salesforce ensured consistent and reliable data. - **Scalable Sales Operations** - The system allows the company to onboard additional sales reps and manage higher lead volumes without increasing administrative workload. - **Enhanced Collaboration** - Slack-based reporting improved communication and transparency between teams and stakeholders. --- #### Tech Stack - **Technology** - Salesforce (Flows, Apex, Custom Objects) - API Integrations - Workflow Automation - **Integrations** - Amplemarket API - Calendly API - Avoma API - Slack API - **Cloud** - Salesforce Sales Cloud - **Tools** - VS Code - Workbench --- #### Result ✔ Fully automated lead capture and sales sequence enrollment ✔ Real-time synchronization between Calendly meetings and Salesforce opportunities ✔ Automated meeting notes and insights stored directly in Salesforce ✔ Client-friendly reporting through Slack-integrated Salesforce dashboards ✔ Scalable and integrated sales ecosystem supporting business growth ### Transforming Retail Efficiency and Customer Service URL: https://phenoble.com/case-studies/transforming-retail-efficiency-and-customer-service Industry: Retail | Region: USA - **📍 Location:** US - **🏭 Industry:** Retail - **💼 Domain:** Retail --- #### Challenge A leading retail company in the USA was experiencing operational inefficiencies due to disconnected systems and the absence of a centralized CRM platform. Multiple departments were using separate tools, which created data silos and limited operational visibility. Key challenges included: - Delayed Order Processing - The lack of real-time data synchronization slowed down order management and made it difficult for teams to make timely decisions. - Disconnected Systems - Different platforms were used across departments, resulting in fragmented data and poor integration between sales, support, and order management. - Inconsistent Customer Service - Customer support teams lacked accurate and centralized information, leading to delays in case handling and reporting. - Manual Zendesk Processes - Many Zendesk operations were handled manually, creating inefficiencies and reducing the speed of customer support responses. These issues negatively impacted operational efficiency, delayed service delivery, and weakened the overall customer experience. --- #### Solution Phenoble Software designed and implemented a Salesforce-based transformation to centralize customer data, automate support workflows, and integrate the company’s e-commerce platform with Salesforce. The solution included migrating customer service operations from Zendesk to Salesforce and building integrations that unified data across systems. ##### Zendesk to Salesforce Migration Phenoble Software migrated the client’s support operations from Zendesk to Salesforce to create a unified CRM environment. Key implementations included: - Email-to-Case automation for instant case creation from customer emails - Automated case assignment rules for efficient routing to support agents - Priority-based escalation rules to ensure critical issues were addressed quickly This ensured faster case handling and improved support efficiency. ##### E-commerce Platform Integration Phenoble Software integrated Salesforce with the client’s e-commerce platform to enable real-time data synchronization. This integration allowed: - Automatic synchronization of orders and customer information - Real-time inventory visibility - Improved coordination between sales and support teams ##### CRM Analytics and Reporting To provide better decision-making capabilities, Phenoble Software implemented advanced Salesforce reporting and dashboards. These dashboards enabled the client to monitor: - Customer behavior and purchasing patterns - Sales performance and order trends - Customer support metrics and service effectiveness This centralized reporting improved operational visibility and strategic planning. --- #### Business Impact - Improved Customer Experience - Faster service delivery and real-time case management enhanced customer interactions. - Reduced Response Times - Automated case creation and assignment significantly reduced support response times. - Higher Customer Satisfaction - Improved service reliability and faster resolutions increased customer satisfaction levels. - Stronger Brand Reputation - Consistent and efficient customer support strengthened the company’s brand perception. - Operational Efficiency - Centralized CRM and automation reduced manual work and improved internal collaboration. --- #### Tech Stack - **Technology** - Salesforce CRM - API Integrations - Automated Workflows - Email-to-Case Automation - Real-time Dashboards - Inventory Management Modules - **Cloud** - Salesforce Sales Cloud - **Tools** - VS Code - Zendesk - Workbench #### Result ✔ Successfully migrated customer service operations from Zendesk to Salesforce ✔ Centralized customer data and support workflows within Salesforce ✔ Enabled real-time synchronization between Salesforce and the e-commerce platform ✔ Automated case management and improved response times ✔ Created a scalable CRM infrastructure supporting long-term retail growth ### B2B Metals: Sales, Service & Forecasting URL: https://phenoble.com/case-studies/streamlining-sales-service-and-forecasting-for-a-B2B-metals-marketplace Industry: Manufacturing | Region: USA --- - **📍 Location:** USA - **🏭 Industry:** B2B E-Commerce / Metals Manufacturing - **💼 Domain:** Agentforce B2B Commerce, Data Cloud & Revenue Lifecycle Management --- #### Challenge A leading B2B metal marketplace in the USA was losing multi-million dollar deals to competitors because their quotation process took 48+ hours. Buyers purchasing complex alloys needed immediate pricing based on volatile spot market rates, but sales reps manually calculated margins using fragmented spreadsheets. Key challenges included: - **Pricing Hallucinations & Delays:** Without real-time spot market data, quotes were either painfully slow or financially inaccurate, leading to margin erosion. - **Fragmented Buyer Data:** Customer order histories, credit limits, and material preferences were siloed across a legacy ERP and email. - **Support Bottlenecks:** Sales reps spent 60% of their day answering simple logistics questions ("Where is my shipment?") instead of prioritizing high-value enterprise deals. The client needed an autonomous, data-first solution to unify pricing logic, automate quotation generation, and deflect low-level logistics inquiries. --- #### Solution **Phenoble** implemented a comprehensive AI-first architecture powered by **Salesforce Agentforce** and **Data Cloud** to eliminate quotation friction and automate customer service. ##### Harmonizing the Supply Chain with Data Cloud Before deploying AI, Phenoble built the foundation. We implemented **Data Cloud** to ingest real-time metal spot prices, legacy ERP inventory levels, and historical customer purchasing data. This created a single, unified data graph, ensuring AI models would never hallucinate pricing. ##### Autonomous Quoting with Agentforce Sales Agents Phenoble developed specialized **Agentforce Sales Agents** equipped with custom Apex actions. When a buyer submits an RFQ via the Experience Cloud portal, the Agentforce copilot instantly: 1. Queries Data Cloud for the buyer's negotiated discount tier. 2. Checks real-time inventory and spot market prices via external API. 3. Generates and emails a highly accurate, margin-protected PDF quote in under 3 seconds. ##### 24/7 Logistics Support via Agentforce CCaaS To protect sales reps' time, we deployed an autonomous customer service agent. Connected to the logistics provider's tracking API, the Agentforce bot intercepts shipping inquiries, authenticates the user, and securely provides live tracking updates and BOL (Bill of Lading) documents without human intervention. --- #### Business Impact - **Instant Quoting:** Quote turnaround time plummeted from 48 hours to under 3 seconds, increasing win rates by 27%. - **Zero Margin Leakage:** Data Cloud-backed pricing rules eliminated manual calculation errors, protecting profitability on volatile metal orders. - **50% Case Deflection:** Agentforce autonomous triage successfully resolved half of all inbound tier-1 support requests (primarily shipping inquiries). - **Rep Productivity Shift:** Sales representatives reclaimed 20 hours per week, allowing them to focus entirely on proactive enterprise relationship building. #### Tech Stack - **AI & Data:** - Salesforce Agentforce - Salesforce Data Cloud - **Cloud:** - Salesforce Sales Cloud - Salesforce Service Cloud - Revenue Lifecycle Management (RLM) #### Result ✔ Autonomous, AI-driven quotation reducing turnaround from 48 hours to 3 seconds. ✔ Pristine data foundation via Data Cloud ensuring zero AI pricing hallucinations. ✔ Agentforce service bot deflecting 50% of routine logistics inquiries. ✔ Highly scalable, autonomous B2B commerce architecture driving immediate ROI. ### Customer & Partner Portal with Experience Cloud URL: https://phenoble.com/case-studies/building-customer-partner-portal-with-salesforce-experience-cloud Industry: Technology | Region: India - **📍 Location:** India - **🏭 Industry:** Software / Technology - **💼 Domain:** Customer Experience & Partner Relationship Management #### Challenges TechNova, a growing software products company, wanted to improve collaboration with both customers and partners. However, the company lacked a centralized platform where customers and partners could interact with the organization efficiently. Several operational challenges were affecting customer support and partner engagement: - **No Customer Self-Service Portal** - Customers relied heavily on email and phone support to raise issues, which increased support workload and delayed resolutions. - **Inefficient Partner Collaboration** - Partners did not have a standardized system to register deals or track opportunities with TechNova’s sales team. - **Manual Support and Partner Management Processes** - Internal teams struggled to scale customer support and partner management due to manual workflows. - **Lack of Personalized User Experience** - Customers and partners interacted with generic systems that did not provide tailored experiences based on their role. TechNova needed a unified, secure platform that could empower customers with self-service capabilities and enable partners to collaborate efficiently with the sales team. #### Solution **Phenoble Software designed and implemented a Salesforce Experience Cloud portal** to provide a unified digital experience for customers and partners. The portal was built with a strong focus on scalability, security, and personalized engagement. **Secure Portal Access and Authentication** Phenoble Software implemented a secure login and access management system for the Experience Cloud portal. Key features included: - Customer self-registration for easy onboarding - Invitation-based partner access for secure collaboration - Multi-factor authentication (MFA) for enhanced security - Google social login integration for flexible authentication - Custom login flows to capture Terms & Conditions acceptance on first login This ensured secure and controlled access to the portal. **Customer Self-Service Capabilities** To empower customers, Phenoble Software implemented several self-service features within the portal. These included: - Integration with Salesforce Knowledge to allow customers to browse help articles - A case creation form with knowledge-based case deflection suggestions - A custom “My Cases” Lightning Web Component (LWC) enabling users to: - View submitted cases - Track case status - Filter and sort case history This significantly reduced reliance on support agents. **Partner Collaboration and Deal Registration** Phenoble Software implemented a partner collaboration framework using the Salesforce Partner Account model. Key capabilities included: - A custom “Register a Deal” LWC allowing partners to create leads directly from the portal - Secure opportunity visibility for partners based on their account access - A Partner Dashboard providing real-time insights into pipeline performance This improved transparency and strengthened collaboration between partners and the sales team. **Personalized Portal Experiences** To improve user engagement, Phenoble Software implemented personalization features across the portal. These included: - Audience targeting to display relevant content for customers and partners - Personalized home pages based on user roles - Gamification features such as reputation levels, badges, and discussion forums - Automated badge assignments to reward active users These features encouraged higher portal adoption and engagement. #### Business Impact - Improved Customer Self-Service - Approximately 60% of customer queries were resolved through knowledge articles, significantly reducing support case volume. - Faster Partner Deal Registration - The deal registration process was reduced from several days to just minutes. - Reduced Support Workload - Self-service capabilities decreased dependency on support agents. - Improved Partner Collaboration - Partners gained better visibility into opportunities and deal progress. - Higher User Engagement - Personalized experiences and gamification features increased portal adoption and interaction. #### Tech Stack - **Technology** - Salesforce Experience Cloud - Salesforce Knowledge - Lightning Web Components (LWC) - Workflow Automation - Audience Targeting - **Cloud** - Salesforce Experience Cloud - Salesforce Service Cloud - **Tools** - VS Code - Workbench #### Result ✔ Unified Experience Cloud portal for customers and partners ✔ Secure self-service platform for case management and knowledge access ✔ Streamlined partner deal registration and opportunity collaboration ✔ Reduced support workload through knowledge-driven case deflection ✔ Personalized portal experience improving user engagement and adoption --- Delivered by our [Salesforce company in Jaipur](/salesforce-company-jaipur) for a client in India. See how we work as a [Salesforce company in India](/salesforce-company-india), or explore [Salesforce for real estate](/industries/real-estate), our lead practice. ### Transforming IT Support Operations with ServiceNow ITSM Automation URL: https://phenoble.com/case-studies/transforming-IT-support-operations-with-serviceNow-ITSM-automation Industry: IT Services | Region: India - **📍 Location:** India, USA - **🏭 Industry:** Information Technology Services - **💼 Domain:** IT Service Management (ITSM) --- #### The Challenge A growing IT services company was struggling with increasing support requests, delayed ticket resolution, and inefficient manual processes. The organization was managing incidents and employee support requests through emails, spreadsheets, and disconnected tools, which created major operational bottlenecks. ##### Key Challenges: - Delayed incident response times - No centralized ticket tracking system - Manual ticket assignment process - Poor SLA visibility - Repetitive Level-1 support workload - Lack of reporting and operational insights - Increased employee frustration due to slow resolutions As the organization scaled, the existing process became difficult to manage and negatively impacted both operational efficiency and employee experience. --- #### The Solution To address the growing inefficiencies in IT support operations, we designed and implemented a comprehensive ServiceNow ITSM transformation strategy, not just a tool implementation, but a complete workflow redesign. Our approach focused on: - Standardization - Automation - Visibility - Scalability --- ##### Step 1: Process Assessment & Workflow Redesign Before implementing ServiceNow, we performed a detailed analysis of the client’s existing IT support processes. ###### Identified Issues: - Workflow gaps - Repetitive manual tasks - Bottlenecks in ticket resolution - Lack of ownership and accountability ###### Actions Taken: - Defined clear ticket flow stages - Established priority and SLA rules - Created structured request categories - Standardized approval workflows This ensured that the system was built on optimized processes, not broken ones. ##### Step 2: Centralized Ticketing System Implementation We implemented a unified ServiceNow ITSM platform to centralize all IT requests. ###### Key Improvements: - All incidents and service requests routed through a single platform - Elimination of email-based and manual tracking - Real-time ticket visibility for all stakeholders - Structured categorization of issues This created a single source of truth for all IT operations. --- ##### Step 3: Intelligent Automation & Workflow Engine To reduce manual effort, we configured automation-driven workflows: - Auto-ticket creation from user inputs - Priority-based routing using predefined rules - Automated escalation for SLA breaches - Status-based workflow transitions - Notifications and alerts for stakeholders This minimized human dependency and improved response speed. ##### Step 4: Self-Service & Knowledge Management We introduced a self-service portal integrated with a knowledge base, allowing employees to resolve common issues independently. ###### Features: - Predefined service catalog - Knowledge articles for frequent issues - Guided request submission forms - Automated request tracking This reduced unnecessary ticket volume and improved user experience. --- ##### Step 5: Smart Assignment & Load Balancing We implemented intelligent ticket assignment logic: - Auto-routing based on issue type and priority - Team-wise and skill-based allocation - Balanced workload distribution across agents This eliminated delays caused by manual assignment and improved efficiency. ##### Step 6: SLA Management & Performance Tracking We configured end-to-end SLA monitoring: - Defined SLA policies for different ticket types - Automated SLA tracking and breach alerts - Real-time dashboards for performance monitoring This ensured accountability and improved service quality. --- ##### Step 7: Reporting & Operational Visibility Custom dashboards and reports were built to provide: - Ticket volume insights - Resolution performance metrics - SLA compliance tracking - Team productivity analysis This enabled leadership to make data-driven decisions. ##### Step 8: Scalability & Future-Ready Architecture The solution was designed to scale with the organization: - Modular workflow design - Easy integration with future systems - Expandable service catalog - Support for additional ServiceNow modules This ensured long-term sustainability of the system. --- #### Core Implementations ##### Incident Management Automation - Automated ticket creation - Priority-based ticket routing - SLA tracking - Escalation workflows - Real-time status updates --- ##### Self-Service Employee Portal - Raise incidents - Track requests - Access knowledge articles - Resolve common issues independently --- ##### Smart Ticket Assignment - Issue category-based routing - Priority-based assignment - Department-wise allocation - Rule-based automation --- #### Business Impact After implementing the ServiceNow ITSM solution, the organization achieved significant operational improvements. ##### Measurable Outcomes: - 52% reduction in manual ticket handling - 41% faster incident resolution time - 47% improvement in SLA compliance - Reduced repetitive Level-1 support workload - Improved visibility into IT operations - Enhanced employee support experience - Centralized reporting and dashboards #### Technologies Used ##### Platform - ServiceNow ITSM ##### Modules - Incident Management - Service Catalog - SLA Management - Knowledge Management ##### Features - Workflow Automation - Assignment Rules - Self-Service Portal - Reporting & Dashboards --- #### Client Feedback > “The ServiceNow implementation transformed the way our IT support team operates. Automated workflows and centralized visibility significantly improved our response times and internal efficiency.” > > , IT Operations Manager, Credit-Cloud --- Delivered from our Jaipur hub. Read about our [ServiceNow ITSM implementation service](/services/service-now), how we operate as a [Salesforce company in India](/salesforce-company-india), and our [Jaipur office](/salesforce-company-jaipur). ## Evergreen guides (full text) ### Dreamforce 2026: What It Means for Real Estate URL: https://phenoble.com/blogs/dreamforce-2026-what-it-means-for-real-estate Author: Sachin Sharma | Published: Thu Sep 17 2026 00:00:00 GMT+0000 (Coordinated Universal Time) | Updated: Thu Sep 24 2026 00:00:00 GMT+0000 (Coordinated Universal Time) We did not fly to San Francisco. We read Salesforce's own announcements and the independent coverage of all three days, September 15 to 17, and asked one question: what changes for a team that runs real estate on Salesforce? None of the announcements we read was specific to real estate. Salesforce named industries like financial services, healthcare, manufacturing, and travel. So this post is a translation, and I have marked what is Salesforce's claim and what is our read. Anything nobody has tested is labeled unverified. Updated September 18 with the final day. Salesforce issued no press release on September 17. The Day 3 news came from the Admin, Architect, and Data 360 keynotes, and it has its own section below. #### The short version - **AIforce** carries your Salesforce data, permissions, and workflows into Claude, Slack, and Lightning. Your team stops going to Salesforce. Salesforce comes to where they already work. - **Salesforce in Claude** is in beta for all customers, with 37 prebuilt skills. All 37 are sales skills; Salesforce says service, marketing, commerce, and industry skills are coming, with no date. Whether they reach managed-package objects, like the REthink+ objects the brokerage we built for runs on, is untested. - **Seven job-ready agents** were announced. Six are generally available and Hunter is in pilot. Two map directly to real estate work: Piper for inbound leads and Casey for service requests. - **Koa**, Salesforce's own CRM model, is pilot only. A mid-market real estate team does nothing about it today. - **Day 2 had no major launches.** The keynote was about operating agents already in production. - **Day 3 had no press releases either.** The Admin, Architect, and Data 360 keynotes carried the news: Builder Central (free, beta from the week of September 21, sandbox only), Security Center Essentials (free), the Headless 360 MCP Server (open beta, GA November), and Scoped Access Definitions (no date). - AIforce, Salesforce in Claude, and the agents all run on your existing data and your existing permissions. That is the safety story, and it is also the exposure. #### What Salesforce announced on Day 1 ##### AIforce Salesforce describes AIforce as a live interface layer that brings the platform to any AI interface. Its own line is: "People don't have to come to Salesforce to get work done. Salesforce comes to them." The surfaces Salesforce confirmed are Claude, Slack, and Lightning. Patrick Stokes, Salesforce's President of Applications and Marketing, said AI "kind of disaggregates the UI and brings AI in to kind of replace it." Salesforce Ben shortened that to "AI replaces the UI," which is the phrase you have probably seen. ##### Claudeforce and Salesforce in Claude Claudeforce is the Salesforce and Anthropic partnership, announced on August 26. The first product is Salesforce in Claude, which Salesforce describes as a plugin with 37 prebuilt sales skills covering meeting prep, deal health review, and pipeline review. A seller can query, update, and act on live CRM data from inside Claude. Per Salesforce, actions route through Salesforce so business rules are enforced, an admin connects once, and there is no new permissions model to build. As of the Dreamforce announcement it is available to all customers in beta. Patrick Stokes told the keynote that activation is a form on the AppExchange plugin listing plus your org ID. Salesforce says skills for service, marketing, commerce, and industries come "in the near future," with no date. Pricing is not stated, and Salesforce notes that pricing and packaging are subject to change. ##### Slackforce Slack CRM creates accounts, logs notes, and updates records from a prompt in Slack, without opening Salesforce. Slack Code gives teams a shared space in Slack to build with agents. Launch timing for the Slackforce components is not stated in what we read. ##### Agentforce Coworker An AI teammate inside Lightning, generally available. Salesforce reports 100,000 users activated within 35 days. ##### Seven job-ready agents Announced September 11, the week before the event. These are prebuilt agents you configure rather than build from scratch, and you can rename them. - **Piper** engages, qualifies, and converts inbound leads across websites and inboxes. - **Casey** resolves customer service issues across voice, SMS, WhatsApp, and web chat. - **Hunter** works the sales pipeline from research through outreach. Pilot now, general availability expected November 2026. - **Marshall** orchestrates back-office processes with audit trails. - **Paige** handles IT and HR service requests. - **Carter** helps shoppers discover products and check out in chat. - **Fin** resolves complex customer experience workflows across channels. Per Salesforce, six are generally available. Pricing is not stated on the announcement. Our read below covers Piper and Casey. We have no real estate read on the other five yet. ##### Koa Koa is Salesforce's first CRM reasoning model, built on NVIDIA Nemotron 3 Super and post-trained on synthetic CRM data. Salesforce says no customer data was used in training, and that on its own CRM benchmark Koa matches or exceeds leading models with three times fewer errors. That benchmark is Salesforce's own. Salesforce says it is available to select pilot customers, with general availability expected in winter 2026 in US regions. Salesforce describes it as a Salesforce-hosted option. Nothing we read says it becomes the default. #### Day 2: a keynote about running agents Mark Wakelin, the GM of Agentforce, said 30,000 customers are now live on the platform. Salesforce Ben's roundup noted that anyone waiting for another major product reveal may have left slightly disappointed. What got stage time instead: - **Agent Router.** One controller that hands parts of a process to dedicated subagents. Southwest Airlines showed a customer name change moving through intake, document validation, and refunds. - **Observability.** Session logs, action traces, latency, and response quality. Vivint showed it against live voice calls. - **Agent Optimizer.** Finds production issues, traces them, suggests changes, and generates regression tests. All three are tools for agents that are already live. Salesforce's "Agentic ROI Playbook" had the same shape: get agents into production, then monitor and improve them. Our read: two years after Agentforce was revealed, the question on stage has moved from what it is to whether it pays. The headline customer was Fulton Bank: 80,000 hours saved, $389M in loans and deposits attributed to Agentforce, and complaint resolution four days faster, with more than 20 production use cases. Those are Salesforce-reported figures, across roughly 3,000 users at a bank. Our read: at brokerage scale the useful question is smaller, which one workflow to automate first. #### Day 3: the keynotes for the people who run the org Salesforce published no press release on September 17. The final day's announcements came from the Admin, Architect, and Data 360 keynotes, reported by Salesforce's own admin blog and by Salesforce Ben. None of them is a headline product. All of them touch the preparation work this post asks for. ##### Builder Central Per Salesforce, a no-code workspace where an admin or a permissioned user describes an app or an agent in natural language, refines it, and deploys it. It is built on AIforce, so it runs inside your existing data, metadata, and permissions. The beta starts the week of September 21 for customers with Agentforce enabled. Salesforce says it is included free in every org, with usage limits, and that the beta deploys to a sandbox with one click. Our read: this is the cheapest way to prototype the one workflow you picked. It stops at the sandbox. Production, permissions, and testing are still work someone has to do. ##### Security Center Essentials A free dashboard of your org's security posture. Per Salesforce, no support case is needed: assign the "View Security Center Pages" permission and open it from the App Launcher. Our read: run it first. It is the quickest look at the loose sharing rules problem described further down, and it costs nothing. ##### Headless 360 MCP Server and Scoped Access Definitions Both from the Architect keynote, as reported by Salesforce Ben. The Headless 360 MCP Server is the standard way for an outside agent such as Claude to discover, describe, and call actions in your org. It is in open beta, with general availability in November. Scoped Access Definitions let an admin narrow what a registered agent identity can do below what the user could do. Leo Tran, a Distinguished Architect at Salesforce, put it as "You can give an agent just the access it needs." No availability was stated for Scoped Access Definitions in what we read. Our read: Scoped Access Definitions is the eventual answer to the catch described further down, where an agent inherits every loose sharing rule. Until it ships, sharing rules are the fix. The MCP server is also the mechanism to watch for the managed-package question, and that is still unverified. ##### Data 360: Agent Context Engine Salesforce announced the Agent Context Engine, shared memory and context across agents, with general availability in December 2026, and an agentic Segment Builder for the new year. Salesforce Ben's summary of Rahul Auradkar's opening was that if you do not have good data, a better model will not save you. Our read: both were presented as part of Data 360, which is a separate licence. A team that does not run Data 360 does nothing about this in 2026. The opening line is the same argument this post makes about the record. ##### Agentforce Coworker in more places Per Salesforce, admins can switch Coworker on in under five minutes, and it was shown running in Microsoft Teams as well as Lightning. Accenture said it rolled Coworker out to 16,000 users overnight. That is a Salesforce-reported figure at consulting-firm scale. #### What it means if you run real estate on Salesforce This section is our read. **Brokerages.** Piper is the closest match to agent one in our four-agent list for real estate: qualifying portal and website leads the moment they arrive. We covered that agent and its metric in [the four Agentforce agents that pay for themselves](/blogs/agentforce-for-real-estate-four-agents-that-pay-for-themselves). A prebuilt starting point shortens the build. You still write the qualification questions and wire the actions to your Lead and Opportunity process, and all of it needs testing. **Developers.** If inbound leads are your first bottleneck too, Piper is the agent to look at first. Slack CRM is worth a test if your sales team already coordinates in Slack, because updating a record from a message removes the step where someone has to open Salesforce to do it. **Property managers.** Casey covers service requests across voice, SMS, WhatsApp, and web chat, which is the closest fit for tenant and resident requests. One caution from our own scoping: agents run on the channels your org is licensed for. WhatsApp needs an approved business messaging integration, so check that before you plan around it. ##### The open question: managed-package objects Salesforce describes the 37 prebuilt skills as sales skills: meeting prep, deal health review, pipeline review. Nothing we read says they reach managed-package objects. The commercial brokerage we built for runs on REthink+, a managed package with its own objects. Nobody on our team has tested the beta against REthink+ or AscendixRE yet. Treat this as unverified. If your deals and properties live in a managed package, it is the first thing to test in a sandbox before you plan anything around Claudeforce. Two paths appeared this week that could change the answer. The Headless 360 MCP Server is the generic way for Claude to reach objects in an org, and the new AgentExchange lists third-party agents, skills, and MCP servers, which a package vendor could publish. Whether REthink or Ascendix lists one is a question for the vendor. Neither path has been tested by us against a managed package. #### We built this pattern before Claudeforce was announced For a US commercial real estate brokerage, we built a similar shape: Claude as the working layer, Salesforce with REthink+ as the record, and Slack as the front door. A broker drops a site photo or a business card into Slack, and the contact or activity record updates in the CRM. Daily operations work went from about 8 hours to 15 to 20 minutes per role, a figure the client confirmed in July 2026 (see the [case study](/case-studies/ai-operations-layer-for-us-cre-brokerage)). To be precise about the comparison: ours is 12 custom Claude Skills and 3 Routines built for one firm. AIforce claims to be a platform layer that carries permissions across every interface. Ours is a different and far smaller thing. It does show the pattern holds up in a working brokerage. #### The catch inside the safety story Every request in AIforce runs on your existing permissions and your existing data. That is why Salesforce can call it governed. Marc Benioff said in the keynote: "your data is your data. It does not go in the models." That is a statement about training. It says nothing about what a permitted user can now simply ask for. Every problem already in your org comes along. - **Duplicate contacts.** The agent cannot tell which one is real. - **Loose sharing rules.** Anything a user could technically see, they can now simply ask for. - **A pipeline nobody trusts.** Now delivered in Slack as a confident answer. Until now, bad records mostly produced bad reports. With an agent acting on the records, they produce actions taken on bad data. #### What to do this quarter 1. **Clean the record first.** Duplicates, ownership, and sharing rules. Agents inherit all of it. Security Center Essentials is free and is the fastest way to see the sharing rules part. 2. **Pick one daily job and measure it.** Write down how many hours it takes today, before anything is built. Without the before, there is no return to report. 3. **Test the Salesforce in Claude beta in a sandbox.** If you run a managed package, test object reach first. 4. **Prototype in Builder Central after September 21.** Free, sandbox only. If the prototype works, the production build is the next decision, not an automatic step. 5. **Wait on Koa.** Pilot only, US general availability expected in winter. The cost of this order of work: weeks of unglamorous cleanup with nothing to demo at the end of it. It is still the right order, because every interface announced this week reads from the same record. If you want a starting point, the [Real Estate AI Assessment](/resources/real-estate-ai-assessment) scores your org across ten questions and shows where the gaps are. #### Frequently Asked Questions ##### Did Salesforce announce anything specific to real estate at Dreamforce 2026? Not in the announcements and coverage we read across all three days. The launches were horizontal: AIforce, Claudeforce, Slackforce, the job-ready agents, Koa, and the Day 3 admin and architect tooling. The closest thing was the Admin keynote demo customer, a fictional smart-home company. Real estate teams have to map the announcements to their own workflows. ##### What is AIforce? Salesforce's interface layer that carries CRM data, permissions, and workflows into Claude, Slack, and Lightning, so people can work with Salesforce without opening the Salesforce UI. ##### Does Claudeforce work with REthink+ or AscendixRE? Unverified. Salesforce describes the 37 prebuilt skills as sales skills, and nothing we read says they reach managed-package objects. We have not yet tested the beta against either package. Test it in a sandbox first. ##### Which job-ready agent should a real estate team look at first? For brokerages and developers, Piper, for inbound lead qualification. It has the clearest metric, which is speed to first qualified response and the share of leads that reach a booked appointment. For property managers, Casey is the closer fit. ##### Should we wait for Koa before starting an Agentforce project? No. Koa is available to select pilot customers only, with US general availability expected in winter 2026. The preparation work, which is clean data and one measured workflow, is the same whichever model runs underneath. ##### What was announced on the final day of Dreamforce 2026? No press releases. The Admin keynote announced Builder Central, a free no-code builder in beta from the week of September 21 that deploys to a sandbox, and Security Center Essentials, a free security dashboard. The Architect keynote showed the Headless 360 MCP Server, in open beta with general availability in November, and Scoped Access Definitions, with no date. The Data 360 keynote announced the Agent Context Engine, with general availability in December 2026. ##### What do the new products cost? Pricing is not stated in the announcements for AIforce, Salesforce in Claude, the job-ready agents, or Koa, and Salesforce notes pricing and packaging are subject to change. Our [pricing page](/pricing) covers what we charge for implementation. Salesforce licenses are bought from Salesforce. #### Sources All Salesforce figures above are as reported by Salesforce or by the coverage linked here. We have not independently measured any of them. - [Salesforce: Dreamforce 2026 media resources](https://www.salesforce.com/news/dreamforce-26-media-resources/) - [Salesforce: AIforce announcement](https://www.salesforce.com/news/stories/aiforce-announcement/) - [Salesforce: Claudeforce press release](https://www.salesforce.com/news/press-releases/2026/08/26/salesforce-and-anthropic-announce-claudeforce/) - [Salesforce: job-ready AI agents](https://www.salesforce.com/news/stories/agentforce-job-ready-ai-agents/) - [Salesforce: Koa reasoning model](https://www.salesforce.com/news/press-releases/2026/09/15/koa-reasoning-model/) - [Salesforce Ben: AIforce launch](https://www.salesforceben.com/salesforce-launches-aiforce-at-dreamforce-26-ai-replaces-the-ui/) - [Salesforce Ben: Agentforce keynote roundup](https://www.salesforceben.com/complete-roundup-of-the-agentforce-keynote-at-dreamforce-26/) - [Salesforce Ben: six takeaways from the main keynote](https://www.salesforceben.com/the-6-biggest-takeaways-from-the-dreamforce-26-main-keynote/) - [Salesforce Admins: Dreamforce 2026 product highlights for admins](https://admin.salesforce.com/blog/2026/dreamforce-2026-product-highlights-for-admins) - [Salesforce: Introducing Builder Central](https://www.salesforce.com/blog/builder-central-ai-development/) - [Salesforce Ben: Architect keynote and the new Well-Architected Framework](https://www.salesforceben.com/new-well-architected-framework-and-agent-revealed-at-dreamforce-26/) - [Salesforce Ben: Data 360 updates from Dreamforce 2026](https://www.salesforceben.com/top-salesforce-data-cloud-updates-from-dreamforce-26/) - [Salesforce Ben: the new AgentExchange](https://www.salesforceben.com/appexchange-slack-marketplace-and-the-agentforce-ecosystem-are-now-one-with-fresh-50m-funding/) ### Agentforce for Real Estate: 4 AI Agents That Pay for Themselves URL: https://phenoble.com/blogs/agentforce-for-real-estate-four-agents-that-pay-for-themselves Author: Sachin Sharma | Published: Wed Sep 16 2026 00:00:00 GMT+0000 (Coordinated Universal Time) | Updated: Thu Sep 24 2026 00:00:00 GMT+0000 (Coordinated Universal Time) Every real estate operator has now sat through an AI demo. The agent answers a question about a listing, the room nods, and nothing ships, because nobody in the room could say what the agent would be measured on or what it would cost per month to run. This post answers both. It covers the four Agentforce agents we deploy for real estate teams, the one metric each has to hit before we call it a success, and what Salesforce actually charges to run an agent as of September 2026. If you cannot name the metric and the cost, you are not ready to fund the agent, and that is fine. Most AI projects that miss their return miss it because the metric was never written down. #### What an Agentforce agent is, in operator terms Agentforce is Salesforce's platform for AI agents that work inside your org. An agent has topics (the jobs it is allowed to do), actions (the things it can read or change in Salesforce, usually built with Flow), and guardrails (what it must never do without a human). It runs in Salesforce, on your data, under your permission model. The difference from a chatbot is that an agent takes actions on records. It does not tell the salesperson to schedule a site visit; it creates the event, sends the confirmation, and logs it. #### Agent one: 24/7 portal lead qualification **Who it is for:** brokerages and developers receiving leads from portals, the website, and paid campaigns. **The problem:** a portal lead that hits an inbox at 9 pm gets a reply at 10 am, if the salesperson is not at a site visit. By then the buyer has spoken to two other agents. **What the agent does:** replies within seconds, asks the three or four questions that qualify the lead (budget, timeline, location, financing), creates or updates the Lead with the answers, and books a call or a site visit with the right person. Anything it cannot answer escalates to a human with the transcript attached. **The metric:** speed to first qualified response, and the share of leads that reach a booked appointment. We built this pattern for a US commercial brokerage; the case study on this site covers how site photos, business cards, and signed pages went from a Slack drop to an updated CRM record without a human retyping anything. #### Agent two: listing and inventory inquiry **Who it is for:** brokerages with active listings and developers with unit inventory. **The problem:** the same questions arrive hundreds of times. Is unit 1204 still available. What is the price on the 2 BHK on floor 8. Is the warehouse on the north side still listed. Each one costs a salesperson a lookup and a reply. **What the agent does:** reads Listing or Unit records and answers with live availability, price list version, and the next step. For developers, it respects holds: a unit on hold reads as unavailable until the hold expires. It never quotes a price that is not on the current price list, because it can only read the record. **The metric:** inquiries resolved without a human, and the lag between a price list change and the first correct quote after it. #### Agent three: lease and document intelligence **Who it is for:** commercial brokerages, lease administrators, and property managers. **The problem:** the terms of a lease live in a PDF. Critical dates, escalation schedules, renewal options, and CAM clauses are typed into a spreadsheet by an analyst, and the spreadsheet is wrong about one in every batch. **What the agent does:** reads the uploaded lease, extracts the fields you define into the Lease record and its Critical Date children, and flags anything it is not confident about for a human to confirm. The human reviews exceptions instead of retyping every field. **The metric:** hours of abstraction per lease, and the exception rate the reviewer has to touch. #### Agent four: tenant service **Who it is for:** property managers, residential and commercial. **The problem:** tenant requests arrive by phone, email, and WhatsApp with no shared queue. Status questions generate repeat calls. Nobody knows the cost per work order because the vendor invoice and the request never meet. **What the agent does:** takes the request on the channel the tenant used, creates the Case and the Work Order, dispatches to the right vendor by trade and SLA, answers status questions from the record, and closes the loop when the vendor marks it done. Anything involving a safety issue, a cost above threshold, or an angry tenant goes to a human immediately. **The metric:** requests handled end to end without a human, and cost per work order once vendor cost is on the record. #### What Salesforce charges to run an agent This is the part most posts skip. The figures below are from Salesforce's published pricing as of September 2026; confirm them on Salesforce's own pricing page before you budget, because they change. - **Usage.** Agentforce is metered. Flex Credits are sold at $500 per 100,000 credits, and a standard agent action consumes 20 credits, so roughly $0.10 per action. Conversation-based pricing is $2 per conversation. - **Seats.** On September 3, 2026 Salesforce introduced Core, Advanced, and Max editions at $195, $395, and $550 per user per month, and each bundles Flex Credits into the seat. Existing Enterprise and Unlimited customers keep their pricing and add Agentforce through an add-on or Flex Credits. - **Prerequisite.** You need a supported edition before an agent can go live. This is the single most common reason a pilot stalls in week one, so we check it in the free audit before anything is scoped. Implementation is separate from all of the above, and ours is fixed price: an Agentforce Pilot in your sandbox is $1,500 for 7 days, and a production Launch is $4,500 over 2 weeks. Both numbers are on our pricing page. #### Why most AI projects miss their return Three reasons, in the order we see them. 1. **No metric.** The agent was funded on a demo. Without a number it cannot fail, which also means it cannot succeed, and the budget quietly disappears at renewal. 2. **Bad data.** An inventory agent on top of a spreadsheet-fed Unit object quotes wrong prices with total confidence. The data readiness check is not a formality; it decides whether the agent should be built at all. 3. **No guardrails.** An agent that can close an Opportunity or delete a Contact without confirmation will eventually do so. Guardrails are configured, tested, and signed off before go-live, not added after the first incident. #### How we prove an agent works before it goes live Salesforce ships a testing tool for agents. We write each test conversation with the topic, action, and reply we expect, run the batch in your sandbox, and hand you the pass and fail report. An agent that has not passed its scripted tests is a demo. An agent that has is a deployment. #### Frequently Asked Questions ##### Which Agentforce agent should a real estate team start with? Lead qualification, almost always. It has the clearest metric, the least data dependency, and the shortest path to a number the sales head cares about. ##### How much does Agentforce cost per month? Usage is metered by Salesforce at published rates, currently $500 per 100,000 Flex Credits or $2 per conversation, on top of a supported seat. The exact monthly figure depends on volume, which is why we size it during the audit rather than guess. ##### Does an Agentforce agent need clean data? Yes. An agent reads records and acts on them. If the records are wrong, the agent is confidently wrong. Data readiness is checked before an agent is scoped. ##### Can the agent work on WhatsApp? Agents run on the channels your org is licensed for. WhatsApp requires an approved business messaging integration and is scoped as an add-on, not included in a standard pilot. ##### How long does it take to deploy a first agent? A sandbox Pilot takes 7 days from the day we have access. A production Launch takes 2 weeks, followed by 30 days of fixes. ### Salesforce for Property Management: From Work Orders to Tenant AI URL: https://phenoble.com/blogs/salesforce-for-property-management-work-orders-to-tenant-ai Author: Sachin Sharma | Published: Mon Sep 14 2026 00:00:00 GMT+0000 (Coordinated Universal Time) | Updated: Wed Sep 16 2026 00:00:00 GMT+0000 (Coordinated Universal Time) A property manager's day is a queue nobody can see. Tenant requests arrive by phone, email, and WhatsApp. Work orders go to vendors by text. Status questions come back to the office because the tenant has no other way to ask. At month end, the vendor invoices arrive and nobody can say what a work order actually cost, because the request and the invoice never met in the same system. Property management software exists, and much of it is good at accounting. The reason operators move the service side onto Salesforce is that the accounting system was never built to run a service queue, a vendor network, a leasing pipeline, and a tenant channel at the same time. Salesforce was. This post covers how we set that up, where an Agentforce tenant service agent pays for itself, and the guardrails it needs before it is allowed near tenant data. #### The service model: Case, Work Order, Vendor Three objects carry the operation. - **Case** is the tenant's request as the tenant sees it. A leaking tap, a broken access card, a noise complaint. It has a channel, a tenant, a unit, a priority, and an SLA clock that starts when the request lands, not when someone reads it. - **Work Order** is the job as the vendor sees it. One Case can produce several Work Orders (a plumber and a painter for one leak), and each carries the trade, the vendor, the scheduled time, and the cost when the invoice arrives. - **Vendor** is the account for each contractor, with trades, coverage area, SLA history, and a scorecard built from the Work Orders they completed. When the scorecard is a report, vendor renewals stop being a matter of who complained loudest. With those three in place, cost per work order is a report: Work Order cost grouped by trade, by property, by vendor, by month. That single report is usually the thing that justifies the project to the owner. #### Dispatch that does not depend on memory Dispatch is where a manual operation leaks money. The wrong trade sent, the vendor who was closest not called, the emergency that waited because the text went to someone on leave. On Salesforce, dispatch is a rule. A Work Order with a trade and a property looks up vendors who cover that trade and that area, ranks them by SLA performance and current load, and assigns. The vendor gets the job on their phone with the unit, the access instructions, and the tenant's preferred window. When the vendor marks it complete and attaches the invoice, the Work Order closes, the Case updates, and the tenant gets a message asking whether the problem is solved. For operators with in-house technicians, Salesforce Field Service adds scheduling, routing, and a technician mobile app on top of the same objects. For operators who use vendors only, Flow automation on Work Order is enough and considerably cheaper. #### Lead-to-lease on the same platform The leasing side uses the objects Salesforce already has. A Lead is a prospective tenant. An Opportunity is an application for a specific unit, with stages for inquiry, tour, application, screening, approval, and lease signed. The Unit is a custom object shared with the service side, so the leasing team sees turn status and the service team sees move-in dates. The reason to run leasing here rather than in a separate tool is the handoff. A signed lease creates the tenant record, the unit status flips to occupied, and the first service request from that tenant lands against a record that already knows who they are and where they live. Renewal risk scoring, which combines lease end date, open Cases, and payment history, only works when all three live in one system. #### Where the Agentforce tenant agent earns its cost An Agentforce agent is an AI agent that runs inside Salesforce, reads and writes records under your permission model, and hands off to a human when a rule says so. For property management, one agent covers the highest-volume, lowest-judgment work: - **Intake.** The tenant describes the problem on WhatsApp, the portal, or email. The agent asks the two or three questions a good coordinator would ask (which room, is water actively leaking, is anyone in danger), creates the Case with the right priority and trade, and confirms to the tenant with a reference number. - **Status.** "Is someone coming today" is answered from the Work Order, on the channel the tenant used, without a call to the office. - **Close the loop.** When the vendor marks the job done, the agent asks the tenant whether it is resolved and reopens the Case if not. - **Reminders and notices.** Inspection windows, planned maintenance, and renewal notices go out from the record and log the response. The metric is the share of requests handled end to end without a human touching them, and cost per work order once vendor cost is on the record. If the agent does not move both, it is not paying for itself, and we say so. What Salesforce charges to run an agent is metered and published; as of September 2026, Flex Credits are $500 per 100,000 with a standard action at roughly $0.10, or $2 per conversation, on top of a supported seat. We size that during the audit rather than guess, because a portfolio's request volume is the whole cost. #### The guardrails, before the agent touches tenant data An agent with access to tenant records is a liability until the rules are configured and tested. These are the ones we do not go live without. 1. **Safety escalates immediately.** Gas smell, flooding, no heat in winter, security breach, or any message that reads as distress goes to a human within the same minute, with the transcript. The agent never triages a safety issue. 2. **Cost thresholds need a human.** The agent can dispatch within the pre-approved amount for the trade. Anything above it creates the Work Order in a pending state and routes for approval. 3. **Tenant data stays with the tenant.** The agent answers only about the unit and Cases belonging to the person it is talking to, enforced by Salesforce sharing rules, not by the prompt. 4. **No lease or financial changes.** Rent, lease terms, deposits, and notices to vacate are out of scope. The agent can explain where to find them and route the request; it cannot change them. 5. **Angry goes to a human.** A tenant who has escalated tone, or who has asked for a person, gets one. 6. **Tested before live.** Salesforce ships a testing tool for agents. We write the scripted conversations, including the ones designed to trick the agent into breaking rules one to five, and the agent does not go to production until the batch passes. #### What this replaces, and what it does not Salesforce does not replace the accounting system. Rent roll, ledger, and owner statements stay where they are, and the two systems exchange tenant, unit, and invoice data through an integration scoped per system. What Salesforce replaces is the queue: the inbox, the WhatsApp group, the vendor texts, and the spreadsheet that tried to hold them together. #### What it costs Every price is on our pricing page. A fixed-scope Real Estate Salesforce Quickstart for one team starts at $8,000. An Agentforce Pilot that proves the tenant agent in your sandbox is $1,500 for 7 days, and the production Launch is $4,500. The free Real Estate AI Audit comes first, and the number is written down before you commit. #### Frequently Asked Questions ##### Can Salesforce replace our property management software? It replaces the service and leasing operation, not the accounting. Rent roll and ledger stay in your existing system and integrate with Salesforce for tenant, unit, and invoice data. ##### Do we need Salesforce Field Service? Only if you have in-house technicians who need scheduling, routing, and a mobile app. Vendor-only operators run dispatch on Work Order automation without it. ##### How does the tenant agent know which tenant it is talking to? Through the channel identity (phone number, portal login, or email) matched to the tenant record, with Salesforce sharing rules limiting what the agent can read to that tenant's own unit and Cases. ##### What is a realistic first scope for an Agentforce tenant agent? Intake and status for maintenance requests on one channel, with safety and cost escalation rules. Reminders, renewals, and additional channels come after the first scope proves its number. ##### How is cost per work order calculated? Vendor cost is captured on the Work Order when the invoice is attached, so the report is Work Order cost grouped by trade, property, vendor, and period. It only works if every job is a Work Order, which the agent's intake enforces. ### AscendixRE vs Rethink vs Custom: Choosing a Salesforce Foundation for Commercial Real Estate URL: https://phenoble.com/blogs/ascendixre-vs-rethink-vs-custom-salesforce-commercial-real-estate Author: Sachin Sharma | Published: Wed Sep 09 2026 00:00:00 GMT+0000 (Coordinated Universal Time) | Updated: Wed Sep 16 2026 00:00:00 GMT+0000 (Coordinated Universal Time) Salesforce ships no product called Real Estate Cloud and no native Property, Listing, Deal, or Comp objects. A commercial brokerage that wants Salesforce to understand its business has three options: install AscendixRE, install Rethink, or build the objects itself. We implement all three, and we do not sell either package, so this comparison has no product to protect. Every factual claim below about the two packages was checked against the vendor's own site or its AppExchange listing in September 2026. Prices and features change; confirm them on the listing before you sign. #### The two packages at a glance **AscendixRE**, by Ascendix Technologies, is a managed package on the Salesforce AppExchange, listed since 2014 and last updated December 2025. Its listing rates 4.98 stars from 91 reviews. Ascendix positions it for commercial real estate: tenant rep and landlord rep brokers, commercial mortgage brokers, and capital markets teams. Published pricing is $79 per user per month for the Foundations tier and $99 for Enterprise, billed annually, with the Salesforce licence included in that figure. An AI Suite add-on, launched in June 2026, is priced per organization from $39 per month and is available on Enterprise only. **Rethink**, now owned by Buildout after a February 2021 acquisition, is also a managed package on the AppExchange, listed since 2009 and last updated July 2025. Its listing rates 4.80 stars from 210 reviews. Buildout positions it for brokers and brokerages across investment sales, leasing, tenant rep, and capital markets. Published pricing is $129 per user per month for Rethink and $299 for Rethink+, which added ownership data and AI owner research in August 2025. Buildout prices on seat count plus a platform maintenance charge whose amount is not published. Neither vendor publishes a minimum seat count or a setup fee. #### What each package models **AscendixRE** names Property, Listings, Availabilities, Lease, Sale, Deals, Contacts, and Capital Sources on its Foundations tier. Enterprise adds Stacking Plans, Commission Calculations, custom objects, and its search and document composer tools. Commission processing, meaning invoices, vouchers, and payouts, is part of the product. **Rethink** names contact management, a property and listing database, comps tracking, deal pipeline management with Buyer Rep, Seller Rep, Landlord Rep, and Tenant Rep deal types, stacking plans, map-based property search, and dashboards. Rethink+ adds property ownership data and predictive analytics. We could not find a commission or back-office module named on Buildout's current pages, so treat commissions as something to verify in a demo rather than assume. **Custom objects** model whatever you define. The brokerage-grade minimum we build is Property, Listing, Deal, Comp, Requirement, and Commission Split, with Contact and Account standard. Nothing is included until you build it, and nothing is missing once you have. #### The decision criteria We use six questions. The order matters: the first two eliminate options faster than the rest. ##### 1. Does your workflow match the package's workflow? Both packages were built for the classic CRE brokerage: listings, deals with a side, comps, stacking plans. If that is your business, a package gives you a decade of refinement for the price of a seat. If your business is a developer that also brokers, a brokerage that runs property management, or a firm whose deal is a lease program rather than a transaction, you will spend the first six months building around the package. That is the signal to build instead. ##### 2. Who carries the org after go-live? A package comes with upgrades and vendor support. A custom build comes with an admin, either yours or a retainer. Under 50 users with no Salesforce admin on staff: package. An existing customized org with an admin who owns it: custom is viable and a package on top of a heavily customized org is where upgrade conflicts live. ##### 3. Are commissions your pain? If month-end split reconciliation is the reason for the project, AscendixRE names commission calculation and processing as a product feature. Rethink's current pages do not, and a custom Commission Split object with Flow automation does it exactly the way your house rules work, at the cost of building it. This is the one criterion where we most often see a package plus a thin custom layer: the package for the front office, a custom object for splits. ##### 4. What happens to your data if you leave? Managed packages own their objects. Records migrate, automations and page layouts do not. If the data model has to be yours for governance or exit reasons, build it. If the brokerage will be on the package for years, this matters less than the vendor's update cadence, and both packages have updated within the last year. ##### 5. What is the real per-user cost? AscendixRE's published price includes the Salesforce licence; Rethink's does not say so on its pricing page and Buildout adds a maintenance charge. A custom build has no package fee but carries Salesforce seats and the implementation. Put all three on one sheet per user per year, with implementation amortized over the term, before comparing. The cheapest sticker is not reliably the cheapest total. ##### 6. Where does AI fit? Ascendix launched an AI Suite in June 2026 that connects to ChatGPT and Claude, parses email, and generates documents, and its Enterprise pricing bundles Salesforce Agentforce credits. Ascendix also lists as an Agentforce implementation consultancy. We found no Agentforce announcement from Buildout for Rethink. A custom build runs Agentforce natively on your objects, which is the most flexible option and the one that depends entirely on the data model being clean. #### Migration and integration lessons from delivery Three things we have hit that no comparison table shows. - **Package objects and your old CRM's fields rarely map one to one.** Budget a mapping workshop before migration, not a script after it. The fields that fall through are always the ones a broker cares about. - **Email and calendar sync should be live on day one of user rollout,** regardless of package. It is the one integration that earns adoption on its own. - **Do not customize the package's own objects beyond fields and layouts.** The moment you write automation against a package object's internal behavior, the next vendor update becomes a project. #### When a consultant changes the math Both vendors handle onboarding themselves, and for a standard brokerage on a standard workflow, self-implementing a package with vendor onboarding is a reasonable path. A partner earns their fee in three situations: the workflow does not fit and someone has to design the custom layer, the migration is from a customized legacy org, or the brokerage wants Agentforce agents on top and needs the data model made agent-ready first. We publish our prices. A fixed-scope Real Estate Salesforce Quickstart starts at $8,000, and the free audit comes first so the decision above is made on your data, not on this post. #### Frequently Asked Questions ##### Is AscendixRE or Rethink better? Neither is better in general. AscendixRE names commission processing and includes the Salesforce licence in its published price. Rethink has the larger review base on AppExchange and adds ownership data in Rethink+. The right one depends on your workflow, your team size, and whether commissions are the problem you are solving. ##### Does Salesforce have a native real estate CRM? No. Salesforce has no Real Estate Cloud and no standard Property or Listing objects. Its only real-estate-adjacent industry data model is the mortgage model in Financial Services Cloud, which is built for lenders, not brokerages. ##### Can we use a package and custom objects together? Yes, and it is common. The package handles Property, Listing, and Deal; custom objects handle what the package does not model, such as house-specific commission rules. Keep custom automation off the package's own objects. ##### How much do the packages cost? As published in September 2026: AscendixRE $79 or $99 per user per month billed annually with the Salesforce licence included; Rethink $129 or $299 per user per month plus an unpublished platform maintenance charge. Neither publishes minimum seats or setup fees. Confirm on the AppExchange listings before budgeting. ### Lead-to-Booking on Salesforce: A CRM Blueprint for Property Developers in India and the GCC URL: https://phenoble.com/blogs/lead-to-booking-salesforce-property-developers-india-gcc Author: Sachin Sharma | Published: Fri Sep 04 2026 00:00:00 GMT+0000 (Coordinated Universal Time) | Updated: Wed Sep 16 2026 00:00:00 GMT+0000 (Coordinated Universal Time) Ask a developer's sales head what happened on launch day and you get the same story from Gurugram to Dubai. Two channel partners claim the same buyer. A unit gets sold twice because the hold expired in someone's head but not in the system. The price list changed at 11 am and half the team quoted the old one. By the end of the week, the truth about who booked what lives in a WhatsApp group and a spreadsheet that three people edit. None of this is a people problem. It is a data model problem. The CRM was set up to track leads, and a developer does not sell leads. A developer sells inventory. This is the blueprint we use when a property developer in India or the GCC moves lead-to-booking onto Salesforce. It is written for the sales head and the CFO, not for the admin. #### The object model: inventory first The mistake is starting with Lead and Opportunity. Start with what you are selling. - **Project**, then **Tower**, then **Floor**, then **Unit.** A unit has a type, a carpet and built-up area, a facing, and a status: available, on hold, booked, allotted, handed over. That status field is the most important field in the org. - **Price List**, versioned. A price list belongs to a project and has an effective date. When the price changes, a new version is created and the old one stays for audit. Every quote references the version it was made from, so "which price did you promise" is a lookup, not an argument. - **Hold**, with an expiry. A hold is a record, not a note. It has a unit, a buyer, a channel partner if any, a created time, and an expiry time. When the expiry passes, an automation flips the unit back to available and notifies the salesperson. No human has to remember. - **Booking**, then **Payment Milestone**, then **Allotment**, then **Handover.** Each is its own record with its own dates, so receivables reporting reads from the system instead of from finance's memory. Lead and Opportunity still exist. They sit on top of this model, not instead of it. A lead converts to a buyer, a buyer holds a unit, a hold becomes a booking, a booking has milestones. #### Double-booking prevention at the record level Every developer has been told "the CRM prevents double booking" and every developer has seen it happen anyway. The reason is that the prevention was a warning, not a rule. On Salesforce it can be a rule. The Unit's status is controlled by automation that fires when a Hold or Booking is created. If a second Hold is created against a unit that already has an active hold, the record is rejected before it saves, with a message naming the existing hold and its expiry. That is a validation, not a popup someone can click through. Launch day changes completely when this is true. The inventory dashboard shows available, held, and booked counts per tower in real time, and every salesperson on the floor sees the same numbers because there is only one place the numbers come from. #### Channel partners: attribution with a timestamp Channel partner disputes cost developers more than any other single process failure, because the cost is paid twice: once in commission paid to the wrong partner, and again in the partner relationship that sours when the dispute goes against them. The fix is boring and it works. A Channel Partner object with registration details and the partner's RERA registration number where applicable. A lead attribution record created the moment a partner submits a lead, with a server timestamp the partner cannot edit. A dispute audit trail that shows both claims side by side with their timestamps. When two partners claim the same buyer, the answer is the earlier timestamp, and both partners can see it. Most disputes end there. The ones that do not get escalated with a record, not a memory. On top of attribution sit the pieces partners actually care about: tiered commission calculation based on the booking value and the partner's tier, payout tracking against milestones, and a self-service portal on Experience Cloud where a partner sees their leads, their bookings, and what they are owed. Partners who can see their own pipeline stop calling your sales team to ask. #### WhatsApp is the channel, Salesforce is the record Buyers in India and the GCC live on WhatsApp. Fighting that is pointless. The goal is not to move buyers off WhatsApp; it is to make sure everything that happens on WhatsApp lands on the record. Site visit scheduling, document collection for KYC and booking, and payment reminders against milestones all run on WhatsApp through an approved business messaging integration, and each message is logged to the buyer and the booking in Salesforce. The salesperson works in the chat. The CFO reads the record. This is also where an Agentforce agent earns its place. A no-show recovery agent that follows up a missed site visit within the hour, a payment milestone chaser that sends the reminder and logs the response, and a first-line qualification agent for portal leads at 2 am. Each is one topic, one workflow, and one number that tells you whether it paid for itself. #### The compliance layer Regulators in these markets want reports that a spreadsheet cannot reliably produce. In India, RERA-registered projects carry disclosure and receivables reporting obligations that vary by state authority. The reports are only as good as the booking and payment records behind them. When Booking and Payment Milestone are real records with real dates, the reporting is a query. When they are rows in a spreadsheet, the reporting is a project every quarter. In Dubai, off-plan sales run through escrow accounts and DLD registration steps. Modeling the escrow milestone and the registration step as stages on the Booking gives the finance team a live view of where every unit sits, instead of reconciling the bank statement against the sales sheet at month end. We are not lawyers and this is not compliance advice. The point is narrower: the reports your CFO signs should read from records, and the records should exist in one system. #### What this replaces Developers in India already have purpose-built CRMs from local vendors, and many of them are good at lead management. The reason large developers move to Salesforce is not features. It is that the group already standardized on Salesforce for something else, the finance team wants one system of record, and the inventory, partner, and compliance model above does not fit inside a lead management tool without becoming custom development anyway. #### What it costs Every price is published on our pricing page. A fixed-scope Real Estate Salesforce Quickstart for one sales team starts at $8,000. The free Real Estate AI Audit comes first, and the number is written down before you commit. #### Frequently Asked Questions ##### Can Salesforce handle unit-level inventory for a residential project? Yes, with a custom object hierarchy of Project, Tower, Floor, and Unit and a controlled status field on Unit. Salesforce does not ship these objects natively; they are built as part of the implementation. ##### How does hold expiry work on Salesforce? A Hold is a record with an expiry timestamp. A scheduled automation checks for expired holds, flips the unit back to available, and notifies the owner. No one has to remember to release inventory. ##### Can channel partners log in to see their own leads? Yes. An Experience Cloud portal gives each partner a view of their leads, bookings, and commission status, scoped so they see only their own records. ##### Does this work with WhatsApp? Yes, through an approved WhatsApp Business integration. Messages for site visits, documents, and payment reminders are sent from the system and logged to the buyer and booking records. ##### Is RERA reporting automatic? The reports read from Booking and Payment Milestone records, so they can be produced from the CRM on demand. What each state authority requires, and how often, is a compliance question for your advisors. ### Salesforce for Real Estate: The Implementation Playbook for Brokerages URL: https://phenoble.com/blogs/salesforce-for-real-estate-brokerage-implementation-playbook Author: Sachin Sharma | Published: Tue Sep 01 2026 00:00:00 GMT+0000 (Coordinated Universal Time) | Updated: Wed Sep 16 2026 00:00:00 GMT+0000 (Coordinated Universal Time) Most brokerage Salesforce projects fail the same way. The org goes live, the managing broker is happy for a month, and by quarter end the agents are back in their phones and spreadsheets. The pipeline in Salesforce is a lagging copy of reality, and the back office still reconciles commissions by hand. The cause is almost never the software. It is that the org was built as a generic sales CRM with the words changed. Opportunity renamed to Deal. Account renamed to Property. That gets you a demo, not a brokerage system. This is the playbook we use when a brokerage asks us to implement Salesforce for real estate. It covers what the org has to model, when to buy a package instead of building, and the rollout order that protects agent adoption. #### Why a renamed Opportunity is not a Deal A commercial deal has parties on both sides, a property, a listing that may or may not be yours, comps that justify the number, and a commission that splits across brokers, teams, and the house. An Opportunity has an Account, an Amount, and a Stage. You can bolt custom fields onto Opportunity until it looks like a deal. Three things break when you do: - **Reporting.** A broker wants production by property type and by deal side. The house wants GCI by month with splits applied. If the deal side, the property, and the split live in text fields on Opportunity, none of that is a report. It is an export. - **Relationships.** One property has many listings over its life. One deal references one listing, many comps, and two or more brokers. Salesforce handles this well when those are separate objects with real lookups, and badly when they are fields. - **Automation.** Hold expiry on a listing, a commission voucher on close, a comp record created from a closed deal. Each of these is a Flow on a specific object. If there is no object, there is nothing to trigger. The brokerage-grade minimum is six objects: Property, Listing, Deal, Comp, Requirement (what a tenant or buyer is looking for), and Commission Split. Contact and Account stay standard. Everything else is optional until a report demands it. #### Package or custom: the decision that sets the budget There are two mature managed packages for commercial brokerages on the Salesforce AppExchange, and both ship the objects above in some form. Buying one is the right call more often than a consultancy likes to admit. Building custom objects is the right call in a narrower set of cases than a brokerage usually thinks. Buy a package when: - Your workflow matches the package's workflow. Tenant rep, landlord rep, investment sales, and capital markets are all covered by the leading packages. If you do those and only those, you are paying for a decade of other brokerages' edge cases. - You have fewer than 50 users and no dedicated Salesforce admin. Packages come with upgrades and support you do not have to staff. - Commission handling is your pain and the package already does splits, vouchers, and payouts. Build custom objects when: - Your deal structure does not fit. Mixed-use developers who also broker, brokerages that run property management, and teams whose "deal" is a multi-year lease program all hit the package walls fast. - You already own a Salesforce org with heavy customization and an admin who can carry it. Adding a managed package on top of a custom org is where upgrade conflicts live. - You need the data model to be yours. Packages own their objects. If you ever leave the package, the data migrates but the automations do not. The honest answer for many brokerages is a package plus a thin custom layer: the package for Property, Listing, and Deal, your own objects for the thing the package does not model. We wrote a separate comparison of the two leading packages against custom objects, with their current AppExchange pricing, so the choice can be made on evidence. #### The rollout order that survives contact with agents Brokerage CRM projects die from adoption, not from bugs. Agents are paid on closings, not on data entry, and any system that asks for entry before it gives value will be ignored. The rollout order below is built around that fact. ##### Phase one: the back office first Start with the people who are paid to be in the system all day. Deal administration, marketing, and accounting. Give them Property, Listing, Deal, and Commission Split with the reports they already produce by hand. When the commission statement comes out of Salesforce instead of a spreadsheet, the back office becomes the system's loudest advocate. This phase also cleans the data. Every property and contact the back office touches gets deduplicated before an agent ever sees the org. Agents forgive a lot, but not duplicate contacts. ##### Phase two: give agents something before asking for anything The first thing an agent sees in Salesforce should be a report or a page they could not get before. Their own pipeline with deal sides, their production against goal, comps on the property they are pitching this afternoon. Only after that do you ask them to log an activity. Mobile matters here more than any other phase. If the agent cannot update a deal stage from the parking lot after a tour, the update happens never. ##### Phase three: automation that removes work Now the automations that were the reason for the project. Listing expiry alerts, hold expiry that releases a listing back to available, a comp record created automatically on close, a commission voucher generated from the deal without anyone typing the split twice. This is also where an AI agent earns its place. A portal lead that hits an inbox waits hours. A portal lead that hits an Agentforce qualification agent gets a reply and a qualified record in the CRM in seconds. We have built exactly that pattern for a commercial brokerage and documented it as a case study on this site, including the part where photos and documents stopped being retyped into the CRM at all. ##### Phase four: integration Email and calendar sync should be live from phase two. Everything else waits until the data is clean and the agents are in. Marketing platforms, listing syndication, accounting, and document signing each connect to a specific object, and connecting them to a messy org copies the mess into three more systems. #### What "done" looks like A brokerage Salesforce implementation is done when three things are true: 1. The commission statement for last month came out of Salesforce, and accounting did not open a spreadsheet to check it. 2. The managing broker's Monday pipeline review runs from a Salesforce dashboard, not from asking each agent. 3. Agents log deal stage changes on their phones the same day, because the report they care about depends on it. If any of the three is false, the project is not done, no matter what the go-live date says. #### What it costs We publish every price. A fixed-scope Real Estate Salesforce Quickstart for one team starts at $8,000, and the free Real Estate AI Audit comes first so the number is written down before you commit. Managed packages carry their own per-user licence on top of Salesforce, and those figures are in the comparison post. #### Frequently Asked Questions ##### How long does a brokerage Salesforce implementation take? For a single office on a fixed scope, a Quickstart is measured in weeks. A multi-office brokerage with commission automation and integrations typically runs 6 to 10 weeks, and the variable is almost always data readiness rather than build effort. ##### Do we need a managed package to use Salesforce for real estate? No. Salesforce ships no native Property or Listing objects, so you either install a package that provides them or build them as custom objects. Both are common. The choice depends on how closely your workflow matches the package and whether you have an admin to carry a custom build. ##### Can Salesforce handle commission splits? Yes, either through a package that includes commission processing or through a custom Commission Split object with Flow automation. What matters is that the split is a record tied to the deal, not a number typed into a field, so it can be reported and audited. ##### What is the biggest reason brokerage CRM projects fail? Agent adoption. The rollout order in this playbook exists to fix that: back office first, value to agents before asking for entry, and automations that visibly remove work. ### Agentforce ROI Benchmarks: What Real Implementations Actually Deliver URL: https://phenoble.com/blogs/agentforce-roi-benchmarks-what-implementations-actually-deliver Author: Kaushal Sharma | Published: Wed Apr 01 2026 00:00:00 GMT+0000 (Coordinated Universal Time) | Updated: Wed Aug 12 2026 00:00:00 GMT+0000 (Coordinated Universal Time) Real Agentforce implementations deliver 38% to 62% case deflection, first response times cut from hours to under 2 minutes, 2.1x to 3.4x more qualified leads worked per SDR, and a first live agent in 6 to 10 weeks. Those are the headline benchmarks; the rest of this post breaks down each one and what drives the variance. Drawing on 40+ Salesforce implementations, including our Agentforce deployments for clients from nonprofits to B2B manufacturers, we started tracking the same metrics clients ask about in every discovery call. This post consolidates those benchmarks so you can set realistic expectations before you buy, budget, or go-live. --- #### Which Metrics Actually Matter Post-Go-Live? Salesforce publishes high-level stats. What's harder to find is implementation-level data broken down by use case. Here's what we see across our portfolio. --- ##### 1. Case Deflection Rate (Service Agents) **Benchmark: 38% to 62% of inbound cases** Service agents are where Agentforce delivers the most measurable ROI. Across deployments using Agentforce for customer service, including password resets, order status, return initiations, and policy lookups, we consistently see between 38% and 62% of cases fully resolved without a human agent touching the ticket. **What drives the variance:** - Knowledge base quality at go-live (the single biggest factor) - How narrow or broad the agent's topic scope is - Whether the org uses Data Cloud for personalized context - Average case complexity (transactional vs. consultative) **Real example:** A retail client processing roughly 4,200 monthly service cases went live with a scoped Agentforce agent handling order inquiries and returns. At 60 days post-launch: 44% case deflection, equating to about 73 fewer human-handled cases per week. At an internal cost of $8.20/case, that's roughly $31K annualized savings from one agent topic. --- ##### 2. First Response Time (Service) **Benchmark: From 4 to 18 hours down to under 2 minutes** This is the easiest win to show leadership. Before Agentforce, first response time in a typical SMB Salesforce org ranges from 4 hours (for orgs with solid triage flows) to 18+ hours (for orgs relying on manual inbox monitoring). After go-live, customers interacting with an Agentforce agent get an immediate, contextual response at any hour. The key word is _contextual_. A generic chatbot that says "I'll connect you with an agent" doesn't move this metric. Agentforce with a proper Knowledge base and CRM data connection gives an answer, not a handoff. --- ##### 3. SDR Productivity (Sales Agents) **Benchmark: 2.1x to 3.4x more qualified leads worked per rep per week** When we configure the [Agentforce SDR agent](/blogs/understanding-and-configuring-your-agentforce-sdr-for-sales-success) to handle inbound lead qualification, including scoring, initial outreach, and meeting booking, the human SDR shifts from volume work to closing readiness conversations. The reps we've tracked handle between 2x and 3.4x more qualified pipeline touches per week, with no headcount increase. The uplift is lower, between 1.6x and 2.1x, when the SDR agent is layered onto a messy lead routing setup or when reps aren't trained to work alongside the agent's handoffs. Implementation quality matters. --- ##### 4. Time to First Value **Benchmark: 6 to 10 weeks from contract to first live agent** One of the most common questions on discovery calls: "How long does this actually take?" The honest answer depends on scope, but here's what we see: | Deployment scope | Typical time to go-live | | ------------------------------------------- | ----------------------- | | Single-topic service agent (narrow) | 6 to 8 weeks | | Multi-topic service agent + knowledge setup | 9 to 13 weeks | | SDR agent with Salesforce CRM integration | 8 to 10 weeks | | Full Agentforce + Data Cloud integration | 14 to 20 weeks | Timelines lengthen when the org has data quality issues, no existing Knowledge articles, or when stakeholder alignment across IT/Sales/Service is incomplete at project start. --- ##### 5. Agent Containment vs. Escalation Split **Benchmark: 55% to 70% fully contained / 30% to 45% escalate to human** "Containment" means the customer's issue was resolved entirely by the AI agent with no human intervention. "Escalation" means the agent recognized the limits of its scope and handed off with context. A healthy escalation rate is not a failure: it's a sign the agent is scoped correctly. The red flag is a _low_ escalation rate paired with low CSAT, which usually means the agent is failing silently and customers are abandoning without resolution. --- ##### 6. CSAT Impact **Benchmark: +6 to +14 points on post-interaction CSAT** This one surprises clients the most. The assumption is that customers dislike AI, but a well-configured Agentforce agent that resolves an issue in under 2 minutes consistently scores higher on post-interaction surveys than a human agent resolving the same issue in 6 hours. Speed matters. Context matters. The agents that score highest are the ones with access to order history, account data, and well-structured Knowledge; not just a list of FAQs. --- #### What Does Agentforce ROI Depend On? (Honest Assessment) The benchmarks above are real, but they're not guaranteed. The orgs that hit the top of the range share these traits: **1. Clean CRM data before go-live:** Agentforce pulls from your Salesforce data. If your contact records are incomplete, your account hierarchies are messy, or your product catalog is inconsistent, the agent's responses will reflect that. Data readiness isn't optional. **2. A maintained Knowledge base:** Service agents are only as good as the articles they're grounded in. Orgs that invest in 30 to 60 well-structured Knowledge articles before launch see 2 to 3x better containment rates at 90 days. **3. Defined escalation paths:** The agent needs clear rules for when to hand off and how to pass context to the human agent. Orgs that skip this step see high escalation abandonment, meaning customers dropped mid-conversation. **4. A human in the loop for the first 60 days:** Every org we've worked with improves containment rate by 10 to 18 percentage points between week 2 and week 10 simply by reviewing escalated conversations and updating agent topics. Agentforce gets better when humans monitor and refine it. --- #### How Do These Benchmarks Compare Across Industries? | Industry | Avg. deflection rate | Avg. time-to-value | | -------------------------------- | -------------------- | ------------------ | | Retail / eCommerce | 48% to 62% | 7 to 10 weeks | | Financial Services | 35% to 50% | 10 to 14 weeks | | Healthcare / Life Sciences | 30% to 45% | 12 to 18 weeks | | Manufacturing / Industrial | 38% to 52% | 8 to 12 weeks | | Nonprofit / Education | 40% to 58% | 6 to 9 weeks | | Real Estate (brokerage, dev, PM) | Not yet published | 6 to 10 weeks | Healthcare and financial services trend lower on deflection because regulatory requirements restrict what an AI agent can resolve unassisted, not because Agentforce performs worse in those orgs. Real estate is the one row without a deflection range, and that is deliberate. Our [real estate deployments](/industries/real-estate) are recent enough that a published average would be a guess dressed as a benchmark. The time-to-value figure holds because it is scope-driven, not industry-driven: a single lead qualification, listing inquiry, or tenant service agent is the same build shape in real estate as anywhere else. We will publish a deflection range when the sample supports one. --- #### Frequently Asked Questions **Is Agentforce worth it for a small Salesforce org?** It depends on case volume. Below roughly 800 monthly service cases, the ROI math gets tighter, not impossible, but you'll want to model it carefully. Above 1,500 cases/month, the case for Agentforce is almost always clear. **How does Agentforce ROI compare to traditional chatbots?** Traditional chatbots (rule-based) typically deflect 15% to 25% of cases. Agentforce, grounded in real Knowledge and CRM data, consistently delivers 2 to 3x that rate, and with dramatically higher CSAT because it gives real answers instead of "here's a link." **What's the typical payback period?** Across our portfolio, orgs with 2,000+ monthly cases typically see full implementation cost payback within 8 to 14 months. Orgs with lower volume may be 18 to 24 months, depending on licensing costs and implementation scope. **Can I see results before committing to a full implementation?** Yes, and this is actually our recommended approach. A single-topic proof-of-concept agent scoped to your highest-volume case type gives you real containment data in 6 to 8 weeks. We use that data to build the business case for broader deployment. --- #### The Bottom Line Agentforce ROI is real, but it's not magic. The orgs that hit 60%+ deflection and 3x SDR productivity didn't get there by turning on a feature. They got there with a well-scoped implementation, clean data, and 60 days of active tuning. If you want to know what the benchmarks look like for your specific org, including case volume, data quality, and use case, [our free 30-minute audit](/contact) is exactly that conversation. We'll tell you where you sit and what realistic outcomes look like before you commit anything. Explore how we approach [Agentforce implementation](/services/agentforce) or review [what 40+ deployments have delivered for clients like yours](/case-studies). ### Integrating AWS S3 with Salesforce Data Cloud for Agentforce Agents URL: https://phenoble.com/blogs/integrating-aws-s3-data-with-salesforce-data-cloud-for-agentforce-agents Author: Kaushal Sharma | Published: Fri Jan 16 2026 00:00:00 GMT+0000 (Coordinated Universal Time) | Updated: Wed Aug 12 2026 00:00:00 GMT+0000 (Coordinated Universal Time) To integrate AWS S3 with Salesforce Data Cloud for Agentforce, you connect the S3 bucket through Data Cloud's Amazon S3 connector, ingest your CSV file with a Data Stream, map it to a custom Data Model Object, and expose it to an agent through an autolaunched Flow action. The result is an Agentforce agent that answers customer questions using product data stored in your S3 bucket. Let's start with the following steps: #### Create AWS S3 Bucket - Login your [AWS Account](https://signin.aws.amazon.com/signup?request_type=register) - Search for **Amazon S3** and click on this - Click on **Create bucket** - Enter the **Bucket name**. In my case bucket name is **my-agentforce-bucket** (Name must be unique) - To save click on **Create bucket** at the bottom - Go to inside bucket **my-agentforce-bucket** - Click on **Create folder** and Give folder name **Product Order/** - Go to inside **Product Order/** folder and Click on **Upload** and Select you your own csv file to upload. - After doing this. You have to create **AWS access key** and **AWS secret access key** to connect with salesforce - Click on your profile and go to **Security credentials** - Click on **Create access key** (Note: If you have already use that) - Select **Third-party service** option. - Click on **Next** - Now you will get access key. Copy the access key and keep it safe place. #### Create Other Connectors - Go to **Data Cloud Setup** from Gear icon - Search for **Other Connectors** in Quick Find Box - Select **Other Connectors** and Click on **New** - Select **Amazon S3** connctor type - Enter inforamtion like below image - Before save click on **Test Connection** - Click on **Save** - Now its look like this: #### Create Data Stream - Go to **Data Stream** tab in Data Cloud App - Click on **New** - Select **Amazon S3** from Other Sources. - Click on **Next** - Enter the following detail as mentioned in image - Click on **Next** - Click on **Properties** tab and select **Other** option - Select **products_id** as Primary Key - Click on **Next** - Enter the following details as mentioned in image - Click on **Next** - Entere the following details as mentioned in image - Click on **Deploy** - After Deploy Check that **Last Run Status** must be success #### How Do You Check That the Data Lake Object (DLO) Was Created? - Go **Data Lake Objects** tab. - Select **All Data Lake Object** from list views - Click **Product Order/Product_Records.csv Amazon** from table. which is category is **Other** #### Create Data Modal Object (DMO) - Click on **Data Lake Objects** tab - Click on **Start** button in the **Data Mapping** section on the right side. - Click on **Custom Data Modal** tab and click on **New Custom Object** - Enter the **Shopping Product** in the Object Label field - Than its should like below as mentioned in image. - **Object Label**: Shopping Product - **Object API Name**: Shopping_Product - Click on **Save** - Now Mappling will look like this - Let's execute the SOQL query for **Shopping Product** object - Go to the **Data Explorer** tab. From where you can see **Shopping Product** table #### Create Flow to use in Agentforce - Go to setup and Search for **Flow** - Click on **New Flow** button and Select **Autolaunched Flow (No Trigger)** - Create these below variable:(Make sure **Availability Outside the Flow** should be **Available for input** for **productId** and **title**. And apart from these 2 fields we have to make **Available for output** for others variable) - Select **Get** element add Following details - **Label**: Get Product Items - **API Name**: Get_Product_Items - **Data Source**: Data Cloud Object - **Data Space**: default - **Object**: Shopping Product - In Filter Records - Condition Requirements: - **Field** -> title **Operator** -> Equal **Value** -> title - **Field** -> products_id **Operator** -> Equal **Value** -> productId - **How many Records to Store**: Only the first record - **How to Store Record Data**: Automatically store all fields - Select **Decision** element and fill following details as mentioned in image. - Select **Assignment** element for **Assigned Products** and fill following details as mentioned in image. - Select **Assignment** element for **Show Error Message** and fill following details as mentioned in image. - Click on **Save** and give name **External Product Data Cloud Flow** #### Use Flow inside Agentforce - Go to setup and Searh for **Agentforce Agents** - Click on **+ New Agent** - Select **Create From a Template** and than **Agentforce Service Agent** - Click on **Next** and Click on all **Added** to remove default topics - Give name **Product Service Agent** and API name **Product_Service_Agent** - Add about **Company** : This agent represents MyKart , a global technology company known for designing and delivering innovative consumer electronics, software, and digital services. Apple’s product portfolio includes iPhone, iPad, Mac computers, Apple Watch. - Select **Agent user**: **EinsteinServiceAgent User (custom_service_agent@00dg5000002y0z3242345.ext)** (This is in my case) - Click on **Next** and No need to select Data Library leave it is blank - Click on **Create** #### Create Topic for Agentforce and Add Action - Go to setup and Searh for **Agentforce Agents** - Go to Product Service Agent CLick on menu button and CLick on **Open in Builder** - Click on **#Topic** and Click on **New** and CLick on **+ New Topic**. - **Name**: Product Details Inquiry - **Api Name**: Product_Details_Inquiry - **Classification Description**: Handles customer inquiries to fetch product details based on their specific question. - **Scope**: You job is only to retrieve product details as requested by the customer, ensuring the response aligns with their query, and not to address unrelated topics or perform actions outside this scope. - **Instruction 1**: If the customer provides a product title or product id, use it to fetch the relevant details. - **Instruction 2**: Provide concise and accurate product details based on the customer's request. - **Instruction 3**: If the customer provide a product id or product title than you have to show about product based on customer request. - **Instruction 4**: If customer ask for specific things like product title, price, discount percentage, discounted total, total and quantity than only show specific things.. If the customer ask for product details than show all details to a customer. - Click on **Next** and Select the actions **External Product Data Cloud Flow** - Click on **Finish** ##### Let's see quick demo #### Frequently Asked Questions **How does Salesforce Data Cloud connect to an AWS S3 bucket?** Through the Amazon S3 connector under Other Connectors in Data Cloud Setup. You supply the AWS access key and secret access key created in your AWS Security credentials, and you can run Test Connection before saving to confirm the link works. **How does an Agentforce agent access data stored in AWS S3?** The agent does not read S3 directly. A Data Stream ingests the S3 CSV into a Data Lake Object, which is mapped to a custom Data Model Object (Shopping Product in this guide). An autolaunched Flow queries that object with a Get element, and the Flow is added to the agent as a topic action. **What file format and key does this integration use?** The walkthrough uploads a CSV file into a folder in the S3 bucket, and the Data Stream uses products_id as the primary key. The Flow then filters records by product id or title to answer customer questions. **Do you need to write code to build this integration?** No. Every step in this walkthrough is configuration: the S3 connector, the Data Stream, the DLO-to-DMO mapping, the autolaunched Flow, and the agent topic are all built with point-and-click tools. --- **Want to implement this for your organisation?** [Phenoble's Data Cloud integration services](/services/data-cloud) cover the full pipeline, from S3 ingestion and identity resolution to Agentforce agent grounding. Our team has connected Data Cloud to AWS, Azure, and on-premise systems for enterprise clients. [Get a free architecture review →](/contact) ### How to Set Up the Agentforce Service Assistant (Step-by-Step Guide) URL: https://phenoble.com/blogs/how-to-set-up-the-agentforce-service-assistant-and-why-it-matters Author: Kaushal Sharma | Published: Thu Dec 25 2025 00:00:00 GMT+0000 (Coordinated Universal Time) | Updated: Wed Aug 12 2026 00:00:00 GMT+0000 (Coordinated Universal Time) You set up the Agentforce Service Assistant by creating an agent from the Service Assistant template in Agentforce Builder, defining topics, assigning service channels, turning on Service AI Grounding and the Service Assistant for Cases, and adding the component to your service pages. The assistant works in an assistive mode inside Service Cloud, giving human agents real-time guidance, recommended actions, and contextual insights during live case handling. This guide walks through each step, from prerequisites to testing. #### What is the Agentforce Service Assistant? The **Agentforce Service Assistant** is an AI-powered assistant embedded directly within Salesforce Service Cloud. It is designed to support customer service agents during live case handling by providing real-time guidance, recommended actions, and contextual insights based on the conversation and case data. Unlike fully autonomous agents, the Service Assistant works in an **assistive mode**, helping human agents respond faster, stay compliant, and follow best practices while retaining full control over customer interactions. --- #### Why Is the Agentforce Service Assistant Important? Customer service teams often deal with: - High case volumes - Repetitive questions - Complex processes and compliance requirements - The need for fast, accurate responses The Agentforce Service Assistant addresses these challenges by: - Reducing average handling time - Guiding agents with next-best actions - Ensuring consistent and compliant responses - Minimizing manual searching across knowledge articles and records - Improving overall agent productivity and customer satisfaction --- #### What Can the Service Assistant Do? The Agentforce Service Assistant can: - Analyze case context and conversation history - Recommend relevant actions and flows - Suggest knowledge articles or answers - Guide agents step-by-step through resolution processes - Trigger Salesforce actions with agent approval - Adapt suggestions dynamically as the conversation evolves --- #### Overview of the Setup Workflow Setting up the Agentforce Service Assistant typically involves: 1. Enabling Agentforce features 2. Configuring service assistant settings 3. Defining topics and actions 4. Connecting data and automations 5. Assigning the assistant to service channels 6. Testing and refining behavior 7. Turning on AI Grounding for Cases 8. Turning on the Service Assistant for Cases 9. Adding the component to the page 10. Service Assistant in Action --- #### Step-by-Step: Setting Up the Agentforce Service Assistant ##### 1. Enable Agentforce and Prerequisites Before configuring the Service Assistant, ensure the following prerequisites are met. ###### 1.1 Enable Agentforce Ensure **Agentforce** is enabled in your Salesforce org. ###### 1.2 Set Up Service Cloud Verify that **Service Cloud** is set up with Cases, Queues, and Omni-Channel. ###### 1.3 Confirm Permissions Confirm required permissions for admins and service agents. This ensures the assistant can access case data, knowledge, and automation tools. --- ##### 2. Create or Select a Service Assistant ###### 2.1 Navigate to Agentforce Builder Navigate to **Agentforce Builder** from Setup. ###### 2.2 Create or Select Agent Create a new agent using the **Service Assistant** template, or select an existing one. ###### 2.3 Provide Name and Description Provide a clear name and description that defines the assistant’s purpose (for example, “Case Resolution Assistant”). This template is optimized for assisted service workflows rather than autonomous conversations. --- ##### 3. Define Topics and Use Cases Topics define when the Service Assistant should step in. Examples include: - Case status updates - Order or entitlement lookup - Refund or escalation guidance - Troubleshooting steps - Policy or compliance checks Each topic includes instructions that guide how the assistant should interpret context and respond. --- ##### 4. Configure Guidance and Recommendations Define **how the Service Assistant guides agents** in an advisory-only mode. It does **not execute automations, update records, or trigger backend logic**. Instead, it provides text-based recommendations for agent decision-making, such as suggesting next steps, recommending knowledge articles, providing compliance reminders, summarizing case context, and offering structured guidance for complex scenarios. All guidance is displayed as read-only suggestions in the Service Console, with the human agent retaining full control. --- ##### 5. Assign Channels and Service Consoles Choose where the Service Assistant will be available, such as the Service Console, Chat or Messaging, Experience Cloud, or other supported service channels. Map the assistant to appropriate queues and Omni-Channel configurations so it activates only in relevant service contexts. Save and Activate the Agent --- ##### 6. Test and Validate the Assistant Before enabling the assistant for agents, test the assistant to ensure it provides helpful guidance without disrupting workflows. - Use **Conversation Preview** to simulate service scenarios. - Validate topic selection and action recommendations. - Adjust instructions, guardrails, and prompts based on test outcomes. - Optionally use the **Testing Center** for structured validation. Testing ensures the assistant provides helpful guidance without disrupting agent workflows. --- ##### 7. Turn on Service AI Grounding for Cases Activate the Service Assistant specifically for case handling in your Salesforce org. - Go to Service AI Grounding - Turn on Service AI Grounding for Case Fields --- ##### 8. Turn ON Service Assistant for Cases --- ##### 9. Add the Component to the Page Integrate the Service Assistant component into the relevant Salesforce pages or consoles. --- ##### 10. Service Assistant in Action Showcase the Service Assistant in action during a service interaction to verify functionality. --- #### Real-World Use Cases The Agentforce Service Assistant is especially useful for: - New agent onboarding and guided resolution - Compliance-heavy industries (finance, healthcare, insurance) - High-volume support teams - Standardized service processes - Reducing dependency on senior agents --- #### Best Practices for Implementation - Start with a **small, high-impact use case** - Use **clear and scoped topics** - Prefer **guided actions** over full automation - Test frequently in sandbox environments - Gather agent feedback and iterate continuously --- #### Conclusion The **Agentforce Service Assistant** enhances customer service by combining AI intelligence with human judgment. By guiding agents in real time, recommending actions, and surfacing relevant insights, it helps teams resolve cases faster, more accurately, and more consistently. When set up thoughtfully, it becomes a powerful co-pilot for service agents, improving both operational efficiency and customer experience. #### Output #### Frequently Asked Questions **Is the Agentforce Service Assistant autonomous?** No. Unlike fully autonomous agents, the Service Assistant works in an assistive, advisory-only mode. It does not execute automations, update records, or trigger backend logic; its guidance appears as read-only suggestions in the Service Console, and the human agent retains full control over customer interactions. **What are the prerequisites for setting up the Service Assistant?** Agentforce must be enabled in your Salesforce org, Service Cloud must be set up with Cases, Queues, and Omni-Channel, and admins and service agents need the required permissions so the assistant can access case data, knowledge, and automation tools. **Where can the Service Assistant be made available?** You can assign it to the Service Console, Chat or Messaging, Experience Cloud, or other supported service channels, and map it to the appropriate queues and Omni-Channel configurations so it activates only in relevant service contexts. **How do you test the Service Assistant before rolling it out?** Use Conversation Preview to simulate service scenarios, validate topic selection and action recommendations, and adjust instructions, guardrails, and prompts based on the outcomes. The Testing Center can optionally be used for structured validation. --- **Need expert help building your Agentforce Service Assistant?** Phenoble specialises in [Agentforce implementation for service teams](/services/agentforce), including contact centre deployments with the [Agentforce Contact Centre](/services/agentforce-contact-center). Our architects handle everything from topic configuration to Einstein Trust Layer governance. [Book a free 30-min audit →](/contact) ### How to Enable Agentforce in Your Salesforce Org (2026 Guide) URL: https://phenoble.com/blogs/how-to-enable-agentforce-in-your-salesforce-org Author: Keshav Sharma | Published: Mon Oct 27 2025 00:00:00 GMT+0000 (Coordinated Universal Time) | Updated: Wed Aug 12 2026 00:00:00 GMT+0000 (Coordinated Universal Time) ### How to Enable Agentforce in Your Salesforce Org To enable Agentforce in your Salesforce org, turn on Einstein in Einstein Setup, switch on the Agentforce toggle under Agentforce Agents, then activate the Agentforce (Default) agent in Builder. If the Agentforce icon or settings are missing from your org, it’s usually because one of these setup steps is incomplete. This guide walks through the exact process, with screenshots, so Agentforce appears properly in your Salesforce environment. #### What Is Agentforce? **Agentforce** is Salesforce’s AI-powered assistant designed to enhance productivity with generative AI capabilities. It helps automate tasks, answer queries, and deliver insights, all within your Salesforce workspace. Before using it, you must ensure that **Einstein Generative AI** is activated, since Agentforce runs on top of that foundation. #### How Do You Enable Agentforce in Salesforce? Follow these steps carefully to enable Agentforce in your Salesforce org: ##### Step 1: Open Setup - Log in to your Salesforce org. - Click the Setup (⚙️) icon in the top-right corner. ##### Step 2: Enable Einstein Generative AI - In the Quick Find box, type **Einstein Setup**. - Click Einstein Setup. - Turn ON the toggle for "Turn on Einstein". - This activates the generative AI foundation required for Agentforce. - Once done, refresh your browser. ##### Step 3: Enable Agentforce - Go back to Setup and in the Quick Find box, search for Agentforce Agents. - Open Agentforce Agents. - At the top, turn ON the Agentforce toggle. - Then, enable “Enable the Agentforce (Default) Agent.” - This ensures the default agent actions are active. - Refresh your browser again. ✅ You should now see the Agentforce icon in your top navigation bar! ##### Step 4: Activate the Agent - Scroll to the bottom, and you should see an agent named Agentforce (Default) in the agent list. - Click Open in Builder. - Click the Activate button. - Your agent is now ready to use. If you are unable to see the Agentforce Agent icon at the top after implementing the above configuration, follow the steps below: - Clear browser cache or perform a hard refresh (Ctrl + Shift + R). - Sometimes, cached data prevents new settings from appearing. ##### Use Case: Summarize and Manage Salesforce Opportunities with Agentforce Agentforce acts as your intelligent Salesforce assistant, allowing you to interact with your CRM data using simple natural language commands. For example, when viewing an Opportunity record, you can use the Agentforce chat panel to perform common actions without manual clicks or navigation. ##### Example Use Case: When a sales representative opens an opportunity record, they can chat with Agentforce to quickly get updates or make changes. ##### Sample interactions: ###### “Summarize this opportunity.” → Agentforce instantly provides a short summary of the key details like deal stage, amount, close date, and recent activities. ###### “Retrieve the activity timeline for this.” → Agentforce fetches all recent interactions, calls, emails, meetings, giving the rep a clear view of the engagement history. ###### “Update fields on this opportunity.” → Users can update opportunity fields directly from the chat, for example: “Update the stage to Proposal/Price Quote” or “Change the close date to next Friday.” ###### Why This Is Useful This feature saves time by eliminating the need to manually search or edit records. Sales reps can focus on conversations and deal progress while Agentforce handles CRM updates through AI-driven automation. #### 💡 Final Thoughts You can easily enable Agentforce in your Salesforce org and start using AI-powered assistance to boost productivity. Once active, you’ll notice a dedicated Agentforce icon in your navigation bar, ready to help with tasks, insights, and automation. If you’re still facing issues after completing all steps, verify permissions and org settings or consider reaching out to your Salesforce admin. #### Frequently Asked Questions **Why is the Agentforce icon not showing in my Salesforce org?** It is usually because a setup step is incomplete: Einstein is not turned on in Einstein Setup, or the Agentforce toggle and the Agentforce (Default) Agent toggle under Agentforce Agents are still off. If everything is enabled and the icon still does not appear, clear your browser cache or do a hard refresh (Ctrl + Shift + R), since cached data can prevent new settings from appearing. **Do I need to enable Einstein before Agentforce?** Yes. Agentforce runs on top of Einstein Generative AI, so you must turn on the "Turn on Einstein" toggle in Einstein Setup first, then refresh your browser before enabling Agentforce. **How do I activate the default Agentforce agent?** In Setup, open Agentforce Agents and scroll to the agent list at the bottom. Find the agent named Agentforce (Default), click Open in Builder, then click the Activate button. **What can Agentforce do on an Opportunity record?** From the chat panel you can ask it to summarize the opportunity (deal stage, amount, close date, recent activities), retrieve the activity timeline of calls, emails, and meetings, or update fields directly, for example changing the stage or the close date. --- **Ready to take Agentforce further?** Enabling it in your org is just step one. [Phenoble's Agentforce implementation team](/services/agentforce) builds fully customised agents, from SDR bots to service assistants, with the Apex actions, Data Cloud connections, and topic guardrails your business needs. [Book a free audit →](/contact) ### How to create agentforce sales coach URL: https://phenoble.com/blogs/how-to-create-agentforce-sales-coach Author: Kaushal Sharma | Published: Wed Oct 08 2025 00:00:00 GMT+0000 (Coordinated Universal Time) | Updated: Wed Aug 12 2026 00:00:00 GMT+0000 (Coordinated Universal Time) To create an Agentforce Sales Coach, you enable Agentforce for Sales in Salesforce Go, create a dedicated user record with the Einstein Agent license and the Agentforce Sales Coach permission set, then configure and activate the agent in Agentforce Builder. Once active, the coach gives sales reps deal-specific pitch practice, role-play scenarios, and personalized feedback directly on the Opportunity page. This guide covers each phase, plus how to test it. #### What is Agentforce Sales Coach? The Agentforce Sales Coach is an AI-driven solution designed to provide deal-specific, personalized feedback to sellers on their messaging and customer communication. It functions like a dedicated coach for every sales representative, guiding them through each opportunity and ultimately helping them close more deals. It is one of two agents included in Agentforce for Sales, alongside the SDR Agent. #### What Does the Sales Coach Do? 1. **Key Functionality and Value** The Agentforce Sales Coach helps managers and sales representatives alike by providing autonomous, scalable coaching that managers often cannot deliver due to time constraints. The Coach offers several core functionalities: - **Autonomous, On-Demand Coaching**: Sales representatives can receive guidance anytime, without needing a live coach. - **Pitch Practice**: Sellers can rehearse their pitch before meetings and receive tailored, actionable feedback based on the specific deal and its current stage. - **AI-Driven Role-Play Scenarios**: Representatives can practice tough conversations, such as negotiations, with a simulated "customer" or "buyer". - **Personalized Feedback**: Reps can improve their approach using insights specific to their deal and its current opportunity stage. - **Data Processing**: The Coach can process all the necessary data and maintains infinite knowledge for every opportunity, allowing managers to use it to scale their coaching efforts. The Coach operates as a "personal trainer in Salesforce" that helps reps build skills needed to close more deals and strengthen customer relationships. It adapts its guidance, introducing advanced techniques as the seller becomes more confident 2. **Components and Structure** The Agentforce Sales Coach is built using several features that allow it to provide coaching and generate feedback: - **Topics**: Allow administrators to group actions into functional jobs to be done, ensuring the agent uses only relevant actions for the task (e.g., coaching or role-play). - **Actions**: Specific sets of tasks an agent can complete within each topic. These can be customized using natural language instructions - **Instructions**: Describe what an action does and when the agent should use it in a conversation - **Prompt**: A natural language query that tells the Large Language Model (LLM) what the user wants to do. The actual feedback generated by the agent is driven by the prompt, which includes grounding data, evaluation criteria, and feedback format. - **Prompt Templates**: Reusable templates used to create personalized prompts by merging data specific to customers, products, and deals, leading to a unique, personalized response The Coach comes out of the box with prebuilt topics, actions, and prompt templates to facilitate quick deployment 3. **Prebuilt Topics** The Agentforce Sales Coach includes three prebuilt topics: - **Opportunity Coaching**: Allows the Sales Coach to provide feedback after a role-play or pitch practice scenario. This topic is related to actions that give feedback based on best practices for **five Opportunity stages**: Qualification, Needs Analysis, Discovery, Proposal/Pricing, and Negotiation/Review. - **Negotiation/Review Role-Play**: Allows the Sales Coach to simulate a customer in a role-play scenario, preconfigured with instructions informed by best practices for negotiation. - **Proposal Quote Role-Play**: Allows the Sales Coach to simulate a customer for practicing proposal and quote conversations. 4. **Technical Requirements** To operate, the Agentforce Sales Coach requires several underlying features and a dedicated user setup: - **Required Features**: The setup and customization require Agentforce, Einstein Generative AI (to power prompt templates), Agentforce Studio (to configure topics and actions), and Data Cloud (used to host files and support Retrieval-Augmented Generation, or RAG). - **User Setup**: The coach operates as an autonomous user in Salesforce. It requires a dedicated user record assigned the Einstein Agent User License and the Einstein Agent User Profile. This user must also have the Agentforce Sales Coach permission set assigned. - **Interface**: The coach is typically accessed through the Agentforce Sales Coach component added to the Opportunity page layout #### What Features Are Required to Set Up the Sales Coach? 1. **Agentforce**: This feature is used to configure and manage agents. 2. **Einstein Generative AI**: This feature is used to power your prompt templates and guide the Large Language Model (LLM) to generate feedback for the sales representative. 3. **Agentforce Studio**: This feature is used to configure topics and actions, power the agent, and equip it with the ability to role-play and generate feedback. 4. **Data Cloud**: This feature is used to host files and support retrieval-augmented generation (RAG). (It is noted that Data Cloud must be enabled for RAG functionality, such as connecting a Knowledge Library, to appear in the configuration process) #### How Do You Configure and Activate the Agentforce Sales Coach? The setup and creation of the Agentforce Sales Coach involves multiple phases, starting with enabling the feature in Salesforce Go, creating a dedicated user, and finally configuring and activating the agent in Agentforce Builder. Here are the detailed steps to create and activate the Agentforce Sales Coach: 1. **Phase 1**: Enable Agentforce Sales Coach and Grant Access This phase activates the core Agentforce features and ensures you have the necessary permissions to manage the coach. - **Access Salesforce Go**: Click the gear icon and click Salesforce Go to access the Salesforce Go home page in Setup. - **Enable Agentforce for Sales**: Scroll down to the **Get Started with Agentforce** section and click **Set Up** on the Agentforce for Sales card. - **Turn On Agentforce**: Click **Turn On** to enable Agentforce in your org, then click **Confirm**. This step makes sales-related agents, including the Sales Coach and SDR Agent, available for setup. - **Enable Sales Coach**: **Toggle on** Agentforce Sales Coach. Click **Confirm** in the dialog box. - **Grant Manager Access**: In the Agentforce Sales Coach setup area, click **Manage** next to **Manage User Access**. Under the Manage - Click on the **Agentforce Sales Coach** tab, select **your name** from the **All** Users list and click **Assign** to grant yourself the ability to manage/configure the agent. - Click on the **Use Agentforce Sales Coach** tab, select **your name** from the **All** Users list, click **Assign**, and then click **Done**. 2. **Phase 2**: Create a Sales Coach User Record and Configure Interface Since the Sales Coach operates as an autonomous user, a specific user record must be created, and the agent needs to be added to the relevant record page. 1. **Create New User**: In Setup, use Quick Find to search for and select **Users**. Click **New User** to create a user record specifically for the sales coaching agent. 2. **Assign License and Profile**: Populate the new user fields, ensuring you assign the following: - User License: **Einstein Agent** - Profile: **Einstein Agent User** 3. Click **Save**. 4. **Assign Permission Set**: Scroll down to the **Permission Set Assignments** section, click **Edit Assignments**, and move **Agentforce Sales Coach** from the Available Permission Sets section to the Enabled Permission Sets section, then click **Save**. 5. **Add Component to Opportunity Pages**: Add the Agentforce Sales Coach component to the Lightning Record Page for Opportunities (e.g., Opportunity Grouped View Default): - In **Setup** Quick Find, search for and select **Agentforce Sales Coach**. - In the **Add Components, Fields, and Actions to Lightning Record Page** section, click **Manage**. - Click Open in App Builder next to the desired Opportunity layout. - Drag the Agentforce Sales Coach component from the Components panel to the record page, typically just above the Related Lists section. - Click **Save**, **Activate**, and assign it as the Org Default. 3. **Phase 3**: Configure and Activate in Agentforce Builder Once the user is created and the component is placed, you define the agent's behavior and activate it using Agentforce Builder. 1. Navigate back to the **Agentforce Sales Coach** setup area in **Salesforce Go** and click **Go to Agentforce Builder** next to the **Build an Agent**. This opens a new tab with the agent type Agentforce Sales Coach already selected. 2. In the Select your agent’s topics step, ensure all available topics have been added and click **Next**. (The agent comes out of the box with prebuilt topics, actions, and prompt templates). 3. In the Customize your agent step, populate the fields for Name, Description, Role, and Company. 4. Select the **Sales Coach Agent** user in Agent User input box that record you created in Phase 2 from the Agent User list. 5. **Check** the box to Keep a record of conversations with Enhanced Event Logs to review agent behavior. 6. Click **Next** in the Select Language and Tone step, leaving defaults if desired. 7. In the Select data sources step, you can optionally connect data sources (like a Knowledge Library, which supports uploaded files) to support Retrieval-Augmented Generation (RAG). Note that Data Cloud must be enabled for this feature. 8. Click **Create**. 9. Once the agent is created, click **Activate**. This makes your Sales Coaching Agent active and ready to use. #### How to test it? 1. **User-Facing Testing Methods (Practice Scenarios)**: The coaching features are accessed via the Opportunities tab in the Sales app. This feature allows sellers to rehearse their pitch and receive tailored, actionable feedback based on the deal's current stage. - Steps for Pitch Practice: 1. Navigate to the **Sales** app and click the **Opportunities** tab. 2. Change the List View to **All Opportunities** and select a specific opportunity (e.g., **Edge Emergency Generator**). 3. Change the Opportunity Stage (e.g., click **Qualification** and select **Mark Stage as Current Stage**). 4. Locate **Agentforce Sales Coach**, which is typically on the right side above the Related lists, and click **Start** to launch the agent. 5. Select the **Practice Your Pitch** and Click on **Next**, click **Enable Microphone and Camera**. 6. Click **Start**, then **Start Recording**, and recite your pitch. The sales coaching agent can only interpret and provide feedback in English. 7. Click **End Practice** when finished. 8. If you meet the minimum content length requirements, a screen will appear allowing you to playback your recorded pitch. 9. Click **View Feedback** to see the agent's critique. Note that this feedback is not stored with the opportunity, so you must click **Copy Feedback** if you wish to save it. 10. You can repeat the practice pitch as often as needed by clicking **Try Again**. ; #### Frequently Asked Questions **What is required to set up the Agentforce Sales Coach?** Four features are required: Agentforce, Einstein Generative AI, Agentforce Studio, and Data Cloud (needed to host files and support retrieval-augmented generation). The coach also needs a dedicated user record with the Einstein Agent User license, the Einstein Agent User profile, and the Agentforce Sales Coach permission set. **What prebuilt topics does the Sales Coach include?** It ships with three prebuilt topics: Opportunity Coaching (feedback based on best practices for the Qualification, Needs Analysis, Discovery, Proposal/Pricing, and Negotiation/Review stages), Negotiation/Review Role-Play, and Proposal Quote Role-Play. **Where do sales reps access the Sales Coach?** Through the Agentforce Sales Coach component added to the Opportunity record page, typically above the Related Lists section. Reps open an opportunity, click Start to launch the agent, and choose a practice scenario such as Practice Your Pitch. **Does the Sales Coach save pitch feedback?** No. Feedback from a practice pitch is not stored with the opportunity, so reps must click Copy Feedback to save it. The coach can only interpret and provide feedback in English, and reps can retry the pitch as often as needed with Try Again. --- #### Related Articles - [Control Your Agent’s Behavior in Salesforce Using Context and Custom Variables](/blogs/control-your-agent-behavior-in-salesforce-using-context-and-custom-variables) - [Event Logs in Agentforce A Complete Guide](/blogs/event-logs-in-agentforce-a-complete-guide) - [Getting Started with Salesforce Agentforce: Enable, Create & Deploy Service Agen](/blogs/getting-started-with-salesforce-agentforce-enable-create-and-deploy-service-agents) Ready to implement? Learn more about our [Agentforce Implementation Services](/services/agentforce). ### Agentforce SDR Agent: How to Configure It for Sales Success URL: https://phenoble.com/blogs/understanding-and-configuring-your-agentforce-sdr-for-sales-success Author: Kaushal Sharma | Published: Wed Oct 08 2025 00:00:00 GMT+0000 (Coordinated Universal Time) | Updated: Wed Aug 12 2026 00:00:00 GMT+0000 (Coordinated Universal Time) The Agentforce SDR (Sales Development Representative) agent is an autonomous AI agent in Agentforce for Sales that nurtures leads 24/7 by sending personalized outreach, answering prospect questions, and booking meetings. Configuring it takes three phases: enable Agentforce and grant access, create a dedicated Einstein Agent user record with the required permission set, then set engagement rules and activate the agent in Agentforce Builder. This guide walks through each phase and shows how to test the agent with a sample lead. #### What is an SDR Agent? The SDR Agent, formally known as the Agentforce Sales Development Representative (SDR) agent, is a key component of Agentforce for Sales. It is an autonomous, proactive agent driven by AI that is designed to help sales teams. The primary function of the SDR agent is to nurture leads at scale 24/7. This is considered transformative for sales teams, allowing them to focus on building customer relationships and pipeline growth. #### What Does the SDR Agent Do? - **Outreach and Engagement:** SDR agents send personalized outreach, answer customers’ questions accurately, and can even book meetings on behalf of the sales team. - **Knowledge Base:** The agent uses organizational information (such as product descriptions, price sheets, or white papers) uploaded via the Upload Files section to accurately answer customer questions. - **Communication Templates:** The agent utilizes out-of-the-box prompt templates for various interactions: - **Draft Agentforce SDR Intro Email:** For initial outreach or first introduction emails to prospects. - **Follow-up on Agentforce SDR Email:** A "nudge email" sent if a prospect does not engage or reply. - **Reply with Product Q&A Agentforce Email:** Answers product questions using uploaded data and includes a meeting booking link. - **Reply with Meeting Agentforce SDR Email:** A reply email for meeting booking that includes a meeting link or lead owner contact information. - **Reply with Fallback Response Agentforce SDR Email:** A handoff email to the seller (lead owner) if the prospect reply is "not right now" or is an off-topic inquiry. - **Activity Visibility:** The agent uses Einstein Activity Capture (EAC) when generating outreach and reply emails, which ensures its emails are captured in Salesforce, giving direct visibility into all of its activities. #### Which user license is required? The user license required for the Agentforce SDR agent is the **Einstein Agent User** license. This license must be assigned to the user record created specifically for the SDR agent. The user license determines which profiles are available for the user. In addition to the Einstein Agent User license, the user record for the SDR agent must also be assigned the Einstein Agent User profile, which specifies the user’s minimum permissions and access settings. Furthermore, the agent needs the Agentforce SDR agent permission set assigned to its user record to perform its work. #### How Do You Configure and Test the SDR Agent? 1. **Phase 1:** Enable Supporting Features and Grant Access This phase lays the groundwork by turning on Agentforce and granting initial user permissions. 1. **Enable Agentforce and SDR Agent**: - Click the gear icon and click **Salesforce Go** (or use Quick Find to select Salesforce Go if already in Setup). - Scroll to the **Get Started with Agentforce** section and click Set Up on the **Agentforce for Sales** card. - Click **Turn On Agentforce** to enable Agentforce in your org, then click Confirm. This step automatically makes sales-related agents, including the Sales Coach and SDR Agent, available for setup. - Toggle on **SDR Agent | Inbound Nurturing**. - Click Confirm in the dialog box to activate the agent. 2. **Grant User Access for Configuration and Use**: - In the SDR Agent | Inbound Nurturing setup area within Salesforce Go, click **Manage** next to **Manage User Access**. - In the **Configure Agentforce SDR Agent** tab, select **All** Users from the Recently Viewed dropdown. - Check the box next to **YOUR NAME** and click **Assign** to grant yourself the ability to configure the agent. - Click the **Use Agentforce SDR Agent** tab. - Select **All** Users, check the box next to **YOUR NAME**, and click **Assign** to grant yourself the ability to use the agent. - Click **Done**. 2. **Phase 2**: Create an SDR Agent User Record Because the agent acts like a user in your organization, a specific user record must be created for it, along with necessary permissions and email configuration. 1. **Create the User Record**: - From **Setup**, use the Quick Find box to search for and click **Users**. - Click **New User** to create a new user record specifically for the SDR agent. - Populate the new user fields according to your company’s preferences. - Crucially, assign the required license and profile: - User License: **Einstein Agent**. - Profile: **Einstein Agent User**. - Click **Save**. 2. **Assign Permissions to the SDR Agent User**: - In the Quick Find box, type and click **Permission Sets**. - Find and click **Agentforce SDR agent** from the list. - Click **Manage Assignments**. - Click **Add Assignments**. - Check the box next to **SDR Agent** (do not assign this to yourself), click **Next**, click **Assign**, and click **Done**. 3. **Add the SDR Agent to Einstein Activity Capture (EAC)**: - In the Quick Find box, type **Einstein Activity Capture**. - Click **Settings** under the Einstein Activity Capture heading. - Click **Add Contact and Event Sync**. - Select your Email and Calendar services, then click Next. - Select the user connection preference, then click Next. - Enter a name and optional description for the new EAC configuration, then click Next. - Verify the Sync Settings (email sync is required for Agentforce SDR) and click Next. - Verify Advanced Settings. - On the EAC Add Users and Profile screen, move the SDR Agent user you created from the Available to Selected list, and click Next. - Click Finish. 4. **Connect Sales User Email Accounts (for Sellers)**: - To allow sellers to view, edit, reschedule, or cancel SDR agent emails from the Activity Timeline of leads, each seller must connect their email account in their Salesforce user profile. - From the seller’s Personal **Settings**, they navigate to **Email and Calendar Accounts** under the Connected Accounts, click **New Account**, and follow the steps to connect their account. 3. **Phase 3**: Configure and Activate the Agent in Agentforce Builder Once the user is created and features are enabled, you use Agentforce Builder to define the agent’s operational rules. 1. **Access Agentforce Builder**: - Click the gear icon and click **Salesforce Go**. - Click **Keep Going** in the Agentforce for Sales box. - Click the **SDR Agent | Inbound Nurturing** title to expand the view. - In the **Build an Agent** section, click **Go to Agentforce Builder**. 2. **Review Topics**: - Ensure the agent type selected is **Agentforce Sales Development Rep**. - Review the available topics (Send Outreach, Respond to Prospect, and Manage Opt-Out) and click **Next**. 3. **Define Settings**: - Fill in detailed information for the Description, Role, and Company fields to help ground the prompts. - For Agent User, **Select the Agentforce SDR user** record you created in Phase 2. - Optionally, **Check the box** to Keep a record of conversations with enhanced event logs to review agent behavior for later auditing. - Click **Next**. 4. **Configure Language, Tone, and Files**: - You can skip the Select Language and Tone section for now, as it can be customized later. Click **Next**. - In the Upload Files section, click Upload Files to add organizational information (like product descriptions or white papers) that the agent will use to answer customer questions accurately. (**Note**: I have not upload files in this blog) - Click **Next**. 5. **Set Engagement Rules and Activate**: - Engagement Rules determine when and how the agent interacts with leads. These rules automate outreach by adding conditions for assigning leads to the agent. - Select an option for Assign Lead to Agent When, defining the Field, Operator, and Value (e.g., Lead Rating equals Cool). - Select the Email Account. - Click Connect an Account to connect the email address used for the SDR agent’s user record. This address must match the one on the user record. - Set the Maximum attempts, Time between attempts, and Maximum number of replies. - Select your Outreach Schedule (hours and days the agent performs outreach). - Click **Create**. - Click **Activate**. 4. **Next Steps:** Testing and Customization 1. **Step 1**: Add the Activate Agentforce SDR Action to Lead Page Layouts You must add the Activate Agentforce SDR action to your Lead page layouts so that you can manually activate the agent on Lead records. 1. From the home page, click the gear icon (⚙︎) and select **Setup**. 2. Navigate to the **Object Manager** tab. 3. In the Quick Find box, search for and select **Lead**. 4. Select **Page Layouts** from the left-hand menu bar. 5. Select **Lead Layout** from the list of Lead Page Layout options. 6. Click **Mobile & Lightning Actions**. 7. Select the **Activate Agentforce SDR** action and drag it to the Salesforce Mobile and Lightning Experience Actions section. 8. Click **Save**. - Once this action is added, you will see Activate **Agentforce SDR** in the Actions menu on the Lead record page. 2. **Step 2**: Create a Test Lead Record Next, you need to create a new lead record to test the agent interactions. 1. From the home page, click the App Launcher (the nine dots). 2. Search for and select Sales. 3. Click the Leads tab. 4. Click New to create a new Lead. 5. Enter your test lead information, such as the first and last name, Company, Lead Source, and Industry fields. These fields are used by the agent to personalize its outreach. 6. Set the lead email address to one you can access for testing, as you will need to monitor and respond to emails from the SDR agent. - Note: The lead email address cannot be in the same domain (means if you had select the gmail service you can not send to message gmail to gmail.) as the agent’s email. #### Output You will get mail like this: Try to reply this above mail "It is possible to get a trial of Sales Cloud?" Then you will get: Click on **Book a Meeting** button. You will redirect on this page: #### Frequently Asked Questions **Which license does the Agentforce SDR agent require?** The SDR agent requires a dedicated user record with the Einstein Agent User license and the Einstein Agent User profile. The Agentforce SDR agent permission set must also be assigned to that user record for the agent to perform its work. **How are the SDR agent's emails tracked in Salesforce?** The agent uses Einstein Activity Capture (EAC) when generating outreach and reply emails, so all of its emails are captured in Salesforce. Sellers who connect their own email accounts can view, edit, reschedule, or cancel SDR agent emails from the Activity Timeline of leads. **What topics come with the SDR agent out of the box?** The Agentforce Sales Development Rep agent type ships with three topics: Send Outreach, Respond to Prospect, and Manage Opt-Out. It also includes prebuilt prompt templates for intro emails, follow-up nudges, product Q&A replies, meeting booking replies, and fallback handoffs to the lead owner. **Can a test lead use the same email domain as the agent?** No. The lead email address cannot be in the same domain as the agent's email, so if the agent uses a Gmail account, the test lead cannot also use a Gmail address. Set the lead email to an address you can access so you can monitor and respond to the agent's emails. --- **Looking for an Agentforce SDR implementation partner?** Phenoble has deployed Agentforce SDR agents for B2B sales teams, including custom lead qualification logic, CRM field mapping, and email sequence tuning. [See how we implement Agentforce for sales →](/services/agentforce) --- #### Related Articles - [Control Your Agent’s Behavior in Salesforce Using Context and Custom Variables](/blogs/control-your-agent-behavior-in-salesforce-using-context-and-custom-variables) - [Event Logs in Agentforce A Complete Guide](/blogs/event-logs-in-agentforce-a-complete-guide) - [Getting Started with Salesforce Agentforce: Enable, Create & Deploy Service Agen](/blogs/getting-started-with-salesforce-agentforce-enable-create-and-deploy-service-agents) Ready to implement? Learn more about our [Agentforce Implementation Services](/services/agentforce). ### Unifying Customer Data with Salesforce Data Cloud- Stream, Resolve, Enrich & Segment URL: https://phenoble.com/blogs/unifying-customer-data-with-salesforce-data-cloud-stream-resolve-enrich-segment Author: Keshav Sharma | Published: Tue Aug 05 2025 00:00:00 GMT+0000 (Coordinated Universal Time) | Updated: Wed Aug 12 2026 00:00:00 GMT+0000 (Coordinated Universal Time) #### What is Salesforce Data Cloud? Salesforce Data Cloud unifies customer data in four steps: stream data in with a Data Stream, merge duplicate records into unified profiles with an Identity Resolution ruleset, enrich those profiles with Calculated Insights, and group them into Segments you can activate. Data Cloud itself is a platform that unifies data from multiple sources to give you a 360-degree view of your customers, whether you're in retail, finance, healthcare, or any data-driven industry. This guide walks through each of those steps hands-on. #### How Do You Create a Data Stream in Data Cloud? - In salesforce org, Click on App Launcher and Search for Data - Select Data cloud from the list - Click on Data streams tab then New button - Choose Salesforce CRM from the screen - Click on Next button - Choose Sales under Standard Bundles - Click on Next - Leave values as is, Click on Next - Data Space automatically populate with default - Click on Deploy - Wait until the deployment is complete. - After deployment complete, You will see these records in Data stream tab ##### Create a Formula Field - From the Data Stream tab, locate and click the Lead_Home data stream that you created. - click the New Formula Field button - For Field Label, name your field **Is US Based** - For Formula Return Type, select Text - Enter this formula in the Transformation Formula field: `IF(sourceField['Country'] == "USA" || sourceField['Country'] == "United States", "TRUE" , "FALSE")` - Validate the formula - Type `India` into the country field and then click Test - Output should = FALSE - Type `USA` and then click Test - Output should = TRUE - Click on Save button You are successfully created Data Stream in Data Cloud. #### How Do You Create an Identity Resolution Ruleset? Unifying customer data through Identity Resolution is a crucial step in transforming scattered data points into meaningful insights. By setting up rulesets in Salesforce Data Cloud, you control how unification happens, ensuring that the most accurate and relevant information makes it into each customer’s unified profile. - Search for and select **Data Cloud** in the App Launcher - Select the **Identity Resolutions** tab and click New - Select **Create New Ruleset** and click Next. - Choose Individual from the Primary Data Model Object dropdown. Individual is also preselected in the next field - Leave the Ruleset Id blank and click Next - In the RuleSet type `Individual Match` - Run jobs Automatically should be Enabled - Also Link records should be Enabled - Click Save ##### Configure - Open the Identity Resolution record - Click on Configure button under Ruleset Properties - Click Next - Click on Configure button to select your first match rule. - Select the Fuzzy Name and Normalized Email and click Next - Keep the default settings as is, and click Next - To add more rules, click Add Match Rule - Repeat the steps to add these other two rules 1. Fuzzy Name and Normalized Phone 2. Fuzzy Name and Normalized Address - Click Save ##### Reconciliation Rule - Click the Warnings tab on the right side of the page to address the warning about the reconciliation rule for Individual.Individual Id. - Click Individual.Individual Id to modify the Reconciliation Rules - Select the checkbox next to Individual ID and then click Update Selected - Disable the Default Reconciliation Rule and then set the Field Reconciliation Rule to Source Priority - Use the up arrows to ensure that the Contact_Home object is first in priority, followed by the Lead_Home object - Click Save #### How Do You Create Calculated Insights? Once you’ve connected, mapped, and unified your data in Salesforce Data Cloud, the next step is to turn that data into actionable intelligence. This is where Insights come in. By querying your unified data, you can generate powerful metrics and analytics that align with your business goals. - Go to the Calculated Insights tab and click New - select Create with Visual Builder and click Next - Select **Create a Calculated Insight** and click Next - Search for and then select **Unified Individual** as your first object in the insight - Click Next ##### Add a Join - In the Visual Insights Builder, click the + next to Unified Individual and select Join - Select **Case** and then click Next - Notice that this automatically adds and joins multiple objects to create a proper join from Unified Individual to Case. - Click **Apply (1)** to verify your selection. ##### Add an Aggregate - Click the + on the last Join and select **Aggregate** - For Measures, click + (1). From the **Count** section, select **Case Id (2)** - Tip: Use the search field to locate Case Id easily - Click Next (3) - For Metric Name enter `Count Case ID`. Notice Metric API Name automatically populates with `Count_Case_ID` - Click **Apply** ##### Add Dimensions - For Dimensions, click + (under the Measures +) and add Unified Individual Id from the source, Unified Individual. - Click Next - For Dimension Name enter `Unified Individual` - Click **Apply** - Follow these steps to add Case Status named **Case Status** as a dimension - Click Apply for the Aggregate selections ##### Save Your Work - Select Save and Run - Name your calculated insight `Unified Individual Case Counts` and click Next - Leave the schedule to the default, `Not Scheduled`, and click `Enable` - On the Calculated Insights tab, click `Publish Now` from the dropdown menu If you don’t see Publish Now, refresh your browser and try again. #### How Do You Create a Segment in Data Cloud? Before diving in, it’s important to understand why Segmentation and Activation are so valuable. When you have access to a large amount of customer data, the challenge is figuring out how to focus on the right group. This project walks you through creating a segment filter in Data Cloud, helping you identify, target, and connect with the customers that matter most, quickly and effectively. - From your Developer org, search for Data Cloud in the App Launcher - From Data Cloud, go to the **Segments** tab and click **New** - Leave **Use a Visual Builder** and **Standard Segment** selected and click **Next** - The default Data Space should be auto-selected. Then from the Segment On dropdown, select **Unified Individual**. - Next, name your segment **No Zip Code**. Add an optional description to describe your segment - Click Next - Select **Standard Publish** - From the Publish Schedule dropdown, select **Don’t refresh** and click **Save** ##### Add Filters The goal of this segment is to narrow down the list of US Based leads who haven’t provided their zip code. Follow these steps to add filters to obtain this result. - With the Attributes pane selected, expand Related Attributes - Search for `Is US Based` under Lead - Select the first option and then drag the Is US Based attribute to the canvas - Within the Lead container - From the Measurement dropdown, select Count - From the Operator dropdown, select At Least - For Value, type `1` - For the Is US Based attribute: - From the Operator dropdown, select `Is Equal To` - For Value, type `true` (and select from available options) - Click Done - Next, search for `Postal Code` under the Related Attribute **Lead** and then drag the **Postal Code** attribute to the canvas - For the Postal Code attribute: - From the Measurement dropdown, select Count - From the Operator dropdown, select At Least - For Value, type `1` - From the next Operator dropdown, select **Has No Value** - Click **Done** - Click **Save** - When the number is refreshed, click **Done** #### How Do You Activate a Segment? Once you’ve built a segment in Data Cloud, the next step is to put it to work, that’s where Activation comes in. Activation is the process of sending your segment to the platforms where you’ll actually use it, like marketing tools or advertising channels. To make this happen, you connect your segment to an activation target. Think of it as the bridge that securely stores the authentication and authorization details for each platform. These targets can include Marketing Cloud, Data Cloud, B2C Commerce, Amazon Ads, Google Audience Insights, and many more. #### Create a New Activation Target - Navigate Activation Targets tab. - Click **New** - Select **Data Cloud** and click **Next** - Name your Activation Target `Data Cloud Segments`. Add an optional description - Select **default** for your Data Space - Click **Save** ##### Activate Your Segment - Navigate to the Activations tab - Click **New** - For Segment, select the newly created **No Zip Code** segment - Select **Data Cloud Segments** as your Activation Target - For Activation Membership, select **Unified Individual** - Click Continue - Next to Email, click **+ Select** and then **Next** - Click Add Attributes - From Direct Attributes under Unified Individual, drag **Last Name** under the Unified Individual section on the right, next to the existing Unified Individual Id. - Click **Save** - Review the summary and then click **Next** - Name the activation **No Zip Code** - Confirm the Incremental Refresh is selected and then click **Save** #### Conclusion: By creating Data Streams, Identity Resolution rules, Calculated Insights, and Segments in Data Cloud, you have successfully established a complete data foundation, from ingesting and unifying data to deriving insights and targeting specific audiences. This end-to-end setup enables smarter decision-making, personalized engagement, and more effective business strategies. #### Frequently Asked Questions **What order should you follow to unify customer data in Data Cloud?** Start by creating a Data Stream to ingest data (for example, the Salesforce CRM Sales bundle), then set up an Identity Resolution ruleset to merge records into unified profiles. From there, build Calculated Insights to derive metrics, create a Segment to target the right group, and finally activate the segment to an activation target. **How does Identity Resolution match records into a unified profile?** You configure match rules on the Individual object, such as Fuzzy Name with Normalized Email, Normalized Phone, or Normalized Address. Reconciliation rules then decide which value wins when sources conflict, for example using Source Priority to rank the Contact_Home object above Lead_Home. **What is a formula field in a Data Stream?** A formula field transforms data as it is ingested. In this guide, an Is US Based field returns TRUE when the source Country field is USA or United States, and that field is later used as a segment filter. **What is segment activation in Data Cloud?** Activation sends your segment to the platforms where you will actually use it, like marketing tools or advertising channels. You connect the segment to an activation target, which stores the authentication details for destinations such as Marketing Cloud, B2C Commerce, Amazon Ads, or Google Audience Insights. --- #### Related Articles - [How to Integrate Avoma with Salesforce](/blogs/how-to-integrate-avoma-with-salesforce) - [How to integrate salesforce with teamup](/blogs/how-to-integrate-salesforce-with-teamup) - [How to Integrate Slack with Salesforce Agentforce](/blogs/how-to-integrate-slack-with-salesforce-agentforce) Ready to implement? Learn more about our [Salesforce Data Cloud & Integration](/services/data-cloud). ### Getting Started with Salesforce Agentforce: Enable, Create & Deploy Service Agents URL: https://phenoble.com/blogs/getting-started-with-salesforce-agentforce-enable-create-and-deploy-service-agents Author: Keshav Sharma | Published: Fri Aug 01 2025 00:00:00 GMT+0000 (Coordinated Universal Time) | Updated: Wed Aug 12 2026 00:00:00 GMT+0000 (Coordinated Universal Time) Salesforce Agentforce brings the power of generative AI to your customer service experience by allowing you to build intelligent AI-powered agents. These agents can handle customer conversations, automate common tasks, and escalate to human agents when needed. In this guide, we'll walk you through the complete setup process, from enabling Agentforce in your Salesforce org to deploying your Service Agent on a public-facing community site. > **Need expert help with your Agentforce implementation?** Phenoble's certified Agentforce specialists have deployed 40+ agents across sales and service teams. [See our Agentforce services →](/services/agentforce) #### 1. How to Enable Agentforce in Your Org Before you can build or deploy any AI agents, you need to enable Agentforce in your Salesforce org. ##### Steps to Enable Agentforce: - Go to Setup in Salesforce. - In the Setup Quick Find, search for and select Einstein Setup. - Click the Turn on Einstein toggle, and make sure Einstein is On - Refresh your browser to reload Setup. - In the Setup Quick Find, search for and select Agentforce Agents. - At the top of the Agentforce Agents page, click the Agentforce toggle, and ensure it is set to On. - Click the Enable the Agentforce (Default) Agent toggle, and ensure it is set to On. #### 2. How to Create a Service Agent - Create Invocable Apex class ```java:OrderStatus.cls public class OrderStatus { @InvocableMethod(label='Order Status' description='Return status of the order based on order number') public static List getStatus(List orderNumbers) { List results = new List(); if (orderNumbers == null || orderNumbers.isEmpty()) { results.add('Error: Order number list is empty or null.'); return results; } try { String orderNumStr = orderNumbers[0]; Order o = [SELECT Id, Status FROM Order WHERE OrderNumber = :orderNumStr LIMIT 1]; results.add(o.Status); } catch (QueryException qe) { results.add('No order found for number ' + orderNumbers[0]); } catch (Exception e) { results.add('Error: ' + e.getMessage()); } return results; } } ``` ##### Create Action - Now In the Quick Find, search for and select Agentforce Assets. - Click on Agentforce Assets - Click on **+ New Agent Action** button - Choose Reference Action Type as **Apex** - Choose Reference Action Category as **Invocable Methods** - Choose Reference Action as Order Status - Click on Next button - In the Agent Action Instruction Write "Return status of the order based on order number. For example: user provide input like this: share me the status of order number 00000100 so it should return the order status." - Loading Text as "Getting Order Details" - In the Input Section Instructions field write "Order number provided by user" and Select checkbox Require input - In the Output Section Instructions field write "show the status of the order" and Select checkbox show in conversation - Click on Finish button ##### Create Sample Data - Click on App Launcher and Search for **Contract** - Select **Contracts** - Create a Record of Contracts - Now Click on App Launcher and Search for **Order** - Select **Orders** - Create a Record of Orders - Make sure order should be linked to the contracts record like this ##### Setup Agent - In the Setup Quick Find, search for and select Agentforce Agents. - Click + New Agent. Note: If the New Agent button is not present, refresh the page until the button appears. - Select Agentforce Service Agent as the type. - Click Next. - On the Select your agent's topics screen, click Added next to Case Management to remove this standard topic from your agent. The button should now be +Add. - Click Added next to every topic - Click Next. - Enter the agent’s Name and API Name as follows: **Name**: Get Order Status **Description**: Deliver personalized customer interactions with an autonomous AI agent. Get Order Status Agent intelligently supports your customers with common inquiries about the order status. **Role**: An AI customer service agent whose job is to help customers with queries regarding order status. **Company**: This is a company which delivers customer orders - Click on Next Button - Click on Create button ##### Grant Permission to Agent User - Create Permission Set named **Get_Order_Status_Permissions** - In the Permission Set Go to **Object Setting** - Find Order object and Give **Read** and **View All Field** Permission - In permission set Now Go to Apex class Access and Click on Edit - Select OrderStatus apex class from Available Apex Classes to Enabled Apex Classes - Click on Save - In Agentforce builder screen Click on Setting Icon! - Scroll down and Copy starting text of Agent User field like this - Search this in **users** list and click on user - Click on **Permission Set Assignments** link from top - Click on Edit Assignments - Find **Get_Order_Status_Permissions** permission set and move it to Enabled Permission Sets - Click on Save button ##### Create a New Topic in Agentforce - Go to your Agentforce Agent - Click on New button and then New Topic - In the **What do you want this topic to do(Optional)** fill as "This topic will call the order status invocable action and share the order status with the customer." - Click on Next button - **Topic Label:** Order Status - **Classification Description:** This topic handles inquiries related to checking the status of an order. It will guide the agent to retrieve and share the order status with the customer. - **Scope:** Your job is only to retrieve and provide the current status of the customer’s order. Do not attempt to handle any other types of inquiries or issues. - **Instructions:** If a user does not have their order number, ask for the order number in correct format - Click on Next button - Choose Order Status action - Click on Finish ##### Omni-channel Settings - In the Quick Find box Search for "Omni-channel Settings" and Select - Turn on Enhanced Omni-Channel Routing toggle button - Make sure Enable Omni-Channel Checkbox is check - Scroll down to bottom and Select Automatically log agents in to Omni-Channel in the new window or tab ##### Create Routing Configuration - In the Quick Find box Search for **Routing** - Click on **Routing Configurations** - Click on **New** Button - Fill the form as following - Click on **Save** button ##### Create a new Queue - In the Quick Find box Search for **Queue** - Click on **Queues** and Click on **New** button - Fill the Label and Queue Name as **Messaging Queue** - In the **Routing Configuration** choose routing configuration which we created in Step 2 - From **Available Objects** choose **Messaging Session** and add it to **Selected Objects** section - Now from **Available Members** choose your admin user and add it to **Selected Members** - Click on **Save** button ##### Create the Omni-Channel Flow - Creating Omni-channel Flow for Inbound - In the Quick Find box Search for **flows** - Click on **New Flow** button - Click on Omni-channel flow - Click on Toggle Toolbox - Create a Text variable like this - Now Click on Add Element and Search for Route - Select Route Work - Fill the values like below - Save the flow and Activate it. ##### Creating Message Channel - In the Quick Find box Search for **Messaging Setting** - Click on **Messaging Settings** - Click on **New Channel** button - Click on Start button - Click on **Messaging for In-App and Web** - Fill the form as following and Click on Next - Now fill the form as following - Choose Flow and Queue of yours - Click on Save button ##### Enable Digital Experience and Embedded Service Deployments - In the Quick Find box Search for "Digital Experience" - Click on **Settings** - Now select the **Enable Digital Experience** checkbox - In the Quick Find box Search for "Embedded" - Select **Embedded Service Deployments** - Click on **New Deployment** button - Select Messaging for in-App and Web - Click on Next button - Click on Web - Click on Next button - **Embedded Service Deployment Name:** Order Status ESD - **API Name:** Auto Populate - **Domain:** my.site.com - **Messaging Channel:** Choose the Messaging Channel which we created ealier - Click on Save button - Now Click on the Publish button ##### Creating and Adding Agent on Site - Go to the All Site - Click on New button - Choose Customer Service Template - Click on Get Started button - Give it a Name and URL and Click on Create button - Select the Administration section - Click on Settings - Click on Activate button - Now go to the builder - Click on Components button - Search for Embedded Messaging - Drag & Drop Embedded Messaging to the Page anywhere - Now Click on Publish and again click on publish button - Click on Got it button - In the Quick Find box search for **Embed** - Select **Embedded Service Deployments** - Open the record which we created earlier - Under the Settings click on Edit Settings - Search for **Show Typing Indicators** and Enable this - In the Quick Find box search for **CORS** - Under Allowed Origin List click on New button - **Origin URL pattern:** https://\*.my.site.com - Click on Save button - Now Go to the All site and Open newly created Community Site - You will see the bot Icon, click on that - Now Test your agent ##### Congratulations you have successfully created and deployed your AI Agent to the Community Site! --- #### Frequently Asked Questions **What do you need to enable before creating an Agentforce agent?** Einstein must be turned on first in Einstein Setup, since Agentforce depends on it. After a browser refresh, open Agentforce Agents in Setup and switch on both the Agentforce toggle and the Enable the Agentforce (Default) Agent toggle. **How does the Service Agent look up an order status?** Through an invocable Apex action. The OrderStatus Apex class queries the Order object by order number, and an Agent Action created in Agentforce Assets references that invocable method. A dedicated Order Status topic on the agent then calls the action when a customer asks about an order. **Why does the agent user need a permission set?** The agent runs as its own user, so it needs explicit access to the data and code it uses. The Get_Order_Status_Permissions permission set grants Read and View All Field access on the Order object plus access to the OrderStatus Apex class, and it must be assigned to the agent user shown in the agent's settings. **How do you deploy the agent to a public-facing site?** Enable Digital Experience, create an Embedded Service Deployment using a Messaging for In-App and Web channel backed by your Omni-Channel flow and queue, then drag the Embedded Messaging component onto a community site built from the Customer Service template. Add a CORS allowed origin for your site domain and publish. --- #### Related Articles - [Control Your Agent’s Behavior in Salesforce Using Context and Custom Variables](/blogs/control-your-agent-behavior-in-salesforce-using-context-and-custom-variables) - [Event Logs in Agentforce A Complete Guide](/blogs/event-logs-in-agentforce-a-complete-guide) - [How to create agentforce sales coach](/blogs/how-to-create-agentforce-sales-coach) Ready to implement? Learn more about our [Agentforce Implementation Services](/services/agentforce). ### What is Salesforce Data Cloud URL: https://phenoble.com/blogs/what-is-salesforce-data-cloud Author: Keshav Sharma | Published: Wed Jul 23 2025 00:00:00 GMT+0000 (Coordinated Universal Time) | Updated: Wed Aug 12 2026 00:00:00 GMT+0000 (Coordinated Universal Time) #### What is Salesforce Data Cloud? Salesforce Data Cloud is a real-time data platform that allows you to unify, harmonize, and activate customer data from various sources (Salesforce and non-Salesforce) to build a single source of truth for each customer (called a Unified Profile). #### Data Cloud App in Salesforce When you open the Data Cloud app (via App Launcher in Salesforce), you’ll see several key tabs. Here’s a breakdown: #### What is a Data Stream in Data Cloud? A Data Stream is a connection pipeline that pulls data from an external source into Data Cloud on a scheduled or real-time basis. ###### Common Data Stream Sources | Source Type | Example | | --------------------------- | --------------------------------- | | **Salesforce CRM** | Accounts, Contacts, Opportunities | | **Marketing Cloud** | Journeys, Email Opens, Clicks | | **Amazon S3 / GCP / Azure** | CSV files, logs, transaction data | | **Snowflake** | Federated tables | | **MuleSoft / APIs** | Custom app data | ###### Key features | 🔑 Feature | 📝 Description | | -------------------------- | ----------------------------------------------------------------------------- | | **Create New Stream** | Easily connect to data sources like Salesforce, S3, Snowflake, or CSV files. | | **Real-Time & Scheduled** | Choose how often data is pulled, real-time, hourly, daily, etc. | | **Preview Data** | See sample records before finalizing the connection. | | **Field Selection** | Select specific fields you want to ingest from the source. | | **Automatic DLO Creation** | Data lands in a Data Lake Object (DLO) automatically. | | **Secure Access** | Enforces data access rules and governance policies. | | **Stream Monitoring** | View status, last run time, and errors from each data stream. | | **No-Code Setup** | Configure everything using a guided, user-friendly UI, no development needed. | #### What are Data Lake Objects (DLOs)? Data Lake Objects (DLOs) are like containers or tables that hold raw data as it comes into Salesforce Data Cloud. When you bring data into Data Cloud from external systems (like a CSV file, an e-commerce platform, or a third-party database), that raw data is stored in a Data Lake Object first. ###### Key Characteristics of DLOs | Feature | Description | | -------------------- | ---------------------------------------------------------------------------------------------------- | | **Raw Data Storage** | DLOs store the original, unprocessed data exactly as it was received from the source. | | **Schema-Driven** | Each DLO has a defined structure (fields and data types) based on what’s coming from the source. | | **Read-Only** | You **cannot change** data directly in DLOs, they are meant for storage, not editing. | | **Mapped Later** | You map DLOs to **Data Model Objects (DMOs)**, which are standardized, cleaned versions of the data. | #### What are Data Model Objects (DMOs)? Data Model Objects (DMOs) are standardized, structured representations of your business data inside Salesforce Data Cloud. They are based on Salesforce’s Customer 360 Data Model, which includes predefined objects like Individual (person), Contact Point, Order, Product, etc. ###### Key Features of DMOs | Feature | Description | | ----------------------- | ------------------------------------------------------------------------------------------------- | | **Standardized Schema** | DMOs follow a consistent data model so all your data fits together, no matter where it came from. | | **Mapped from DLOs** | You map raw data in DLOs to DMOs for harmonization and further use. | | **Part of C360 Model** | DMOs are part of Salesforce’s **Customer 360 Data Model** designed for customer-centric data. | | **Can Be Extended** | You can create **custom DMOs** or extend standard ones by adding custom fields. | #### Data Explorer Data Explorer is like a search and preview tool inside Data Cloud. It lets you: - Look at customer profiles. - See how data from different sources has been combined. - View calculated insights and linked objects (like purchases, emails, etc.). - Test your data before using it in segments or campaigns. | **Feature** | **Description** | | ----------------------------------- | --------------------------------------------------------------------------------------- | | **Unified Profile Viewer** | View the full 360° profile of a customer (combined from multiple sources). | | **Search Tool** | Search for any record using email, phone, name, etc. | | **Data Model Object (DMO) Browser** | See how data is organized into customer, order, email, etc. | | **Linked Data Viewer** | See all related objects (e.g., customer → orders → products). | | **Calculated Insights Preview** | View KPIs like total spend, purchase count, or loyalty score. | | **Record Preview Table** | Browse customer records in a spreadsheet-style layout. | | **Test Conditions or Filters** | Try out filter conditions (e.g., customers with 3+ purchases) before creating segments. | #### Einstein Studio Einstein Studio is a feature inside Salesforce that allows you to create and use AI/ML models with your Data Cloud data. For example: - Predict which customers are likely to churn. - Score leads based on past purchase behavior. - Recommend products based on browsing or order history. | Feature | What It Does | | ------------------------------ | --------------------------------------------------------------------- | | **Model Builder** | Create and configure ML models using your customer data | | **External Model Integration** | Connect to AI services like **SageMaker** or **Vertex AI** | | **Zero-ETL Integration** | Use data from Data Cloud directly, no need to move it between systems | | **Train and Test Models** | Train your models and test how accurate they are | | **Deploy Models** | Publish the model so its predictions can be used in Salesforce | | **Use in Segments or Flows** | Use prediction scores to personalize customer journeys | ##### Semantic Layer The Semantic Layer is like a translator between your raw data and your business users. It helps turn complex data structures into simple, meaningful terms that everyone can understand, like "Customer", "Order", or "Total Spend". | Component | Description | | ---------------------- | -------------------------------------------------------------------------- | | **Labeling** | Renaming technical fields to human-readable labels | | **Descriptions** | Adding help text so users know what each field means | | **Data Types & Units** | Defining how each field should be formatted (number, currency, text, etc.) | | **Relationships** | Linking objects (like Customer → Orders → Products) | | **Access Control** | Showing only relevant fields to different users (e.g. Marketing vs. IT) | #### What is Identity Resolution? Identity Resolution is the process of identifying and combining duplicate or related records from different systems into one unified customer profile. Example: It helps you recognize that "John berry", "J. berry", and "john.berry@test.com" are the same person, even if their data comes from different sources. | Feature | What It Does | | ----------------------------- | --------------------------------------------------------------------- | | **Matching Rules** | Define how to find similar records (e.g., same email or phone number) | | **Resolution Rules** | Decide how to merge fields (e.g., take most recent phone number) | | **Unified Individual Object** | The final result, one single customer profile (golden record) | | **Rule Sets** | Groups of rules you create and run on your data | | **Manual Review (optional)** | You can preview matched results before finalizing | #### Profile Explorer Profile Explorer is a tool inside Data Cloud that lets you: View the full, unified customer profile, all data about a person in one place. ###### It shows everything you know about a customer: - Contact details - Orders - Products viewed - Support cases - Calculated insights (like total spend) - Segments they belong to | **Feature** | **What It Shows** | | -------------------------- | ----------------------------------------------------------------------------- | | **Unified Profile** | All merged information about a customer from different systems | | **Linked Data** | Connections to orders, products, addresses, activities, etc. | | **Calculated Insights** | Metrics like total revenue, visit count, average spend | | **Segment Membership** | Lists of segments (like VIP Customers, Active Users) this customer belongs to | | **Data Model Object View** | Details from mapped DMOs like Individual, Email, Address, etc. | #### What are Calculated Insights? Calculated Insights are custom KPIs or metrics that you create based on customer data. **Exp:** Calculated Insights help you answer questions like, "How many orders has a customer placed?" or "What is the total amount they’ve spent?" | Feature | Description | | ------------------- | -------------------------------------------------------------- | | **No-code builder** | Create insights using point-and-click, no SQL needed | | **Use DMOs** | Works on structured data like `Individual`, `Order`, `Product` | | **Filters** | Apply conditions (e.g., orders from last 90 days) | | **Grouping** | Calculate per customer, per region, or per product | | **Reusable** | Use in segments, profile explorer, and activations | #### Data Action Target Data Action Targets Send Data Cloud segments or insights out to other systems, like: - Marketing Cloud - Facebook Ads - Google Ads - Email platforms - External APIs - Salesforce orgs (like Sales or Service Cloud) | Feature | Description | | -------------------------- | ---------------------------------------------------------------------- | | **Real-time or scheduled** | Send data continuously or at specific intervals | | **Multiple channels** | Integrate with ad networks, CRMs, CDPs, or custom systems | | **Custom or Prebuilt** | Use Salesforce connectors or create custom targets via API or MuleSoft | | **Data governance** | Uses permissions to ensure secure and controlled data sharing | #### Data Actions Data Actions let you send audience segments or insights from Data Cloud to external destinations like: - Marketing Cloud - Ad Platforms (Facebook, Google, etc.) - Salesforce CRM (Sales/Service Cloud) - Custom APIs - Data Lakes / Warehouses (Snowflake, S3) | Feature | Description | | ------------------ | ---------------------------------------------------------------------- | | **Choose Targets** | Pick a pre-configured Data Action Target (e.g. Marketing Cloud) | | **Map Fields** | Choose which fields (e.g. email, phone, name) you want to send | | **Set Schedule** | Choose to run one-time or on a recurring schedule (e.g. daily at 9 AM) | | **Preview Output** | See sample records before activation to ensure accuracy | | **Track Runs** | View status and logs of past executions (success/failure) | #### What is a Segment in Data Cloud? In Salesforce Data Cloud, a Segment is a group of people (or profiles) who match certain rules or conditions. | Feature | Description | | ----------------------- | --------------------------------------------------------------------- | | **Segment Builder** | A visual, no-code tool to define your segment rules | | **Unified Profiles** | Works on real-time, unified customer data (after identity resolution) | | **Drag-and-drop rules** | Easily add filters like "City = Mumbai", "Orders > 3", etc. | | **Realtime updates** | Segments automatically refresh as data changes | | **Preview & Activate** | See who qualifies _before_ pushing the segment live | | **Used in Activation** | You can send segment data to other systems via Data Actions | #### What is Activation in Data Cloud? Activation is the process of sending data (like segments or calculated insights) from Salesforce Data Cloud to external systems such as: - Marketing Cloud - Google / Facebook Ads - Salesforce Sales or Service Cloud - External APIs or Data Warehouses | Feature | Description | | ------------------ | ---------------------------------------------------------------------- | | **Select Segment** | Choose which audience you want to activate | | **Pick Target** | Choose where to send the data (e.g., Marketing Cloud, Ads, Salesforce) | | **Field Mapping** | Match fields from Data Cloud to target fields (e.g., email, name) | | **Schedule Runs** | Decide when and how often to send (once or recurring) | | **Monitor Runs** | See logs of each activation, success, failures, record counts | #### What is a Data Space? In Salesforce Data Cloud, a Data Space is like a separate folder or workspace to keep your data organized and isolated. | Feature | Description | | --------------------------- | ------------------------------------------------------------------------------- | | **Logical Separation** | Keeps data and operations isolated across business areas | | **User Access Control** | You can assign users to specific data spaces only | | **Scoped Segments** | Segments and calculated insights are **only valid within their own data space** | | **Security and Governance** | Ensures data isn’t accidentally shared between spaces | | **Reusable Across Org** | One org can have **multiple data spaces** | #### Search Index A Search Index in Data Cloud allows you to search customer profiles quickly using keywords, just like you use Google to search the web. | Feature | Description | | ------------------------ | -------------------------------------------------------------------------- | | **Profile Search** | Enables keyword-based searching of profiles (email, phone, name, etc.) | | **Fast Results** | Searches millions of records in seconds | | **Flexible Matching** | You can search using full or partial values (e.g., part of email or phone) | | **Scoped by Data Space** | You can only search profiles in your current **Data Space** | | **View Profile Details** | Search results show detailed Unified Profile view | #### Data Shares Data Shares allow you to share your unified data (like customer profiles, insights, or segments) with other Salesforce orgs, external systems, or third-party partners, securely and in real-time. | Feature | Description | | ------------------------ | ----------------------------------------------------------------- | | **Secure Sharing** | Share data securely with permissions and access controls | | **Selective Fields** | Choose what fields and objects to share, no over-sharing | | **Real-Time or Batch** | Share in real-time (event-based) or as scheduled data packages | | **Destination Options** | Share to other Salesforce clouds, Snowflake, AWS, or partner orgs | | **Supports Segments** | You can share a whole **Segment** or just part of it | | **Scoped by Data Space** | Sharing is limited to the selected **Data Space** | #### What is a Data Graph? A Data Graph is a visual map of related customer data across multiple objects (tables), like a family tree of customer information. A Data Graph shows how different pieces of customer data are connected, like linking a person to their orders, devices, visits, preferences, and more. | Feature | Description | | -------------------------- | ---------------------------------------------------------------------- | | **Joins Multiple Objects** | Links different Data Model Objects (DMOs) together | | **Visual Mapping** | Shows how your data tables relate (Customer → Order → Product) | | **Power for Insights** | Required for Calculated Insights and Segment building | | **AI-Ready** | Einstein & Prompt Builder use the Data Graph for smart recommendations | | **Semantically Linked** | It’s not just SQL joins, it understands the meaning of relationships | #### Data Share Targets A Data Share Target is the destination where your shared data from Data Cloud will go. A Data Share Target is "where" you want to send data, like Marketing Cloud, Snowflake, or another Salesforce org. | Feature | Description | | ------------------------- | ---------------------------------------------------------------------- | | **Connects Destinations** | Sets up the destination system for the shared data | | **Secure Integration** | Uses secure auth to link to Salesforce, Snowflake, AWS, etc. | | **Reusable** | You can create once and use across multiple Data Shares | | **Batch or Real-Time** | Supports both scheduled and event-based (real-time) sharing | | **Data Mapping** | Lets you map fields between Data Cloud and the destination system | | **Smart Routing** | Can be tied with segment refresh or calculated insights for automation | #### Query Editor Query Editor is a tool inside Data Cloud that allows you to write and run SQL-like queries to explore and analyze your data. **Sample SQL Queries** ``` SELECT * FROM Individual WHERE Country = 'India' ``` | Feature | Description | | ----------------------- | ------------------------------------------------------------------- | | **SQL-Based Interface** | Write queries using a simple SQL-like syntax (Snowflake SQL flavor) | | **Joins Support** | Combine multiple Data Model Objects in one query | | **Preview Results** | Instantly see what your query returns | | **Save Queries** | Save frequently-used queries for reuse | | **Debugging Tool** | Great for testing data before building Segments or Insights | | **Explore Raw Data** | View raw records from unified or ingested sources | #### Communication Capping Communication Capping is a feature in Data Cloud that lets you control how often a customer receives marketing messages, like emails, SMS, or push notifications, across channels. It helps ensure that customers don’t get overwhelmed or spammed with too many messages. | Feature | Description | | -------------------------- | ---------------------------------------------------------------------- | | **Set Message Limits** | Limit the number of emails, texts, or pushes per day/week/month | | **Define Time Windows** | Set rules like “max 1 SMS per day” or “max 3 emails per week” | | **Cross-Channel Control** | Capping applies across **email, SMS, push, in-app**, etc. | | **Segment-Based Rules** | Apply different caps to different segments (VIP vs. Regular customers) | | **Works with Activations** | Prevents activation journeys from triggering too many messages | | **Overage Detection** | Warns or blocks activations that break the cap rules | #### Data Transforms Data Transforms let you clean, reshape, and prepare your ingested data before using it in segments, insights, or activations. Data Transforms are like recipes you create to fix or modify your raw data, so it becomes usable and accurate for marketing, analytics, and personalization. | Feature | Description | | ------------------------------ | -------------------------------------------------------------------------------------------- | | **Input Source** | Use any ingested dataset (batch or streaming) | | **Transform Rules** | Apply logic like merging, formatting, trimming, filtering | | **No-Code Interface** | Visual builder lets you configure transforms without writing code | | **Preview Output** | See the result of transformations before saving | | **Save and Reuse** | Saved transforms can be used in activations, segments, and more | | **Integrates with Data Model** | You can map the final output to standard Data Model Objects like `Individual`, `Order`, etc. | #### Reports The Reports tab gives you a visual and interactive summary of your data usage, processing status, segmentation activity, and insights generation. It helps you understand how well your Data Cloud setup is working. Reports show you what’s happening inside Data Cloud, like how many profiles were matched, how many records were ingested, and if your identity resolution is working. | Feature | Description | | ------------------------------- | ----------------------------------------------------------------- | | **Data Ingestion Overview** | See how much data has been ingested over time | | **Identity Resolution Summary** | Shows how many identities were matched or stitched | | **Profile Stats** | Tracks number of unified profiles created, merged, or in error | | **Segment Execution** | Tells you how many segments ran successfully vs. failed | | **Activation Performance** | Shows where data was activated (Email, Ads, Mobile) and how often | | **Historical Trends** | Allows comparisons over time, like week over week change | | **Downloadable Reports** | You can export reports for stakeholders in CSV or other formats | #### Conclusion In this blog, we explored all the major tabs and components available in Salesforce Data Cloud, including Data Streams, Identity Resolution, Profile Explorer, Segments, Calculated Insights, and more. Each feature plays a unique role in helping you bring together data from different sources, unify it, and use it effectively for activation and personalization. Salesforce Data Cloud is a powerful tool that connects data, AI, and customer insights, and learning it step-by-step will set you up for success in modern data-driven CRM strategies. #### Frequently Asked Questions **What is the difference between a Data Lake Object and a Data Model Object?** A Data Lake Object (DLO) stores the original, unprocessed data exactly as it was received from the source, and it is read-only. A Data Model Object (DMO) is the standardized, cleaned version of that data, mapped from DLOs and based on Salesforce's Customer 360 Data Model. **How does Identity Resolution create a unified customer profile?** Identity Resolution uses matching rules (for example, same email or phone number) to find related records across systems, then resolution rules to decide how fields merge, such as taking the most recent phone number. The result is a single Unified Individual record, often called the golden record. **Can Salesforce Data Cloud connect to non-Salesforce data sources?** Yes. Data Streams can pull data from sources such as Amazon S3, Google Cloud, Azure, Snowflake, Marketing Cloud, and custom apps via MuleSoft or APIs, on a scheduled or real-time basis. **Do you need to write code to use Salesforce Data Cloud?** Most features are no-code: Data Streams use a guided setup UI, Calculated Insights have a point-and-click builder, and Segments use a drag-and-drop visual builder. The Query Editor is available if you want to explore data with SQL-like queries. ### How to Use AgentForce in Salesforce URL: https://phenoble.com/blogs/how-to-use-agentforce-in-salesforce Author: Keshav Sharma | Published: Tue Apr 15 2025 00:00:00 GMT+0000 (Coordinated Universal Time) | Updated: Wed Aug 12 2026 00:00:00 GMT+0000 (Coordinated Universal Time) To use AgentForce in Salesforce, you enable Einstein and AgentForce in Setup, build a flow that retrieves the data your agent needs, then create an agent with topics and actions in Agent Builder and test it in the Conversation Preview. AgentForce is Salesforce's AI-driven feature for automating customer support and service interactions, built on Einstein AI. This guide walks through each step in order. ##### Step 1: Creating an AgentForce Org To work with AgentForce, you need a specific Salesforce org. Follow these steps to create one: 1\. Visit this [Trailhead link](https://trailhead.salesforce.com/content/learn/projects/quick-start-build-your-first-agent-with-agentforce/configure-an-agentforce-service-agent) and sign in. 2\. Click on Launch to create and open the Salesforce org. 3\. Once your org is ready, proceed to the next steps. ##### Step 2: Enabling AgentForce Before configuring AgentForce, you must enable it in your Salesforce org: 1\. Click the Setup icon and select Setup. 2\. In the Quick Find box, search for Einstein Setup and select it. 3\. Click the Turn on Einstein toggle and ensure Einstein is enabled. 4\. Refresh your browser. 5\. In the **Quick Find box**, search for **Agents** and select it. 6\. On the **Agents** page, enable **AgentForce** by toggling it on. ##### Step 3: Creating a Flow to Get and Pass Data to the Agent Flows help automate processes for AgentForce. To create a flow: 1\. Navigate to **Setup > Flow**. 2\. Click **New Flow**. 3\. Select **Autolaunched Flow** and click **Create**. 4\. Create input text type variable. 5\. Drag a **Get Records** element to retrieve data from the **Case** object. 6\. Drag an Assignment element to store data in a collection variable. 7\. Connect the elements and click Save. 8\. Click **Activate**. ##### Step 4: Creating an Agent, Topics, and Actions To configure an AgentForce AI-powered agent: ###### 1\. Create an Agent: Go to **Setup > Agents**. Click **+ New Agent**. Select **Agentforce Service Agent** as the type. Then click on **Next**. Remove all the added topics. Then click on **Next**. Fill in all the details. Then click on **Next**. Then click on **Create**. ###### 2\. Create Topics: From the Agent Builder, click New and select New Topic. Enter the name. Then click on **Next**. Fill in all the details. Leave it all, then click on **Next**. Click **Finish**. ###### 3\. Create Actions for the Topic: Click on the **topic** that you created. Click the **This Topic’s Actions** tab. Click New and select **Create New Action**. Select **Flow** as the Reference Action Type. For Reference Action, select **your flow name**. Leave the other options as is, and click **Next**. Fill in all the details. Click **Finish**. ###### 4\. Click **Activate**. ###### 5\. Test the Agent: While still in the Agent Builder, click **Refresh** (circular arrow) in the top right corner of the **Conversation Preview**. Go ahead and enter this prompt: **Provide details about all high-priority cases**. Press your **Enter** key. ##### Conclusion AgentForce in Salesforce enables AI-powered automation for better customer service. By setting up an org, enabling AgentForce, creating a test object, building a flow, and configuring an AI agent, you can optimize service interactions efficiently. Try out these steps and start leveraging AgentForce in your Salesforce environment! #### Frequently Asked Questions **Do I need a special Salesforce org to work with AgentForce?** Yes. The walkthrough uses a dedicated org created through the Trailhead quick start project: sign in on the Trailhead project page, click Launch, and Salesforce provisions the org for you. **What has to be enabled before configuring AgentForce?** Two things in Setup: turn on the Einstein toggle in Einstein Setup (then refresh your browser), and toggle AgentForce on from the Agents page. **How do flows connect to an AgentForce agent?** You build an autolaunched flow with an input text variable, a Get Records element that retrieves data from the Case object, and an Assignment element that stores the results in a collection variable. That flow is then wired to a topic as an action with Flow as the Reference Action Type. **How do I test the agent after activating it?** In Agent Builder, click the Refresh icon in the Conversation Preview, then enter a prompt such as "Provide details about all high-priority cases" and press Enter. --- #### Related Articles - [Control Your Agent’s Behavior in Salesforce Using Context and Custom Variables](/blogs/control-your-agent-behavior-in-salesforce-using-context-and-custom-variables) - [Event Logs in Agentforce A Complete Guide](/blogs/event-logs-in-agentforce-a-complete-guide) - [Getting Started with Salesforce Agentforce: Enable, Create & Deploy Service Agen](/blogs/getting-started-with-salesforce-agentforce-enable-create-and-deploy-service-agents) Ready to implement? Learn more about our [Agentforce Implementation Services](/services/agentforce). ## Other blog posts - [Building an Agent with Agentforce Script in Salesforce](https://phenoble.com/blogs/building-a-agent-with-agentforce-script-salesforce): Agent Script is a language used to build agents in Agentforce Builder. - [Einstein Conversation Insights: The Complete Guide for Salesforce Teams](https://phenoble.com/blogs/einstein-conversation-insights-complete-guide): Einstein Conversation Insights (ECI) is Salesforce's AI call analytics tool. Setup, configuration, use cases, and how to get real ROI from it in 2026. - [Apollo.io Sequences: Complete Guide to Automating Cold Outreach.](https://phenoble.com/blogs/Apollo.io-Sequence): Complete guide to Apollo.io Sequences: build multi-step cold outreach with automated emails, call tasks, and LinkedIn touchpoints for consistent SDR output. - [Automating Sales with Apollo.io Workflows](https://phenoble.com/blogs/Automating-Sales-with-Apollo.io-Workflows): How to use Apollo.io Workflows to automate lead nurturing, trigger outreach sequences, and enrich Salesforce records, cutting manual SDR work. - [How to Integrate Apollo.io with Salesforce (Step-by-Step Guide)](https://phenoble.com/blogs/How-to-Integrate-Apollo.io-with-Salesforce): Step-by-step guide to integrating Apollo.io with Salesforce, sync contacts, leads, and activity data to power your pipeline with enriched prospect data. - [RingCentral Integration with Salesforce](https://phenoble.com/blogs/RingCentral-Integration-with-Salesforce): Connect RingCentral to Salesforce so calls, SMS, and voicemail log against the right record. Setup steps, CTI configuration, and common pitfalls. - [Clerk Salesforce Integration with Webhooks and API Calls](https://phenoble.com/blogs/clerk-salesforce-integration-with-webhooks-and-api-calls): When building customer and team-centric applications, keeping your identity platform and CRM - [How to Run your MCP Servers from the Command Line Interface to Call Multiple Tools](https://phenoble.com/blogs/how-to-run-your-mcp-servers-from-the-command-line-interface-to-call-multiple-tools): This walkthrough shows how to **run your MCP servers** from the command line - [Step by Step Guide: Connecting Postman to Salesforce via OAuth 2.0](https://phenoble.com/blogs/step-by-step-guide-connecting-postman-to-salesforce-via-oauth): If you work with Salesforce APIs, you know that **testing endpoints** can sometimes be - [How to add a Global Callable Class which Implements Callable and Register it as a Tool in MCP Server](https://phenoble.com/blogs/how-to-add-a-global-callable-class-which-implements-callable-and-register-it-as-a-tool-in-mcp-server): A global callable class” in Apex is a class marked global that implements - [Build a UI which shows Agentforce Prompt Box and execute the command locally](https://phenoble.com/blogs/build-a-ui-which-shows-agentforce-prompt-box-and-executes-the-command-locally): This blog provides a small web UI that can call MCP tools from multiple servers - [Creating an Apex Rest API and using it as a custom tool in Custom MCP Server](https://phenoble.com/blogs/creating-an-apex-rest-api-and-using-it-as-a-custom-tool-in-custom-mcp-server): This solution uses Apex REST for object describe and jsforce in your MCP - [How to install the Custom MCP Server Part - 2](https://phenoble.com/blogs/how-to-installing-the-custom-mcp-server): In this blog, we’ll show you how to install and configure a custom MCP server - [How to install the Standard MCP Server Part - 1](https://phenoble.com/blogs/how-to-installing-the-standard-mcp-server): Part 1 of our MCP series: how to install the standard MCP server for Salesforce and confirm it is running before adding custom tools. - [How to Use the Testing Center in Salesforce to Test AI Agents](https://phenoble.com/blogs/how-to-use-the-testing-center-in-salesforce-to-test-ai-agents): A quick overview of using Salesforce’s Agentforce Testing Center to validate, batch-test, and build trust in custom AI agents before production deployment. - [How to Setup Email Verification for Customer Service Agent in Salesforce](https://phenoble.com/blogs/how-to-setup-email-verification-for-customer-service-agent-in-salesforce): A concise guide on enabling secure email-based customer verification for Salesforce Customer Service Agents using Agentforce standard authentication actions. - [Salesforce Account Intelligence View Prioritize and Act on Your Accounts Efficiently](https://phenoble.com/blogs/salesforce-account-intelligence-view-setup): Salesforce’s Account Intelligence View is a powerful enhancement designed to give sales - [Salesforce Contact Intelligence View See, Act, and Engage Faster](https://phenoble.com/blogs/salesforce-contact-intelligence-view-setup): Salesforce has elevated contact management with the Contact Intelligence View, a powerful feature - [Salesforce Lead Intelligence View: Focus Your Sales Efforts Smarter](https://phenoble.com/blogs/salesforce-lead-intelligence-view-setup): Salesforce has introduced the Lead Intelligence View to help sales teams efficiently identify - [Salesforce Pipeline Inspection: Real-Time Visibility for Smarter Sales Management](https://phenoble.com/blogs/salesforce-pipeline-inspection-setup): Salesforce Pipeline Inspection is a powerful sales management feature designed to give sales teams - [How to create and deploy unlocked package using second generation package](https://phenoble.com/blogs/how-to-create-and-deploy-unlocked-package-using-second-generation-package): What an Unlocked Package is, when to use one, and how to create and deploy it with second-generation packaging for trackable org changes. - [Ensuring Code Quality and Security Compliance with Salesforce Code Analyzer](https://phenoble.com/blogs/ensuring-code-quality-and-security-compliance-with-salesforce-code-analyzer): Salesforce Code Analyzer is a command-line tool (built on Node.js) that helps analyze - [Financial Service Cloud-28 Interest Tags - Browse Modal and Tag Category Hierarchy-Visualization & Filtering](https://phenoble.com/blogs/financial-service-cloud-28-interest-tags-browse-modal-and-tag-category-hierarchy-visualization-and-filtering): How to use the Interest Tags Browse Modal and Tag Category Hierarchy in Financial Services Cloud to search, assign, and filter client interests. - [Financial Service Cloud-27 Work With Interest Tags](https://phenoble.com/blogs/financial-service-cloud-27-work-with-interest-tags): In this blog, you will learn how to effectively work with Interest Tags - [Financial Service Cloud-26 Add the Interest Tags Component to Record Pages](https://phenoble.com/blogs/financial-service-cloud-26-add-interest-tags-component-to-record-pages): How to add the Interest Tags component to record pages in Financial Services Cloud so advisors manage client interests inside the profile. - [Financial Service Cloud-25 Configure Interest Tags](https://phenoble.com/blogs/financial-service-cloud-25-configure-interest-tags): How to configure and manage Interest Tags in Financial Services Cloud so client engagement is structured, personalized, and searchable. - [Financial Service Cloud-24 Interest Tags Set-up](https://phenoble.com/blogs/financial-service-cloud-24-interest-tags-set-up): How to set up Interest Tags in Financial Services Cloud to capture client interests, needs, and prospecting opportunities on the record. - [Financial Service Cloud-23 Expire Obsolete Life Events or Business Milestones and Associate an Event with an Opportunity](https://phenoble.com/blogs/financial-service-cloud-23-expire-obsolete-events-or-milestones-and-associate-an-event-with-an-opportunity): How to expire obsolete Life Events or Business Milestones in Financial Services Cloud and associate an event with an Opportunity. - [Financial Service Cloud-22 Configure Contextual Actions for Events and Milestones](https://phenoble.com/blogs/financial-service-cloud-22-configure-contextual-actions-for-events-and-milestones): How to configure Contextual Actions for Events and Milestones in Financial Services Cloud so advisors act directly from a client life event. - [Financial Service Cloud-21 Personalize Events & Milestones with Custom Icons and Configure Compact Layouts](https://phenoble.com/blogs/financial-service-cloud-21-personalize-events-and-milestones-with-custom-icons-and-configure-compact-layouts): How to personalize Events and Milestones in Financial Services Cloud with custom icons and compact layouts for clearer event details. - [Financial Service Cloud-20 Configure Business Milestones and Hide Sensitive Life Event Types](https://phenoble.com/blogs/financial-service-cloud-20-configure-business-milestones-and-hide-sensitive-life-event-types): How to configure Business Milestones and hide sensitive Life Event types in Financial Services Cloud's Events and Milestones component. - [Financial Service Cloud-19 Add the Events & Milestones component to the page layout](https://phenoble.com/blogs/financial-service-cloud-19-add-the-events-and-milestones-component-to-the-page-layout): How to add the Events and Milestones component to a Financial Services Cloud page layout so client events show directly on Person Accounts. - [Financial Service Cloud-18 Events and Milestones](https://phenoble.com/blogs/financial-service-cloud-18-events-and-milestones): How Events and Milestones in Financial Services Cloud help advisors track life events and build more personalized client relationships. - [Financial Service Cloud-17 Add new graph to Rachel Adams Person Account](https://phenoble.com/blogs/financial-service-cloud-17-add-new-graph-to-rachel-adams-person-account): How to add a new ARC Relationship Graph to a Person Account in Financial Services Cloud, using the Rachel Adams sample record as the walkthrough. - [Financial Service Cloud-16 Create and View Custom ARC Relationship Graphs](https://phenoble.com/blogs/financial-service-cloud-16-create-and-view-custom-arc-relationship-graphs): How to create and view custom ARC Relationship Graphs in Financial Services Cloud using Graph Designer to map client and household connections. - [How to create and deploy package using second generation managed packages](https://phenoble.com/blogs/how-to-create-and-deploy-package-using-second-generation-managed-packages): What a Second-Generation Managed Package (2GP) is, how its lifecycle works, and how to create and deploy one for AppExchange distribution. - [Financial Service Cloud-15 Configure Quick Actions in ARC](https://phenoble.com/blogs/financial-service-cloud-15-configure-quick-actions-in-arc): How to configure quick actions in Financial Services Cloud's Actionable Relationship Center (ARC) so advisors complete routine tasks in place. - [Financial Service Cloud-14 Customize Record Card Fields and Side Panel](https://phenoble.com/blogs/financial-service-cloud-14-customize-record-card-fields-and-side-panel): How to customize record card fields and the side panel in Financial Services Cloud's Actionable Relationship Center (ARC) to surface key client data. - [Financial Service Cloud-13 Add ARC to Account Page Layout](https://phenoble.com/blogs/financial-service-cloud-13-add-arc-to-our-account-page-layout): In Salesforce Financial Services Cloud, the Actionable Relationship Center (ARC) - [Financial Service Cloud-12 Actionable Relationship Center](https://phenoble.com/blogs/financial-service-cloud-12-actionable-relationship-center): In this blog, you will learn how the Actionable Relationship Center (ARC) - [Financial Service Cloud-11 Customize Group Types and Roles](https://phenoble.com/blogs/financial-service-cloud-11-customize-group-types-and-roles): In Salesforce Financial Services Cloud (FSC), every client’s financial world - [Financial Service Cloud-10 Understanding Group Membership](https://phenoble.com/blogs/financial-service-cloud-10-understanding-group-membership): In today’s financial services industry, understanding not just an individual - [Financial Service Cloud-9 Build a Contact-Contact Relationship with a Reciprocal Role](https://phenoble.com/blogs/financial-service-cloud-9-build-a-contact-to-contact-relationship-with-a-reciprocal-role): How to build a contact-to-contact relationship with a reciprocal role in Financial Services Cloud for lawyers, accountants, and other advisors. - [Financial Service Cloud-8 Managing Visibility - Controlling Access on Relationship Maps and Group Builder](https://phenoble.com/blogs/financial-service-cloud-8-managing-visibility-controlling-access-on-relationship-maps-and-group-builder): How Relationship Map and Group Builder visibility controls in Financial Services Cloud keep advisors and bankers seeing only the data they need. - [Financial Service Cloud-7 How to Enable or Disable Multiple Relationship Groups](https://phenoble.com/blogs/financial-service-cloud-7-how-to-enable-or-disable-multiple-relationship-groups): Step-by-step guide to enabling or disabling Multiple Relationship Groups in Financial Services Cloud and what it changes for household records. - [Financial Service Cloud-6 Record Rollup Definitions Explained](https://phenoble.com/blogs/financial-service-cloud-6-record-rollup-definitions-explained): How Record Rollup Definitions in Financial Services Cloud aggregate financial data across household and group hierarchies for a complete AUM view. - [Financial Service Cloud-5 Roll-Up Summaries and Account Ownership & Roll-Ups Simplified](https://phenoble.com/blogs/financial-service-cloud-5-roll-up-summaries-and-account-ownership-and-roll-ups-simplified): Managing client financial data effectively is at the heart of Financial Services Cloud - [Financial Services Cloud 4 Managing Households & Configuring Group Builder](https://phenoble.com/blogs/financial-services-cloud-4-managing-households-and-configuring-group-builder): Relationship groups let you group related accounts together so you can manage them easier. Accounts added to a Relationship - [Financial Service Cloud-3 Understanding Person Account and Relationship Management](https://phenoble.com/blogs/financial-service-cloud-3-understanding-person-account-and-relationship-management): Person Accounts and relationship management in Financial Services Cloud: how clients, households, and groups are modeled and connected. - [Financial Service Cloud-1 Introduction](https://phenoble.com/blogs/financial-service-cloud-1-introduction): In today's fast-paced financial industry, managing customer relationships. - [Financial Service Cloud-2 Org Review & User Setup, Profiles, Permission Set Licenses, Permission Sets](https://phenoble.com/blogs/financial-service-cloud-2-org-review-and-user-setup-profiles-permission-set-licenses-permission-sets): Setting up Salesforce Financial Services Cloud (FSC) correctly is essential. - [Salesforce Health Cloud-1 Introduction](https://phenoble.com/blogs/salesforce-health-cloud-1-introduction): Health Cloud is a tool made by Salesforce that helps hospitals, doctors. - [Salesforce Health Cloud-10 Healthcare Data with Relationship Cards](https://phenoble.com/blogs/salesforce-health-cloud-10-healthcare-data-with-relationship-cards): A relationship card in Salesforce Health Cloud is a tool that shows important related information. - [Salesforce Health Cloud-11 Benefit Verification Concept](https://phenoble.com/blogs/salesforce-health-cloud-11-benefit-verification-concept): A practical guide to Benefit Verification in Salesforce Health Cloud: how payers and providers automate eligibility checks and cut claim denials. - [Salesforce Health Cloud-12 Utilization Management](https://phenoble.com/blogs/salesforce-health-cloud-12-utilization-management): In this blog, you will learn how Utilization Management in Salesforce Health Cloud streamlines. - [Salesforce Health Cloud-13 Configure Patient Lists](https://phenoble.com/blogs/salesforce-health-cloud-13-configure-patient-lists): In this blog, you will learn how to create smarter, more informative patient lists in Salesforce Health Cloud. - [Salesforce Health Cloud-14 Advanced Therapy Management](https://phenoble.com/blogs/salesforce-health-cloud-14-advanced-therapy-management): In this blog, you will learn how Advanced Therapy Management in Salesforce Health. - [Salesforce Health Cloud-2 Permissions Explained](https://phenoble.com/blogs/salesforce-health-cloud-2-permissions-explained): In this blog, you’ll learn everything about permissions in Salesforce Health Cloud, what they are. - [Salesforce Health Cloud-3 Care Team Setup](https://phenoble.com/blogs/salesforce-health-cloud-3-care-team-setup): In this blog, you’ll learn what the Care Team feature in Salesforce Health Cloud. - [Salesforce Health Cloud-4 Understanding Care Coordination](https://phenoble.com/blogs/salesforce-health-cloud-4-understanding-care-coordination): In this blog, you’ll learn what care coordination really means, why it’s crucial for delivering better. - [Salesforce Health Cloud-5 Care Plans, Goals & Tasks](https://phenoble.com/blogs/salesforce-health-cloud-5-care-plans-goals-and-tasks): In this blog, you’ll learn what Care Plans, Goals, and Tasks are in Salesforce Health Cloud. - [Salesforce Health Cloud-6 Provider Management](https://phenoble.com/blogs/salesforce-health-cloud-6-provider-management): In this blog, you’ll learn what a payer is in Salesforce Health Cloud, why they play a critical. - [Salesforce Health Cloud for Payers: Managing Insurance & Care Plans](https://phenoble.com/blogs/salesforce-health-cloud-7-payers-for-manage-insurance-and-care): How Salesforce Health Cloud helps insurance payers manage member data, care plans, provider networks, and compliance. A practical guide for healthcare IT teams. - [Salesforce Health Cloud-8 Data Model Explained](https://phenoble.com/blogs/salesforce-health-cloud-8-data-model-explained): When working with Salesforce Health Cloud, understanding the data model is the foundation for building any healthcare. - [Salesforce Health Cloud-9 Care Model & Provider Model](https://phenoble.com/blogs/salesforce-health-cloud-9-care-model-and-provider-model): Salesforce Health Cloud's Care Model and Provider Model explained: how they structure care plans, provider relationships, and clinical workflows. - [Understanding and Creating Cadences in Salesforce](https://phenoble.com/blogs/understanding-and-creating-cadences-in-salesforce): In Salesforce, a cadence is a planned, scheduled sequence of sales activities designed to automate and streamline outreach efforts. - [Unlocking Sales Potential with Einstein Conversation Insights in Salesforce](https://phenoble.com/blogs/unlocking-sales-potential-with-einstein-conversation-insights-in-salesforce): Einstein Conversation Insights (ECI) is a Salesforce feature that uses AI to analyze recorded sales conversations. - [Control Your Agent’s Behavior in Salesforce Using Context and Custom Variables](https://phenoble.com/blogs/control-your-agent-behavior-in-salesforce-using-context-and-custom-variables): Agentforce gives you the flexibility to design intelligent chat assistants that respond differently based on your users' inputs and business logic. - [Troubleshooting API Failures with Log Frames](https://phenoble.com/blogs/troubleshooting-api-failures-with-log-frames): In the world of Salesforce development, making API calls is a routine task. These calls allow you to interact with external systems,. - [Understanding Sales Velocity How to Measure and Accelerate Your Revenue Growth](https://phenoble.com/blogs/understanding-sales-velocity-how-to-aeasure-and-accelerate-your-revenue-growth): Sales velocity measures how quickly sales opportunities move through your pipeline and result in revenue. - [Slack and Salesforce Integration for Sharing Dashboards](https://phenoble.com/blogs/slack-and-salesforce-integration-for-sharing-dashboards): Integrating Slack and Salesforce for sharing dashboards is a powerful way to enhance team collaboration - [How to invoke Prompt Template from Apex and Lightning web components](https://phenoble.com/blogs/how-to-invoke-prompt-template-from-apex-and-lightning-web-components): In this blog you will use flex template to generate social media posts. - [Invoking Agentforce Agents from Apex Unlocking AI Automation in Salesforce](https://phenoble.com/blogs/invoking-agentforce-agents-from-apex-unlocking-ai-automation-in-salesforce): Salesforce Agentforce empowers users to bring conversational intelligence and task automation directly into. - [How to Integrate Slack with Salesforce Agentforce](https://phenoble.com/blogs/how-to-integrate-slack-with-salesforce-agentforce): Salesforce Agentforce empowers support teams to engage with customers directly across messaging channels. - [How to Integrate Avoma with Salesforce](https://phenoble.com/blogs/how-to-integrate-avoma-with-salesforce): Avoma is a powerful AI meeting assistant that automatically records, transcribes, and summarizes your meetings. - [How to Native Integration Amplemarket with Salesforce](https://phenoble.com/blogs/how-to-native-integration-amplemarket-with-salesforce): Integrating Amplemarket with Salesforce enables sales teams to streamline their prospecting and outreach . - [Event Logs in Agentforce A Complete Guide](https://phenoble.com/blogs/event-logs-in-agentforce-a-complete-guide): Agentforce, Salesforce’s AI-powered assistant, is built to deliver seamless user experiences by interacting dynamically with customer inputs. - [Interactive Language in Agentforce A Guide with Examples and FAQs](https://phenoble.com/blogs/interactive-language-in-agentforce-a-guide-with-examples-and-faqs): Modern customer experiences demand AI assistants that can adapt to user preferences, including language and tone. - [Transfer AI Agent to Live Agent in Salesforce](https://phenoble.com/blogs/transfer-ai-agent-to-live-agent-in-salesforce): Agentforce is Salesforce's AI-powered conversational agent, built to handle customer queries via digital channels like chat. - [Scheduled Jobs in Salesforce: Resume and Pause, A New Feature You Should Know](https://phenoble.com/blogs/scheduled-jobs-in-salesforce-resume-and-pause-a-new-feature-you-should-know): Salesforce's Resume and Pause feature for Scheduled Jobs gives admins control over recurring Apex jobs without deleting and recreating them. - [Secure your salesforce data with encryption and digital signatures](https://phenoble.com/blogs/secure-your-salesforce-data-with-encryption-and-digital-signatures): How to protect Salesforce data at rest and in transit with platform encryption and digital signatures, with implementation examples. - [How to Register at the TDX Bengaluru Agentforce Hackathon](https://phenoble.com/blogs/how-to-register-at-the-TDX-bengaluru-agentforce-hackathon): TDX is the premier developer conference for the Agentforce ecosystem. This event is essential for developers, administrators. - [How to integrate salesforce with teamup](https://phenoble.com/blogs/how-to-integrate-salesforce-with-teamup): How to integrate Salesforce with Teamup: generate an API key, store a bearer token, create a Named Credential, and sync sub-calendars. - [Understanding salesforce strip inaccessible for security and permissions management](https://phenoble.com/blogs/understanding-salesforce-strip-inaccessible-for-security-and-permissions-management): Salesforce provides a powerful toolset for developers to manage and enforce - [How to Secure Your Salesforce Queries with String.escapeSingleQuotes](https://phenoble.com/blogs/how-to-secure-your-salesforce-queries-with-String-escapeSingleQuotes): How String.escapeSingleQuotes protects Apex SOQL queries from injection, with examples of vulnerable code and the secure version. - [Lightning tree grid table inside lightning web component](https://phenoble.com/blogs/lightning-tree-grid-table-inside-lightning-web-component): How to build a lightning-tree-grid inside a Lightning Web Component to show hierarchical data with expandable rows and nested records. - [Append edit and delete button inside dropdown menu of actions to a column in lightning datatable](https://phenoble.com/blogs/append-edit-and-delete-button-inside-dropdown-menu-of-actions-to-a-column-in-lightning-datatable): In this blog we will learn how to add actions in lightning datatable.. - [Passing Wrapper from Apex to Flow in Salesforce](https://phenoble.com/blogs/passing-wrapper-from-apex-to-flow-in-salesforce): In Salesforce development, integrating Apex with Flows allows for powerful automation and customization. - [Salesforce CPQ: Custom Actions](https://phenoble.com/blogs/salesforce-CPQ-custom-actions): Custom actions are buttons that sales representatives can utilize to perform specific actions within the CPQ interface. - [Salesforce CPQ: Summary Variable](https://phenoble.com/blogs/salesforce-CPQ-summary-variable): Summary Variable allows you to perform mathematical operations on collected values from a number of fields associated with various records. - [How to configure first experience site in salesforce](https://phenoble.com/blogs/how-to-configure-first-experience-site-in-salesforce): Salesforce Experience Cloud use to create branded digital experience to share information and collaborate with people who are key to your business process. - [How to Sync Outlook with Salesforce Using Einstein Activity Capture](https://phenoble.com/blogs/how-to-sync-outlook-with-salesforce-using-einstein-activity-capture): In today's fast-paced business environment, sales teams are constantly striving - [Salesforce CPQ: Guided Selling](https://phenoble.com/blogs/salesforce-CPQ-guided-selling): Guided selling in Salesforce CPQ is a feature that helps sales reps quickly and easily find the right products for their. - [Salesforce CPQ Account Based Contract Pricing](https://phenoble.com/blogs/salesforce-CPQ-account-based-contract-pricing): In Salesforce CPQ, account based contract pricing allows you to negotiate and apply custom prices for products and services - [Salesforce CPQ: Percent of Total Pricing](https://phenoble.com/blogs/salesforce-CPQ-percent-of-total-pricing): In Salesforce CPQ, Percent of Total pricing is a feature that allows you to set a product's list price as a percentage of the. - [Salesforce CPQ Block Pricing](https://phenoble.com/blogs/salesforce-cpq-block-pricing): Block pricing is used for managing product pricing based on quantity. It allows you to define different price points for specific quantity ranges. - [Salesforce CPQ Bundle Product](https://phenoble.com/blogs/salesforce-cpq-bundle-product): A bundle product is a grouping of multiple individual products or services that are sold together as a single package. - [Salesforce CPQ: Configuration Attribute](https://phenoble.com/blogs/salesforce-cpq-configuration-attribute): A configuration attribute in Salesforce CPQ is a picklist field that allows you to define specific characteristics or options for a product or bundle. - [Salesforce CPQ: Cost and Markup Pricing](https://phenoble.com/blogs/salesforce-cpq-cost-and-markup-pricing): Cost pricing is a method of setting product prices based on their cost plus a desired markup. This means that instead of using. - [Salesforce CPQ : How to Setup Salesforce CPQ](https://phenoble.com/blogs/salesforce-cpq-how-to-setup-salesforce-cpq): CPQ stands for Configure, Price, Quote. It is a business software that helps businesses to automate the process of configuring, pricing, and quoting. - [Salesforce CPQ Option Constraints](https://phenoble.com/blogs/salesforce-cpq-option-constraints): Option constraints in Salesforce CPQ control which product options can be selected together inside a bundle. What they are and how to create them. - [Salesforce CPQ Product Rule](https://phenoble.com/blogs/salesforce-cpq-product-rule): A Product Rule in Salesforce CPQ is a powerful tool that allows you to automate business logic and guide sales reps during the product configuration process. - [Salesforce CPQ Subscription Product and Price Dimensions (Multidimensional Quote)](https://phenoble.com/blogs/salesforce-cpq-subscription-product-and-price-dimensions-multidimensional-quote): In Salesforce CPQ (Configure, Price, Quote), a subscription product refers to a type of product or service that is sold on a recurring basis. - [Record trigger flow](https://phenoble.com/blogs/record-trigger-flow): As businesses evolve and user expectations soar, the demand for robust automation solutions has never been higher. Enter Record-Triggered Flows. - [Email to Lead in Salesforce](https://phenoble.com/blogs/email-to-lead-in-salesforce): Email-to-Lead is a feature in Salesforce that enables businesses to automatically convert incoming emails into potential sales leads. - [Web to Case in Salesforce](https://phenoble.com/blogs/web-to-case-in-salesforce): What Web-to-Case is in Salesforce and how to build a Web-to-Case form so website support requests become cases automatically. - [Web to Lead in Salesforce](https://phenoble.com/blogs/web-to-lead-in-salesforce): What Web-to-Lead is in Salesforce and how to create a Web-to-Lead form so website inquiries land in your CRM as leads automatically. - [How to communicate between unrelated components using Lightning Message Service](https://phenoble.com/blogs/how-to-communicate-between-unrelated-components-using-lightning-message-service): In Salesforce, you can establish communication between Lightning Web Components (LWCs) using various methods. - [Life cycle hook in aura components](https://phenoble.com/blogs/life-cycle-hooks-in-aura-components): How Aura components are instantiated, rendered, and rerendered, and which lifecycle hooks fire at each phase so you can hook in the right logic. - [How to email to case in salesforce](https://phenoble.com/blogs/how-to-email-to-case-in-salesforce): Email-to-Case is a feature in Salesforce that allows you to automatically create or update cases in Salesforce Service Cloud from inbound emails. - [Life cycle hooks in lightning web component](https://phenoble.com/blogs/life-cycle-hooks-in-ligtning-web-component): Lightning Web Component lifecycle hooks explained: constructor, connectedCallback, renderedCallback, render, disconnectedCallback, errorCallback. - [Security Level Permission In Salesforces"](https://phenoble.com/blogs/security-level-permission-in-salesforces): Sharing settings in Salesforce control who can view, edit, and share records. What they are, how to define them, and the options available.