Today4 stories · 3 briefs

The Daily Org

Spring '27Sandboxes 6 Feb 2027

Curated by Abhinav (opens in a new tab)

Vol. I · No. 17The independent daily for Salesforce admins, developers and architects4 stories · 3 briefs

Must-readAgentforce and AI

Route real phone calls to your Agentforce Voice agent using Salesforce CLI and Omni-Channel flows (opens in a new tab)

You will learn how to configure an Agentforce Service Agent user, request a phone number, and build a one-element Omni-Channel routing flow to connect callers to your voice enabled script.

Why read this

You will also know how to verify call routing and inspect post call records using the Salesforce CLI.

  1. Verify entitlements and licenses
  2. Create an Agentforce Service Agent user
  3. Build an Omni-Channel routing flow
  4. Activate the flow and PSTN Voice channel
  5. Test the call and query records
This diagram shows the five-step process for routing real phone calls to an Agentforce Voice agent

The article explains that routing live calls requires an active Agentforce Voice agent, a dedicated Einstein Agent User license, and available inbound voice credits. Developers must verify entitlements and create a service agent user through the Salesforce CLI before configuring any routing logic.

A call reaches the agent through three linked components: a purchased phone number, a PSTN Voice channel, and an Omni-Channel flow. The flow requires a single input variable named recordId and one Route Work element that directs the call to the activated service agent, with a voice queue as a fallback.

After activating the flow and channel, administrators can test the connection by dialing the assigned number. Since live sessions do not generate transcripts, the author demonstrates how to query VoiceCall and AgentWork records via SOQL to confirm call duration, vendor type, and successful routing.

Read the original at Salesforce Developers Blog (opens in a new tab)

Worth reading?

RecommendedApex and platform

Securing Salesforce to LLM integrations with Apex and scoped permissions (opens in a new tab)

Readers will learn how to enforce least-privilege access when calling external language models from Apex, including proper use of WITH USER_MODE, Named Credentials, and response validation.

The article argues that connecting Salesforce to a large language model takes more than an API key. The integration should control which records and fields the model can reach, protect credentials, minimize the data sent, and stop AI output from triggering unauthorized actions. It proposes an architecture with five parts: Salesforce enforcing permissions, Apex or middleware handling authorization and request building, Named Credentials managing the endpoint and authentication, the LLM API generating output, and a validation layer checking results before they are shown or used. A support assistant summarizing Cases, for example, needs only subject, description and status, not full contact or financial history. Authorization should happen before data is sent to the model and again before any business action follows its response.

The piece distinguishes several permission mechanisms that must be combined rather than relying on OAuth scopes alone: integration identity, object permissions, field-level security, record sharing and application-level restrictions. In Apex, declaring a class with sharing does not enforce object and field permissions, so the article recommends WITH USER_MODE on supported SOQL queries, with Security.stripInaccessible() as an alternative for removing inaccessible fields. For credentials, it recommends never hardcoding API keys and instead using External and Named Credentials, granting access through Permission Sets, and keeping separate configurations for each environment. A sample Apex class summarizes a Case through the OpenAI Responses API, querying only needed fields, sending a minimal payload, and checking the HTTP status and response structure before returning text.

The article also covers defending against prompt injection, since record text from emails or tickets may contain malicious instructions. Its safeguards include treating retrieved text as untrusted, limiting fields and records, avoiding unrestricted query or tool access for the model, checking proposed operations against a server-side allowlist, requiring human approval for consequential changes, and filtering documents by user access before they reach the model in retrieval-based designs. For scale, it suggests asynchronous processing with Queueable Apex or middleware for longer tasks, bounded retries with backoff only for suitable errors, request identifiers to prevent duplicate actions, token and latency monitoring, and cache designs that respect permission changes. The conclusion urges starting with a read-only use case and adding write capabilities only after authorization and failure handling are tested.

Read the original at dev.to (opens in a new tab)

Worth reading?

Agentforce and AI

Salesforce discusses partner concerns over new AI agent billing model (opens in a new tab)

Readers will learn how Salesforce plans to charge Flex Credits for external AI agent interactions via MCP and APIs, and what partners are urging the company to adjust regarding predictability and friction.

Salesforce has introduced a pricing model requiring external artificial intelligence agents to register on the platform and consume Flex Credits for every successful call made through the Model Context Protocol or direct application programming interfaces. The initiative tracks each interaction as a Headless Platform Interaction, shifting costs away from traditional seat licensing toward usage-based billing for agentic traffic.

The announcement triggered significant pushback from implementation partners and independent architects who warned that per-action charges would create financial friction and discourage developers from building around the platform. Critics noted that customers already face heavy seat costs and questioned whether the market would accept paying for every individual request made by automated systems.

In response to the community reaction, Salesforce leadership initiated direct conversations with key ecosystem stakeholders to address these concerns. Participants emphasized the need for transparent pricing structures, additional platform value to justify the fees, and mechanisms that allow partners and administrators to continue leveraging artificial intelligence tools without unexpected production expenses.

Read the original at Salesforce Ben (opens in a new tab)

Worth reading?

Apex and platform

Master six overlooked Developer Console features to speed up debugging and querying (opens in a new tab)

You will learn how to configure saved workspace layouts, set persistent debug log levels, and use checkpoints and tree views to trace execution faster.

Why read this

The guide also explains how to export raw logs for side-by-side comparison when troubleshooting production issues.

The article positions the Developer Console as a lightweight scratchpad for quick queries and debugging, highlighting six underused capabilities that improve daily workflows. It begins by explaining how saved perspectives organize interface panels for specific tasks like data investigation versus breakpoint tracing.

It details how checkpoints capture heap and variable state at exact execution lines without cluttering code with debug statements. The author also recommends defining custom log levels for Execute Anonymous runs to filter out noise and speed up analysis.

Further tips cover the Query Editor, which now supports multi-line SOQL and maintains session history for rapid iteration. Debug logs can be navigated using a tree view to isolate specific classes, and the raw log export function allows developers to download and diff outputs across environments to pinpoint failures.

The piece concludes by reinforcing that while the console handles ad-hoc tasks efficiently, Visual Studio Code with the Salesforce extensions remains the superior choice for source tracking, testing, and deployment workflows.

Read the original at dev.to (opens in a new tab)

Worth reading?

In brief