The independent daily for Salesforce admins, developers and architects

Curated by Abhinav (opens in a new tab)

Recommended

Poor agent context inflates token use and Flex Credit spend (opens in a new tab)

You will learn how weak business context makes Salesforce agents burn far more tokens, and which low-cost habits (documenting objects, defining terms, cleaning records, using Flow where no reasoning is needed) reduce that cost before Headless Platform Interaction metering starts.

  • 43,000: Tokens used without the harness, with a wrong answer
  • 7,000: Tokens used with the configured harness
The same question used far fewer tokens once the agent had proper business context

A Dreamforce demo followed a sales rep asking an agent which customers to focus on to close a Q3 gap. Without a harness, the agent used 43,000 tokens and gave a wrong answer: it recommended a frozen customer, missed a renewal already in the pipeline, and misread fiscal Q3. With a properly configured harness that pulled live pipeline data, used a semantic layer to define Q3, and drew on memories of past customer interactions, the same question took 7,000 tokens and produced a sound answer.

The article argues that Flex Credit burn comes largely from the context an agent must work out for itself. Outcome-based pricing and the planned charge for Headless Platform Interactions make this matter, since the meter runs whether or not the answer is good. No multiplier has been published yet, and Salesforce has promised 30 days’ notice before metering starts. Context packs let a harness supply only the subset of information an agent needs, so the aim is the right context rather than the most context.

The author suggests practical steps for now: fully document the one or two objects agents will rely on most, write down ambiguous definitions such as fiscal quarters, clear stale and duplicate records, use a plain Flow where a deterministic answer is enough, and record a consumption baseline before metering gets more complicated.

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

Worth reading?