Conga Adds Deal-Level Discount Rules as It Opens Quotes to Copilot and Claude
Conga's October 14 release lets Copilot and Claude see quotes and approvals and send agreements for signature. Its new CPQ controls check discounts against the whole quote instead of each line.
TL;DR
- Conga's October 14 release connects Copilot and Claude to its quotes and approvals and adds CPQ controls that check discounts per deal.
- Conga names one assistant action, sending an agreement for signature, and hasn't said whether the MCP server can submit or change quotes.
- Deal desks should sort approvals into read, trigger and human-only, and set deal-level discount policy before reps quote through assistants.
Conga launched an MCP server on October 14 at its Conga Connection event in Amsterdam. It connects Claude, Microsoft Copilot and other MCP-compatible assistants to the platform where Conga’s customers build quotes and contracts. The October release published the same day added deal-level pricing controls to Conga CPQ, so organizations can "apply pricing policies across the full quote" instead of checking discounts one line at a time. Conga says it has more than 10,000 customers, including over half of the Fortune 100.
The pricing change matters more now that assistants can reach the quote. Line-level discount thresholds were written for a person changing one line and waiting for a manager. A rep who can ask the assistant already open on their desktop about a quote may find it easier to learn where those lines sit. A threshold a rep can see turns into a target. Conga's new rule reads the whole deal, so it can't be cleared one line at a time. Conga's announcement doesn't say how far an outside assistant gets, which leaves the deal desk to set the limits.
Conga names one assistant action, sending an agreement for signature
Conga's announcement gives three examples. A CFO asks Copilot which contracts expire in the next 90 days, and a legal operations lead asks Claude what an amendment changed. The third is for the deal desk. A sales rep can "see where a quote stands in approval and send the agreement for signature." The release post describes the server as access to contracts, quotes, obligations and approvals through natural language. Neither page says an outside assistant can change a price, apply a discount, submit a quote for approval or approve one. Neither says how the server handles user permissions. Conga didn't disclose pricing or an availability date.
Conga's own Sales Agent for Salesforce, documented for the June '26 release, already goes further. It can create quotes and "submit quotes for approval." Conga says that agent respects user permissions and lets admins limit which fields it reads and changes. So the vendor ships an assistant that triggers approvals inside its own product today. It hasn't published whether the MCP server exposes the same actions to Copilot and Claude, under the same limits.
Line-level discount rules are the weak point if assistants can read them
On Conga's own description, the MCP server mostly reads. Its examples show an assistant checking where a quote stands in approval. None show it reading the thresholds behind the approval, and a rep could already check a quote's approval status in the CPQ screen. If the server runs under each rep's existing permissions, the approval rules the deal desk already maintains still decide what happens.
No one has reported an assistant surfacing discount thresholds, so this is a risk to plan for. If an assistant can read the approval rules and every pending approval, it can tell a rep how deep a discount can go before it trips a review. Line-level rules give that answer one at a time. Deal-level controls close the gap only if someone sets them before reps ask an assistant to build the quote. SalesTech Edition's write-up makes the same point about order, quoting ServiceNow's CPQ head (whose company competes with Conga) on pricing rules coming before AI-built quotes.
What this means for deal desk and RevOps leaders
If you run Conga, or any CPQ that ships an MCP server, sort every approval into three groups before reps connect an assistant: what the assistant may read, what it may trigger and what stays with a person. Sending an agreement for signature is the trigger Conga names, so decide whether an assistant may send one while an approval on the quote is pending or was granted as an exception. Treat discount thresholds as sensitive data too, and decide whether reps should see them through an assistant at all.
Then get Conga's answers in writing. Ask whether the MCP server runs under each rep's own permissions and the field limits admins set for the Sales Agent. Ask which actions it exposes beyond reading and sending for signature, and whether assistant-initiated actions are logged apart from a rep's own clicks. Business of GTM made the same argument to CX leaders about which support journeys an outside agent may read or change. The deal desk owns the sales version of that list.
Set the deal-level policy before the assistant goes live, with a margin floor on the full quote and a named approver for exceptions. For the first full quarter, report discount depth on assistant-built quotes separately from the rest. If assistant-built quotes discount deeper, that report will show it before gross margin does.
Odds are the MCP server gains quote submission within a year, since Conga's own Sales Agent already submits quotes for approval. Get the three groups signed off before that release lands.
