The Salesforce Platform for BAs (Clouds + AI Overview)

Purpose: free salespeople from administrative drag so they can spend time actually selling.

Sales roles carry a surprising amount of admin work: logging customer interactions, tracking inventory and prices, processing orders, chasing approvals. Sales Cloud centralizes all of it. Key capabilities include lead and opportunity tracking through the sales funnel, automated sequences of emails, alerts, and tasks at each stage, a single home for all correspondence, approval workflows (for example, discount approvals), and reference data for pricing and inventory.

Who relies on it: small businesses, consultants, service providers, marketers, distributors, brick-and-mortar retail, recruiters, online marketplaces, manufacturers, and suppliers. In other words, nearly everyone who sells anything.

Purpose: manage customer inquiries and support at scale.

Service Cloud is built around the case: a record representing a customer's service request, question, or complaint. Around the case, Service Cloud layers workflow tools that route the right work to the right person automatically: email-to-case and web-to-case (turn inbound messages into tracked cases), assignment rules (send cases to the right team), escalation rules (raise the alarm when a case sits too long), queues (shared work pools), and auto-response rules (immediate acknowledgments).

If Sales Cloud is about winning customers, Service Cloud is about keeping them.

Purpose: reach customers with consistent, personalized messages across fragmented channels.

Today's customers interact with brands across email, social media, mobile, ads, and the web, often in fragmented ways. Marketing Cloud addresses that fragmentation with deeper segmentation, targeting, and personalization. Historically its parts came in two flavors: studios (manage content and specific channels: email, mobile, advertising) and builders (manage data and campaign automation, most famously Journey Builder, which visually maps the journey a contact takes through your marketing touchpoints).

Currency note, worth reading twice: as of mid-2026, Salesforce has been rebranding this product family under its AI push. You will see the names Agentforce Marketing and Marketing Cloud Next for the current agent-driven generation of the product, with "Marketing Cloud" still widely used for the classic product line. Expect job postings and client conversations to mix these names freely for years. If a client says "Marketing Cloud," clarify which generation and which components they own. This is a perfect example of why BAs verify product names per project rather than memorizing them once.

Purpose: build the outward-facing digital front doors of an organization.

Experience Cloud creates portals, forums, websites, and help centers where customers, partners, and even employees engage with the business. Key capabilities: branded community portals (customer support, partner engagement, employee collaboration), personalization driven by CRM data (the portal knows who you are and shows relevant content), content management for knowledge articles and FAQs, and deep customization of the interface.

For a BA, Experience Cloud projects are especially fun: they sit right at the intersection of process design, user experience (Module 19), and content strategy (Module 21).

Purpose: gather all customer data in one place so the organization can act on a complete picture.

Modern organizations have customer data scattered across dozens of systems. Data Cloud aggregates it. Its key capabilities, in plain English: data ingestion (pull data in from many sources, including outside Salesforce), identity resolution (recognize that "Bob Smith" in the billing system and "Robert Smith" in the support system are the same person, and merge the view), data processing (convert, purify, and improve data), audience segmentation (build precise groups from the unified data), and data activation (send the unified data back out to other applications where work happens).

Data Cloud has become the foundation for Salesforce's AI story, because AI is only as good as the data it can see. You may also encounter the name Data 360 for parts of this product family. Same idea: one unified customer data layer.

Purpose: help colleges and universities centralize data for admissions, financial aid, student success, and career services, supporting students through their whole lifecycle.

Remember the funnel? Higher education has the most elaborate version you will ever see: suspects (might apply someday) become prospects, then applicants, then confirmed, deposited, and enrolled students, and ultimately alumni and donors. The surrounding cast is huge too: students, parents, instructors, staff, secondary schools, recruitment agents, researchers, partner institutions.

Two flagship capability areas:

• Recruitment & Admissions: streamline recruiting and manage applications efficiently. Lead management nurtures applicants through the top of the enrollment funnel; action plans assign students the tasks and documents needed to complete applications; application management gives staff streamlined review processes.
• Student Success: centralize data so advisors can track progress and step in early. Curriculum management models programs, courses, and degree requirements; milestone tracking flags students who are falling behind before it becomes a crisis.

Purpose: deliver personalized, connected care across the healthcare ecosystem: providers, payers, medical device companies, and pharmaceutical manufacturers.

Healthcare's version of the funnel is a lifelong continuum of engagement: health history, diagnoses, appointments, procedures, medications, and health programs, involving patients, families, providers, hospitals, insurers, pharmacies, and more.

Key capabilities:

• Patient 360: one unified view of the patient, consolidating demographics, clinical data, and interactions from many sources so providers can make informed decisions.
• Care Plans: create, track, and manage personalized care plans with goals, tasks, and milestones, adjusting treatment as progress is monitored.
• Care Coordination: let care teams collaborate across multiple providers, share information, and message patients securely.
• Health Timeline: visualize a patient's history (encounters, lab results, medications) in one intuitive view.

Typical implementations serve either providers (hospitals, clinics, ambulatory care centers) or payers (insurance companies and government healthcare agencies). One caution to carry from day one: healthcare projects involve regulated, protected data, and the security concepts in Module 7 stop being theoretical the moment you touch one.

Purpose: help nonprofits manage operations, engage donors, and advance their missions.

Nonprofit Cloud supports four pillars: fundraising management (track donations, manage campaigns, cultivate donor relationships end to end), program management (plan, track, and measure the impact of programs delivered to constituents), grantmaking (manage the full grant lifecycle from application to disbursement and reporting), and volunteer management (recruit, schedule, and track volunteers).

A Quick Primer on the Nonprofit Sector

Because so much Salesforce consulting work serves nonprofits (and because many students in this course may work with community organizations here in Hawaii), it is worth understanding what makes a nonprofit distinct:

• Purpose: nonprofits advance social causes and provide public benefit; they are mission-driven rather than profit-driven.
• Governance: volunteer boards of directors provide oversight and accountability to constituents.
• Revenue allocation: revenue must advance the mission; profits cannot be distributed to shareholders, board members, or individuals.
• Regulation: nonprofits operate under specific rules and enjoy tax-exempt status (501(c)(3) in the U.S.) reflecting their public-interest role.

Compare the three sectors side by side:

Why this matters to a BA: a nonprofit client's "customers" are donors, volunteers, grantees, and program participants all at once, their budget approval works differently (often a board decision), and their success metrics are mission outcomes rather than revenue. Discovery questions that work at a sales company will miss the mark at a food bank unless you adjust.

You have used a traditional chatbot: it matches your words against scripted answers, and the moment you step off the script, it falls apart. Agentic AI is a different idea. An AI agent can analyze data, make decisions within a defined scope, and take actions across systems, without a human driving every step.

Salesforce's umbrella brand for this capability is Agentforce. Conceptually, an agent is a self-service, personalized assistant for a defined job: answering customer service questions around the clock, qualifying inbound sales leads and booking meetings, drafting and optimizing marketing campaigns, or assisting employees with day-to-day data lookups and routine tasks.

However the products evolve, four concepts have stable value for a BA:

1. Agents are defined by jobs, scope, and actions. Building an agent means defining what job it does, what topics it may handle, what data it may see, and what actions it may take. That definition work is requirements work. Read that sentence again, because it is a career signal: the skill this course teaches (turning fuzzy business needs into precise, testable definitions) is exactly the skill agent projects need.

2. Trust and guardrails are part of the design, not an afterthought. Business-grade AI requires explicit limits: which tasks the agent may perform, what data privacy rules apply, and when the agent must escalate to a human. Expect every AI requirement conversation to include guardrail requirements. "What should this agent refuse to do, and when must it hand off to a person?" is a question BAs will ask for the rest of their careers.

3. AI quality depends on data quality. Agents act on the data your org gives them (this is why Data Cloud matters so much). A messy database produces a confidently wrong agent. The unglamorous data hygiene work covered later in this course has become an AI prerequisite.

4. The business case is capacity. Agents take on routine, time-consuming tasks around the clock, freeing staff for higher-value work, and improving customer experience with faster, more personalized responses. When you scope AI work as a BA, that is the value language stakeholders respond to: hours reclaimed, response times cut, coverage extended.

Concretely, on projects that include AI capabilities, expect your BA responsibilities to include: documenting which use cases justify an agent (and which do not), eliciting the rules and knowledge the agent needs, defining escalation paths to humans, writing acceptance criteria for agent behavior (including what it must not do), and planning testing and training around a system whose behavior is less deterministic than a validation rule. None of that requires you to understand machine-learning mathematics. All of it requires the core BA craft you are learning in this course.