Explanation:

In the context of Energy & Utilities Cloud, which is built on Salesforce Industries (Vlocity) OmniStudio, integrating with DocuSign for eSignatures is accomplished using a combination of OmniScripts and Integration Procedures with specific pre-built actions.

Why Options B and D are Correct:

B. An OmniScript can be configured, and a DocuSign Envelope action can be used to email the contract for signature:
• OmniScripts are the guided interaction framework in OmniStudio.
• They can include a DocuSign Envelope action, a pre-built component that handles creation of a DocuSign envelope, attaches the contract document, and sends it to the specified recipients for signature.
• This is a declarative way to embed eSignature functionality into a business process like Contract Lifecycle Management.

D. An Integration Procedure with a DocuSign Signature action can be called from an OmniScript to email the contract for signature:
• For complex scenarios or additional data manipulation before sending to DocuSign, an Integration Procedure (IP) can be used.
• The IP can contain a DocuSign Signature action that handles the API call to DocuSign.
• This IP can then be invoked from within an OmniScript, providing a reusable, logic-rich way to manage the eSignature process.

Why the Other Options Are Incorrect:

A. The 'Send for eSignature' Velocity action:
• Velocity is a scripting language within OmniStudio for data manipulation and logic.
• It is not a container for actions like "Send for eSignature."
• There is no standalone "Velocity action" of this nature; actions reside within OmniScripts or Integration Procedures.

C. An Integration Procedure with an HTTP action:
• While technically possible to build a custom HTTP callout to DocuSign, it is unnecessary.
• Salesforce Industries (Vlocity) provides pre-built DocuSign actions ("DocuSign Envelope" and "DocuSign Signature") for declarative integration.
• Using pre-built actions is recommended, avoiding custom HTTP development.

Reference:
Salesforce Industries (Vlocity) OmniStudio: DocuSign Integration
• The Vlocity managed package includes pre-defined DocuSign Action Elements for OmniScripts or Integration Procedures.
• These actions abstract the complexity of the DocuSign API, allowing administrators to configure eSignature workflows declaratively.
• Typical Contract Lifecycle Management flow: generate contract document (via DOCX Template) → use DocuSign action within OmniScript to send for signature.

Explanation:

In Salesforce Energy and Utilities Cloud (using Industries CPQ / EPC), commodity pricing for energy products like electricity or gas is typically usage-based (also called consumption-based or volume-based pricing). The actual or estimated monthly amount a customer pays depends on their consumption (e.g., kWh of electricity used), multiplied by a unit rate (price per unit), often with tiered rates, standing charges, or taxes.

To calculate an estimated monthly amount during quoting (e.g., in the cart or quote preview):
• Configure the commodity product with usage pricing in Industries CPQ.
• Set up a Usage Price (or Pricing Element with Charge Type = Usage) on the product or price list.
• Define an Estimated Usage Quantity (e.g., average monthly kWh like 2000 kWh as a default or input via attributes/slider in reference UI).
• Use a calculation matrix or pricing rule to multiply estimated usage by the unit rate to derive the Usage Price Total (estimated monthly commodity cost).

This is the standard approach for variable commodity charges in energy/utilities, as documented in Salesforce Industries pricing modules. It provides transparency during customer acquisition (e.g., “Based on your estimated 500 kWh/month, your bill would be approx. $X”).

Why Not the Other Options:

A. Using one-time price:
One-time (one-off) charges apply to setup fees, deposits, or non-recurring items, not ongoing monthly commodity usage.

B. Using monthly recurring price:
Recurring pricing (e.g., fixed monthly fee) suits standing charges, service fees, or flat-rate subscriptions, but not variable commodity costs that fluctuate with consumption.

C. Using a subscription pricing plan:
Subscription plans handle recurring fixed or tiered charges (e.g., monthly access fees), but commodity pricing in utilities is primarily usage-driven rather than pure subscription. While subscriptions can include usage elements, the core for variable monthly commodity estimation is usage pricing.

References:
Salesforce Trailhead: “Guide to Configuring Usage Pricing in Salesforce” — Explains setting up usage pricing for commodities (electricity/gas), using estimated usage quantity × usage price to show estimated monthly totals in quotes/carts.
Salesforce Help: “Usage-Based Pricing for Industries CPQ” — Details enabling and configuring usage pricing for Energy & Utilities Cloud, including charge measurements for consumption-based billing.

Explanation:

The Energy & Utilities Contact Center Console in Salesforce Energy and Utilities Cloud is specifically designed to integrate with Salesforce Field Service for managing customer interactions that involve field work. It provides agents with tools to view available time slots, worker schedules, and to schedule service appointments (field technician appointments) directly from the console.

Official Salesforce documentation confirms that the Energy & Utilities Contact Center Console integrates with Salesforce Field Service and uses its capabilities to fetch live appointment data (such as time slots and technician availability) and to create and schedule service appointments.

Scheduling field technician appointments (creating and assigning Service Appointments in Field Service) requires the underlying Salesforce Field Service functionality. These features, including scheduling and dispatch tools such as Dispatcher Console, are tied to Field Service licenses (for example, Dispatcher or equivalent licenses).

Without the appropriate Salesforce Field Service license assigned to the user (or without org-level enablement), the scheduling features within the Contact Center Console would not be available or fully functional for creating and dispatching field technician appointments.

Why not the other options?
C. Energy and Utilities Base Service license — This is a core permission set license for accessing Energy and Utilities Cloud features such as the industry data model, console access, and customer service tools. It enables the Contact Center Console itself but does not provide the Field Service scheduling and dispatch capabilities required for managing service appointments.

D. Energy and Utilities Base Service license (duplicate option) — Same reasoning as above; it does not grant Field Service scheduling functionality.

E. Salesforce Service Console license — This is a general Service Cloud console license. While the Energy & Utilities Contact Center Console is built on Service Cloud, scheduling field technician appointments requires the Field Service add-on, not just the base Service Console license.

Salesforce Contact Center license — If referring to Digital Engagement or similar features, this license supports omni-channel and digital interaction capabilities, not field service scheduling and dispatch functionality.

References:
Salesforce Help: “Manage Field Service Appointments for Energy & Utilities Customers” — States that the Energy & Utilities Contact Center Console integrates with Salesforce Field Service and provides tools to schedule service appointments and related work.
Salesforce Help: “Schedule a Service Appointment for Energy & Utilities Customers” — Describes how the console interacts with Salesforce Field Service to fetch live service appointment data, including time slots and worker schedules.

Explanation:

✅ B. Use the Consumer Account record type → In Energy & Utilities Cloud, the Consumer Account record type is designed to represent individual subscribers (e.g., a household with an electricity account). This makes it easy to distinguish between consumer and business entities.

✅ C. Enable Person Accounts to model consumers → Person Accounts let Salesforce treat an individual customer as both an Account and a Contact in one record, which is ideal for B2C scenarios. Energy companies can leverage this to track residential customers without creating separate account-contact pairs.

Why not the others:

❌ A. Use the Account Contact Relation object → That’s used for defining relationships between contacts and multiple accounts (e.g., a consultant linked to multiple corporate clients). It’s helpful for complex B2B relationships but not the foundation for differentiating consumer vs. business accounts.

❌ D. Use Contacts just for B2B scenarios → Inaccurate. Contacts are used in both B2B and B2C contexts, but for consumers, Person Accounts are the correct modeling approach.

Reference:
Salesforce Energy & Utilities Cloud Data Model Guide
Salesforce Help: Person Accounts

Explanation:

A. Service Cloud → Service Cloud provides case management, knowledge, omnichannel, and agent tools. For a utility’s Customer 360 vision, it’s essential so service agents can view and resolve customer issues effectively.

D. Energy and Utilities Base → This license unlocks the industry-specific data model (Consumer Accounts, Service Points, Premises, Service Agreements, etc.) and utility-specific capabilities like meter-to-cash visibility. It’s the foundation for Energy & Utilities Cloud implementations.

Why not the others:

B. Contract Lifecycle Management (CLM) → Useful for managing complex contracts, but not central to giving agents a Customer 360 across utility billing and service processes.

C. Configure Price Quote (CPQ) → More relevant for quoting and sales processes. Utilities usually don’t need CPQ for standard residential/commercial utility billing.

Reference:
Salesforce Help: Energy & Utilities Cloud Overview
Salesforce Service Cloud Overview