Salespeak Company Context

Answer a question about the user's own company from the knowledge it keeps in Salespeak. Use it when a request depends on a fact about the user's own company: its product and capabilities, pricing and plans, integrations, security and compliance, customers, competitors, ideal customer, or how it positions and describes itself. Typical requests are a prospect email, call prep, an objection, a comparison or a partner intro. It is not meant for rewriting or summarizing text the user provided, for tone changes, or for questions unrelated to the user's company. It reads the company's knowledge and changes nothing. Which version of a disputed fact is right is decided by an admin in the Salespeak app, not by this tool. Args: query: What you need to know about the company, as a question (required). One topic per call. Returns: JSON with: - `status`: "answered", "partial", or "not_in_kb" when the company has no recorded answer. - `answer`: the answer, grounded in the company's knowledge bank. - `records`: the records behind the answer, each with an `authority` (`approved` means a person at the company approved it); `authority_summary`, `freshness` and `gaps` describe them. - `conflicts`: where the company's own sources disagree on this question. The user sees these versions in a card and chooses one there. - `other_open_conflicts`: how many other open conflicts the company's knowledge holds. - `knowledge_scan`: whether the knowledge was ever checked for conflicts ("done", "running" or "never") and the page where an admin runs the check. - `notes`: plain statements about this result, for example that the user has not chosen between conflicting versions yet.

ask_company_context

Mark, in the user's own company workspace, that two of its records disagree and need a decision. Use this when the user says a company answer is wrong, or asks to report or escalate a disagreement between company sources. It stores one flag in the same Salespeak workspace this app reads from, the one the user signed in to: who raised it, and optionally which record they believe is right and why. It sends nothing to any other system, service or person, and changes no answer. The company's admins see the flag the next time they review conflicts in that workspace. Args: conflict_id: The conflict's id, from the `conflict_id` of a conflict in a company context answer or in the list of open conflicts (required). preferred_record_id: The conflict's record the user believes is right, if they said. note: A short reason in the user's words (up to 1000 characters). Returns: JSON confirming the flag, or an error message.

flag_knowledge_conflict

List where your company's own knowledge contradicts itself. Use this tool to see the open conflicts between records in your knowledge bank, found by the offline knowledge bank scan: two sources that state different prices, limits, plans, dates or definitions for the same thing. Perfect for: - "What is inconsistent in our company context?" - "Where do our sources disagree?" - "What should product marketing settle first?" Args: limit: Maximum conflicts to return (default 10, capped at 25). Returns: JSON with `conflicts`, most severe first. Each has a stable `conflict_id`, the topic, how the records disagree, and both records with their sources.

list_knowledge_conflicts

Quote, for each record of a conflict, the passage that states the disputed fact. It exists for the Company Context card, which calls it once a conflict is on screen so each option can show the sentence that disagrees and not the start of the record. It reads only records of the user's own company and changes nothing. Args: conflicts: Up to 5 items of `{"record_ids": [...], "note": "..."}`, copied from the `conflicts` of a company context answer (required). Returns: JSON `{"claims": [{record_id: passage}, ...]}`, one object per conflict, in order. A record with no such passage has no entry.

quote_conflict_passages