Predictika · Business banking quotes

An AI sales agent's business checking quote, checked before it goes out

An AI sales agent prepares a business checking proposal for a small business: the account, the monthly service fee it will charge, and what the customer is told about included transactions, cash deposits and wires. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of the published account terms and returns a verdict, every reason and the figures it computed.

Scope: Chase Business Complete Banking, Performance Business Checking and Platinum Business Checking proposals: monthly service fee and how it is waived, and the included transactions, cash deposits and wires. See everything this validator covers

This validator models proposals for three Chase business checking accounts as published on the Chase business checking pages, not just the scenarios shown below.

  • Monthly service fee — $15 for Business Complete Banking, $40 for Performance Business Checking and $95 for Platinum Business Checking, and whether it is waived. Business Complete: $2,000 minimum daily ending balance, $2,000 in eligible QuickAccept or Chase Payment Solutions deposits, $2,000 in eligible Chase for Business credit card purchases, a linked Private Client Checking, JPMorgan Classic Checking or Private Client Checking Plus account, or Military Banking. Performance: $35,000 in average beginning day balances in qualifying linked business deposit accounts. Platinum: $100,000, or $50,000 when linked to a Private Client Checking, JPMorgan Classic Checking or Private Client Checking Plus account. The stated fee must equal the computed fee.
  • Included usage — per statement cycle: Business Complete 20 transactions with a banker and $5,000 in-branch cash deposits; Performance 250 debits and deposits with a banker, $20,000 of cash deposits and two outgoing domestic wires; Platinum 500, $25,000 and four outgoing wires. A proposal that promises no extra fees but expects more than the account includes is blocked.
  • Approvals — expected usage beyond the allowance without a no-extra-fees promise goes to a person, because the fee amounts are in a separate fee schedule that is not on the account pages.

Any proposal for these three accounts that touches these rules is in scope — not only the scenarios pictured here. Not covered: other Chase accounts, the amounts of overage, wire and other fees (not on the account pages), interest options, card acceptance and payments products, and promotions. This validator checks account terms only and produces no price build-up or line-item quote. Assumptions: transaction counting follows the wording of each account page, which differs slightly between pages; Business Complete wires are not modeled because its page lists none.

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

7 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

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
A fee that is waived by any one of several conditionsOnly with care
A rule per waiver path; it works, but one account has five paths and another has a combined-balance threshold with a second threshold when a linked account exists.		Every path is evaluated together and the fee the quote should show is computed from them.
A stated fee that has to match the computed feeOnly with care
The rep types the fee; a validation rule can compare it, but only if every waiver rule has already run.		The stated fee is compared with the computed fee in the same pass as every other rule.
Allowances that differ by account: transactions, cash deposits, wiresOnly with workarounds
Three accounts with three allowances each, checked against expected usage, plus a promise made in the proposal text.		The account's allowances are looked up and compared with expected usage, and the promise is one of the inputs.
A fee that applies but is not published on the product pagesOnly with workarounds
There is no price to compute, so the proposal usually goes out with the overage left out.		The overage is recognized and the proposal is held for a person to confirm.
Every problem returned in one answerOnly with workarounds
Rules tend to fire as the quote is saved or a step is completed, so a rep 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 states a monthly service fee of $0; the published terms give $40.
2The quote states a monthly service fee of $0; the published terms give $15.
3Expected usage goes beyond what the account includes; fees apply, but their amounts are in a separate fee schedule that is not on the account pages, so a person should confirm them.
4The quote promises no extra fees but the customer expects 21 transactions a statement cycle; the account includes 20.
5The quote promises no extra fees but the customer expects $20,001 of in-branch cash deposits a statement cycle; the account includes 20,000.
6The quote promises no extra fees but the customer expects 5 outgoing wires a statement cycle; the account includes 4.
7The quote promises no extra fees but the customer expects 300 transactions a statement cycle; the account includes 250.
8The quote promises no extra fees but the customer expects $30,000 of in-branch cash deposits a statement cycle; the account includes 20,000.
9The quote promises no extra fees but the customer expects 5 outgoing wires a statement cycle; the account includes 2.

  

  

    
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 business checking proposal for a small business: the account, the monthly service fee it will charge, what the customer is told about included transactions, and more. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of the published account terms and returns a verdict, every reason and the figures it computed.
    2. 
      
  2. I will start with the first request by the agent.
    3. 
      
  3. The agent says. Please set up Chase Business Complete Banking for a business with a minimum daily ending balance of $3,500. It expects 35 transactions with a banker, $8,000 in in-branch cash deposits each statement cycle. The rest of the request is on screen. The quote states a monthly service fee of $0.
    4. 
      
  4. Before it goes out, the agent calls the validator.
    5. 
      
  5. Blocked, with two findings, all in one answer. The quote promises no extra fees but the customer expects 35 transactions a statement cycle; the account includes 20. The quote promises no extra fees but the customer expects $8,000 of in-branch cash deposits a statement cycle; the account includes 5,000.
    6. 
      
  6. The validator returned two 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 allowances that differ by account: transactions, cash deposits, wires, a rules-based CPQ can do this only with workarounds.
    8. 
      
  8. Now the agent resubmits.
    9. 
      
  9. The corrected request. It changes the promise of no extra fees to no.
    10. 
      
  10. It calls the validator again.
    11. 
      
  11. Not blocked, but held for a person.
    12. 
      
  12. The two blocking findings are cleared; one approval remains for a person: fees on usage above the allowance to confirm.
    13. 
      
  13. Two problems caught in one call, fixed in one pass, and the corrected quote now goes to a person for approval. That is the value of Predictika's validator: catching mistakes before they reach the customer.
    14.