#Sales Cloud169 debatiendo

@Maiko Tsuchida さん 

こんなレポートでいいですか？ 

商談が関連する活動 レポートを選択してみてください 

Hi Barb, 

I couldn't find a confirmed public Known Issue tied specifically to Winter '27 for this yet, so this may be new/unreported so far. A few things worth checking first, since these are the most common causes of activities suddenly disappearing after a release: 

1. Setup > Record Page Settings — check if "Default Activities View" got reset to "Related List" instead of "Activity Timeline" (or vice versa) for affected users/profiles. Releases sometimes reset this default. 

2. Check if it's a permissions/FLS issue on Task/Event fields specifically introduced by a release-related metadata change, rather than the timeline component itself. 

3. Ask affected users to try Personalize view (gear icon on the Activity component) to reset their individual view — a stale personalized setting can also break post-release. 

Reference:

If none of that resolves it and you can reproduce it consistently, worth opening a case and referencing Winter '27 explicitly — if others in this group hit it too, it'll likely get logged as a Known Issue soon.

Hi Tamas Society team, 

Confirmed: your 10 donated Enterprise Edition licenses don't include WhatsApp — that functionality lives in Digital Engagement, a separate paid add-on to Service Cloud Enterprise/Unlimited, priced per-user (retail ~$75/user/month). It's not bundled free with the Power of Us donated licenses. 

Direct answers to your questions: 

1. Do donated licenses include WhatsApp? No. You'd need Digital Engagement added on top of Service Cloud. 

2. Is nonprofit discount pricing available for it? Yes — Digital Engagement is listed under Salesforce's Nonprofit Pricing page as one of the products eligible for discounted (not free) nonprofit rates through the Power of Us program. 

What each of your 5 requirements maps to: 

1-2. Capture WhatsApp enquiries as Leads/Contacts + log conversation — Digital Engagement creates MessagingSession/MessagingEndUser records tied to Lead/Contact automatically. 

3. Auto-assign to team member — Omni-Channel routing (included with Service Cloud) handles this once Digital Engagement is active. 

4. Send approved outbound WhatsApp messages — needs Meta-approved message templates plus the WhatsApp Outbound Messages entitlement. 

5. Connect to Sales pipeline — standard, since Leads/Contacts converting into Opportunities works the same regardless of source channel. 

Next step: Since you're already an approved Power of Us nonprofit, contact your Salesforce Account Executive (or your nonprofit-specialist partner) directly and ask specifically for nonprofit pricing on: Service Cloud Enterprise (if not already included) + Digital Engagement (WhatsApp channel). They can quote the exact discounted rate for your org size. 

Reference:

Worth asking your Account Executive if a Nonprofit Cloud edition bundle already includes Digital Engagement at a lower combined cost, rather than adding it separately — bundling sometimes prices out better for smaller orgs like yours.

Hi @Muhammad Arsalan

There was a post about the same error yesterday as well. The ID for this package has been changed several times in the past. 

I encourage you to get help from the Trailhead support team. 

https://trailhead.salesforce.com/trailblazer-community/feed/0D54S00000JeXW9

I tried it too, and it certainly won't install.

Hi Raviraj, 

Try the below path: 

1. Enable WhatsApp as an Enhanced Messaging Channel in Service Cloud, connecting your Meta Business/WhatsApp Business account. 

2. Set up Omni-Channel routing (queue + routing config, or an Omni-Channel flow) so incoming WhatsApp sessions land with the right team, including support for bot-based routing. 

3. Auto-create a Case from an incoming message using an Einstein Bot or Flow — the bot captures the customer's intent, and on unresolved/escalation intents, invokes a flow action to create a Case, tagging it back to the messaging session. 

4. Send updates back on the case (like "latest update") using Messaging Components — reusable structured message templates (Question, List Selector, etc.) that reps or flows can push into the WhatsApp thread, including dynamic content pulled from the Case record. 

5. For proactive/automated updates outside an active session (e.g., status changed to Resolved), use Template-Based Automated Messages — these require Meta-approved templates and the WhatsApp Outbound Messages SKU. 

The exact Trailhead module walking through this entire flow end-to-end (WhatsApp setup → routing → messaging components → case creation) is "WhatsApp for Agentforce Service," which I'd start with since it's hands-on with the Ursa Major Solar org. 

References: 

-

-

-