Predictika · Managed SD-WAN service quotes

An AI sales agent's Smart Connectivity quote, checked before it goes out

An AI sales agent prepares a quote for a managed SD-WAN and security service: a plan (SC or SC Pro), a device, the number of sites, links per site and client VPNs, threat profiles and traffic rules, included changes, log retention, speed and the availability promised. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of the service rules and returns a verdict and every reason.

Scope: Liberty Networks Smart Connectivity quotes (SC and SC Pro): site and VPN limits, plan limits on profiles, rules, changes and log retention, device speed, links per site, load balancing, availability and the stated link total. See everything this validator covers

This validator models Smart Connectivity quotes of this kind, not just the scenarios shown below.

  • Service limits — up to 10 sites and 100 client-to-site VPNs, and what each plan allows in threat profiles, traffic rules, included changes a month and months of logs.
  • Devices and links — the speed each device supports, up to two links per site, load balancing that needs more than one link, and the availability the service can promise.
  • Totals and review — the links in total compared with the total the quote states, and a person’s review of customer-supplied circuits and large VPN counts.

Any Smart Connectivity quote that touches these rules is in scope — not only the scenarios pictured here. The SC and SC Pro plans, the 10 sites, 100 client VPNs, three threat profiles and six traffic rules in SC Pro, the included changes, one year of logs in SC Pro, fiber and GPON speeds up to 150 Mbps, two links per site, the SLA up to 99.6 percent, load balancing and customer-supplied circuits follow Liberty Networks’ public Smart Connectivity page; the SC limits on profiles, rules and logs, the MX67 and MX85 devices, the MX64 speed cap and the review thresholds are modeled and not published by Liberty Networks. Not covered: prices (none are modeled, so this page shows no price build-up), other services, installation and support terms.

The AI sales agentBuilds the Smart Connectivity quote from the conversation and says it is ready.
Predictika validatorChecks every rule at once and returns the verdict, each finding, and the computed figures.

6 scenarios in 3 groups · each group runs from the agent’s first attempt to the outcome · click one to switch

What the agent proposes

The AI sales agent says

Illustrative agent statement. The validator receives the structured request below.

Proposing agent: AI sales agent (scripted)

Before sending, the agent must call Recorded run

Predictika validator


      

        
        
        
      

      
Waiting for the call.

      
    

  

  
  

    
Where rules-based CPQ gets it wrong
Click to expand
    
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 caughtTypical rules-based CPQPredictika
Limits that differ by planOnly with care
SC and SC Pro allow different profiles, rules, changes and log months, so each limit needs its own rule against the plan chosen.		The plan and every setting are checked together on every call.
Speed that depends on the deviceOnly with care
Each device supports a different speed, so the rule must look up the device before it compares the speed asked for.		The device and the speed are fields of one request and are checked together.
A link total built from sites and links per siteOnly with workarounds
The total is the sites multiplied by the links per site, so a rule must compute it before comparing it with the total the quote states.		The total is computed on every call and compared with the stated total.
Options that need other choicesOnly with workarounds
Load balancing needs more than one link and a customer-supplied circuit needs a person’s review, so rules must look across several choices at once.		All choices are in one request and are compared on every call.
Every problem returned in one answerOnly with workarounds
Rules tend to fire as a step is saved or completed, so a person often fixes one error and meets the next.		All findings come back together, whatever order the choices arrived in.

  

  

    
What this validator catches: findings from its test cases
Click to expand
    
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.

    
1The quote has 11 sites; the service supports up to 10.
2The quote has 101 client-to-site VPNs; the service supports up to 100.
390 client-to-site VPNs is close to the service limit; a person should confirm capacity.
4The quote has 3 threat protection profiles; this plan allows 1.
5The quote has 4 threat protection profiles; this plan allows 3.
6The quote has 3 custom traffic rules; this plan allows 2.
7The quote has 7 custom traffic rules; this plan allows 6.
8The customer expects 3 included changes a month; this plan includes 2.
9The customer needs 12 months of log retention; this plan keeps 3.
10The quote asks for 120 Mbps; this device supports 100 Mbps (service maximum 150).
11The quote asks for 151 Mbps; this device supports 150 Mbps (service maximum 150).
12The quote has 3 links per site; the service supports up to 2.
13Load balancing needs at least 2 WAN links per site; the quote has 1.
14The quote promises availability of 999 tenths of a percent; the service SLA is up to 996 (99.6%).
15The quote states 8 links in total; the sites and links per site give 10.
16The quote uses a customer-supplied (BYOC) circuit; a person should confirm the third-party link is suitable.

  

  

    
Scenarios and results
Click to expand
    
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.

    
1. Plan limits and site count: A basic SC plan for 12 sites with Pro-level profiles, rules, changes and log retention

    
The agent's request. Please quote the SC plan for 12 sites with 2 links per site, on MX84 devices at 100 Mbps and 40 client VPNs. The quote lists 3 threat protection profiles, 5 custom traffic rules, 4 included changes a month and 12 months of log retention. It promises availability of 99.6 percent and states 24 links in total. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Too many sites. The quote has 12 sites; the service supports up to 10.
    • 
      
  • Threat profiles over plan. The quote has 3 threat protection profiles; this plan allows 1.
    • 
      
  • Traffic rules over plan. The quote has 5 custom traffic rules; this plan allows 2.
    • 
      
  • Changes per month over plan. The customer expects 4 included changes a month; this plan includes 2.
    • 
      
  • Log retention over plan. The customer needs 12 months of log retention; this plan keeps 3.
    • 
    

    
2. Plan limits and site count: The agent resubmits after fixing the errors

    
The agent's request. Please quote the SC Pro plan for 10 sites with 2 links per site, on MX84 devices at 100 Mbps and 40 client VPNs. The quote lists 3 threat protection profiles, 5 custom traffic rules, 4 included changes a month and 12 months of log retention. It promises availability of 99.6 percent and states 20 links in total. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • Service summary. 10 site(s), 20 link(s) in total, up to 100 Mbps, 4 changes a month included.
    • 
    

    
3. Device speed, links and availability: Five sites on MX64 devices at 140 Mbps with three links per site, 99.9 percent availability and the wrong link total

    
The agent's request. Please quote the SC Pro plan for 5 sites with 3 links per site, on MX64 devices at 140 Mbps and 40 client VPNs. The quote lists 3 threat protection profiles, 5 custom traffic rules, 4 included changes a month and 12 months of log retention, with load balancing. It promises availability of 99.9 percent and states 8 links in total. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Speed over device or service limit. The quote asks for 140 Mbps; this device supports 100 Mbps (service maximum 150).
    • 
      
  • More than two links per site. The quote has 3 links per site; the service supports up to 2.
    • 
      
  • Availability over service maximum. The quote promises availability of 999 tenths of a percent; the service SLA is up to 996 (99.6%).
    • 
      
  • Stated link total does not match. The quote states 8 links in total; the sites and links per site give 15.
    • 
    

    
4. Device speed, links and availability: The agent resubmits after fixing the errors

    
The agent's request. Please quote the SC Pro plan for 5 sites with 2 links per site, on MX84 devices at 140 Mbps and 40 client VPNs. The quote lists 3 threat protection profiles, 5 custom traffic rules, 4 included changes a month and 12 months of log retention, with load balancing. It promises availability of 99.6 percent and states 10 links in total. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • Service summary. 5 site(s), 10 link(s) in total, up to 140 Mbps, 4 changes a month included.
    • 
    

    
5. Load balancing and VPNs: Load balancing on one link, too many client VPNs and a customer-supplied circuit

    
The agent's request. Please quote the SC Pro plan for 5 sites with 1 links per site, on MX84 devices at 100 Mbps and 120 client VPNs. The quote lists 3 threat protection profiles, 5 custom traffic rules, 4 included changes a month and 12 months of log retention, with load balancing and a customer-supplied circuit. It promises availability of 99.6 percent and states 5 links in total. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Too many client VPNs. The quote has 120 client-to-site VPNs; the service supports up to 100.
    • 
      
  • Load balancing needs multiple links. Load balancing needs at least 2 WAN links per site; the quote has 1.
    • 
      
  • Third-party circuit to review. The quote uses a customer-supplied (BYOC) circuit; a person should confirm the third-party link is suitable.
    • 
    

    
6. Load balancing and VPNs: The agent resubmits after fixing the errors

    
The agent's request. Please quote the SC Pro plan for 5 sites with 2 links per site, on MX84 devices at 100 Mbps and 70 client VPNs. The quote lists 3 threat protection profiles, 5 custom traffic rules, 4 included changes a month and 12 months of log retention, with load balancing. It promises availability of 99.6 percent and states 10 links in total. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • Service summary. 5 site(s), 10 link(s) in total, up to 100 Mbps, 4 changes a month included.
    • 
    

  

  

    
Narration transcript
Click to expand
    
The text of the narrated walkthrough, step by step.

    
    
      
  1. Welcome to a demo of Predictika's Validator. An AI sales agent prepares a quote for a managed SD-WAN and security service: a plan (SC or SC Pro), a device, the number of sites, and more. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of the service rules and returns a verdict and every reason.
    2. 
      
  2. I will start with the first request by the agent.
    3. 
      
  3. The agent says. Please quote the SC plan for 12 sites with 2 links per site, on MX84 devices at 100 Mbps and 40 client VPNs. The quote lists 3 threat protection profiles, 5 custom traffic rules, 4 included changes a month and 12 months of log retention. The rest of the request is on screen.
    4. 
      
  4. Before it goes out, the agent calls the validator.
    5. 
      
  5. Blocked, with five findings, all in one answer. The quote has 12 sites; the service supports up to 10. The quote has 3 threat protection profiles; this plan allows 1. The quote has 5 custom traffic rules; this plan allows 2. The other two are on screen.
    6. 
      
  6. The validator returned five blocking findings in one answer. A check that reads one field at a time would pass most of this; it shows only when the choices in the quote are checked against each other.
    7. 
      
  7. What this shows: for limits that differ by plan, a rules-based CPQ is error-prone for this.
    8. 
      
  8. Now the agent resubmits.
    9. 
      
  9. The corrected request. It changes the plan to SC Pro, the sites to 10 and the stated total links to 20.
    10. 
      
  10. It calls the validator again.
    11. 
      
  11. This time the validator clears it.
    12. 
      
  12. All five earlier findings are cleared.
    13. 
      
  13. Five problems caught in one call, fixed in one pass, and a clean quote. That is the value of Predictika's validator: catching mistakes before they reach the customer. Now you can try the other scenarios yourself.
    14.