Predictika · Contact center editions, add-ons, named and concurrent seats, and committed usage
An AI sales agent prepares a subscription quote for a cloud contact center platform: an edition, an optional add-on, a seat model, a number of seats, a term, a committed usage amount against expected usage, and a discount. Before the quote goes out, the agent sends it to Predictika's validator, which checks all of it together, including the net total the agent states, and reports every problem in one pass.
This validator checks any quote for this product line against the rules below, not just the scenarios shown on this page.
Any quote that touches these rules is in scope, not only the scenarios pictured here. Not checked: other Genesys products, overage billing after signing, real list prices, taxes and multi-currency quoting.
6 scenarios in 3 groups · each group runs from the agent’s first attempt to the outcome · click one to switch
Illustrative agent statement. The validator receives the structured request below.
Proposing agent: AI sales agent (scripted)
Before sending, the agent must call Recorded run
What this means
Our assessment of what a typical rules-based CPQ (product rules, price rules and validation rules, as in Salesforce CPQ) does with the same cases. It is a judgment about effort and reliability, not a claim that nothing can be built.
| What the validator caught | Typical rules-based CPQ | Predictika |
|---|---|---|
| A committed usage amount judged against expected usage | Only with workarounds A custom ratio of two entered amounts with block and approval levels on both sides; usage terms are usually outside the product catalog. | The ratio, the review bands and the commit discount are one calculation, returned with the other findings. |
| An add-on that needs a higher edition and its own minimum seats | Only with care Product rules and quantity validation; works, but every add-on adds rules to keep in step with the editions. | The edition level and the add-on minimum are catalog attributes checked together on every call. |
| Named and concurrent seats with different prices | Only with care Price book entries or variants per seat model and a rule for the editions that do not offer concurrent seats. | The seat model selects the price column; availability is a catalog attribute. |
| Volume tiers combined with term and commit discounts | Only with care Tiered price rules plus a term discount and a commit discount applied in a fixed order. | Tier, term discount and commit discount are one calculation. |
| A quoted total that no longer matches | Only with workarounds The total the agent states is a typed number; unless someone adds a recalculation rule it is accepted as is. | The validator computes the total and blocks a quote whose stated total does not match. |
Every rule is checked on every call, in any order the choices arrive; one problem never hides another. Blocking findings stop the quote; approval findings need a person to sign off; everything else is computed.
| 1 | Fewer seats than the minimum for the edition are blocked. |
| 2 | An add-on with fewer seats than its own minimum is blocked. |
| 3 | An add-on that needs a higher edition than the one quoted is blocked. |
| 4 | Concurrent seats on an edition that does not offer them are blocked. |
| 5 | A term other than 1 or 3 years is blocked. |
| 6 | A usage commit with no expected annual usage entered is blocked. |
| 7 | A usage commit below 50 percent of the expected annual usage is blocked. |
| 8 | A discount above the limit for the order size is blocked. |
| 9 | A net total that does not match the total the validator computes is blocked. |
| 10 | A usage commit below 70 percent of expected usage needs deal desk approval. |
| 11 | A usage commit above 120 percent of expected usage needs deal desk confirmation. |
| 12 | A discount above the 10 percent a rep can give needs approval, up to the limit for the order size. |
| 13 | A net order value above USD 1,000,000 needs a sales director review. |
The recorded result of the validator for each scenario on this page: the request the AI agent sent, the verdict, and every finding, in the order they appear above.
The agent's request. Please check this subscription quote for Northwind Health Partners: Cloud CX 2 for 200 named seats on a one year term, with an annual usage commit of USD 60,000 against USD 200,000 of expected usage, at the net total of USD 319,440. It is ready to send.
Verdict: Blocked.
The agent's request. I have raised the usage commit to USD 160,000, which is 80 percent of expected usage, and updated the net total to USD 411,440. Please check it again.
Verdict: Allowed.
The agent's request. Please check this quote for Alder Creek Insurance: Cloud CX 2 with the Workforce Engagement add-on for 20 named seats on a three year term, at the net total of USD 99,360. It is ready to send.
Verdict: Blocked.
The agent's request. I have raised the quote to 25 seats, which meets the add-on minimum, at the net total of USD 124,200. Please check it again.
Verdict: Allowed.
The agent's request. Please check this quote for Harborview Credit Union: Cloud CX 2 with the Digital Messaging add-on for 150 named seats on a three year term, at the net total of USD 588,409.92. It is ready to send.
Verdict: Blocked.
The agent's request. I have corrected the net total to the validator figure of USD 653,788.80 and changed nothing else. Please check it again.
Verdict: Allowed.
The text of the narrated walkthrough, step by step.