Summary

  • Frigade launched the Assist API on 8 September, offering product answers and contextual guidance through a customer's existing agent.
  • Keeping the conversation in-house does not settle who maintains product knowledge, approves corrections or carries the cost of a wrong answer.

A software company may have built its own agent and still not want to teach it every corner of its product. Frigade is selling into that gap. Its 8 September announcement makes product assistance callable from an existing agent, without adding a competing chat box. The commercial proposition is to buy a capability while keeping the customer-facing conversation.

That is a more interesting boundary than the number of lines needed to connect an API. According to the product page, the customer's agent decides when to request help and what to do with the result. A recognisable interface can therefore stay put while part of the explanation behind it comes from another supplier. For a buyer, continuity of appearance and continuity of operational control are different purchases.

Knowing the screen is not knowing every obligation

Frigade describes browser-based learning, refreshed as a product changes and supplemented by written material. These are vendor descriptions, not independent evidence that every role or release is covered. A button visible to one account need not be available to another; nor does a visible setting by itself establish what a customer's contract includes.

The important operating question is how a discovered change becomes a checked answer. Someone must decide which user roles and exceptional workflows to test, and when stale guidance should be withheld. Buying the mapping work can reduce a task for engineers. It does not make that acceptance decision disappear.

The feedback feature lets support and product teams coach responses. That moves an economically useful lever nearer the people who see customer confusion. It also creates a review problem: a sensible correction to one exchange may be too broad for another. Ownership needs to include approval, scope and reversal, not simply access to a feedback box.

A useful answer is not an executed task

There are two meanings of “tool call” to keep apart. An agent can call Frigade for help. Separately, Frigade's existing action feature uses functions developers explicitly expose. The launch is not evidence that an assistant acquires arbitrary powers inside a customer's application.

Likewise, sending a conversation to a person is not the same as resolving it. Frigade describes context-preserving support handover. Buyers should follow the issue beyond that transfer: was the task completed, did the user return, and how much staff work remained?

The public Growth plan starts at $1,000 a month with 2,500 queries and two agents. That bundle is not a marginal query price or a complete Assist API quotation. Its economic test is the total work avoided after review, escalation and integration costs—not the reassuring disappearance of a second chat window.