Predictika · Campus Switch Quote Check
Halvern Networks, a fictional network equipment vendor, lets an AI sales agent put together quotes for its Orrin and Tarn switches. Before the agent sends one, the call goes to Predictika’s Campus Switch Quote Check. It checks that the uplink module, power supplies and stack size fit the switch, that the power budget holds, that the tier covers the features, that the term, support level, lead time and discounts are allowed, and that the total the agent stated matches the one computed from the line items. Then it returns one verdict: allow, needs approval, or block.
Illustrative only. Halvern Networks and its customers are fictional. Product names, prices, lead times and discount limits are invented for this demonstration.
This validator decides one thing: whether one quote may be sent, given what is in it. It is not a pricing system, and it does not know the customer.
Within these rules the validator handles any combination of the listed choices, not just the seven scenarios on this page. It never sees the customer, the contract or the order system; those facts are taken as stated.
The validator takes the quote as inputs: the switch, uplink module, power supplies, support level, tier, site, layout, term, delivery date, discounts and the total the agent stated. It looks up the part details in the catalog, computes the line items and the total, and applies the rules.
Two honest limits. The validator judges the quote it is given: if the agent gets a fact about the customer wrong, the answer follows it. And a quote that never calls the validator is not checked; in this demo the agent calls it itself, and in a deployment the quoting workflow makes the call.
7 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 agent (scripted)
Before sending, the agent must call Recorded run
What this means
General statements about quoting tools, not about any named product. We rest this on public descriptions of how such tools work; anyone running a specific product will know it better than we do.
| What the validator caught | Typical tool | Predictika |
|---|---|---|
| Fitting each part to the switch family | Cannot do it Quoting tools look parts up in a catalog. Blocking an uplink module, a power supply or a stack size that does not fit the chosen switch takes a rule that reads them together. | Every rule is checked on every call and the verdict lists each finding. |
| Power budget: system plus PoE against the supplies, in redundant or combined mode | Only if someone is vigilant A catalog lists watts per supply. Whether the supplies carry what the order needs, in the mode chosen, has to be computed for each order. | Every rule is checked on every call and the verdict lists each finding. |
| Checking the agent’s stated total against the computed one | Only with workarounds Many tools show a total. Recomputing it from the line items and comparing it to what the agent stated needs a rule that does both. | Every rule is checked on every call and the verdict lists each finding. |
| Separating blocked discounts from discounts that only need approval | Only if someone is vigilant Approval workflows record who approved. Knowing whether a discount is blocked, or only above what a rep may give alone, has to be added. | Every rule is checked on every call and the verdict lists each finding. |
| Uplink module for the wrong switch family | Only with workarounds Catalog lookups confirm that each part exists. Whether the parts fit this switch, and whether the supplies carry the power the order needs, takes a rule that reads them together. | Every rule is checked on every call and the verdict lists each finding. |
| Link Pair needs the Premier tier | Only if someone is vigilant Tier requirements sit in a data sheet. A rule has to read the layout, the feature and the tier together. | Every rule is checked on every call and the verdict lists each finding. |
| Wrong number of power supplies | Only if someone is vigilant Most tools stop at the first failing check. Returning every finding together takes a rule set designed to do that. | Every rule is checked on every call and the verdict lists each finding. |
| 2-hour care at a remote site | Only if someone is vigilant Support levels depend on the site, and lead times depend on the model. Neither shows up as a typo. | Every rule is checked on every call and the verdict lists each finding. |
Every rule is checked on every call, in any order the choices arrive; one problem never hides another. Blocking findings stop the request; approval findings need a person to sign off first.
| 1 | Uplink module Orrin UM-8X does not fit Orrin 3-48HX; Orrin 3 switches take UX modules and Orrin 2 switches take UM modules. |
| 2 | Orrin 2-48P has modular uplinks and ships with none; add an uplink module. |
| 3 | Orrin 2L-48P has fixed uplinks and takes no uplink module; remove Orrin UM-4G. |
| 4 | Power supply TC-600W does not fit Orrin 2-24T; Orrin switches take OA supplies and Tarn switches take TC supplies. |
| 5 | 1 power supplies per switch is not valid; use 1 or 2, and redundant power needs 2. |
| 6 | 100 W of PoE per switch was requested but Orrin 2-24T is not a PoE model. |
| 7 | Each switch needs 1280 W (system plus PoE) but the power supplies provide 1000 W in this mode. |
| 8 | A stack of 7 exceeds the 6 switch maximum for Orrin 2-24T. |
| 9 | A Link Pair on the Tarn core switches requires the Premier subscription tier. |
| 10 | Fabric automation requires the Premier subscription tier. |
| 11 | A subscription term of 2 years is not offered; choose 1, 3 or 5 years. |
| 12 | 2-hour onsite care is not available at remote sites; choose 4-hour onsite or next-business-day. |
| 13 | The Orrin 3-48HX lead time is about 14 weeks; the customer needs it in 6. |
| 14 | A hardware discount of 44.0 percent is above the ceiling of 40.0 percent without deal registration and 48.0 percent with it. |
| 15 | A subscription discount of 21.0 percent is above the 20.0 percent cap. |
| 16 | Stated total does not match: the agent stated $67535.2; the validator computes $62535.2. |
| 17 | The quote has no CareLine support; a support waiver is required. |
| 18 | A hardware discount of 45.0 percent is above the 30.0 percent a rep may give alone. |
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. I'm sending this quote to Pinegate Clinics: two stacks of four switches with redundant supplies and a 28 percent discount. The parts are all from the same catalog, so it should fit.
Verdict: Blocked.
The agent's request. I'm sending the same quote with the right module and larger supplies: two stacks of four switches, a 28 percent discount.
Verdict: Allowed.
The agent's request. I'm sending this quote to Ironbridge Freight: two stacks of two switches with fabric automation and a 22 percent discount, all on the Base tier to keep the price down.
Verdict: Blocked.
The agent's request. I'm sending the same quote on the Premier tier: two stacks of two switches with fabric automation and a 22 percent discount.
Verdict: Allowed.
The agent's request. I'm sending this quote to Alder Valley Schools: three stacks of four switches, redundant power, a 2 year term and a 44 percent discount to win the school year.
Verdict: Blocked.
The agent's request. I'm sending the quote again with two supplies per switch, a 3 year term and a registered deal at 45 percent.
Verdict: Needs approval.
The agent's request. I'm sending this quote to Marlow Textiles: three switches at their remote mills with two-hour onsite care, an 18 percent discount, and they need them in 6 weeks.
Verdict: Blocked.
The text of the narrated walkthrough, step by step.