Predictika · Business ticket quotes

An AI sales agent's Business Tickets quote, checked before it goes out

An AI sales agent prepares a Business Tickets quote for a company with a number of contract lines, with Collaboration, Email, Email Plus, Navigation, Cloud Storage and Social tickets on each line and the total the quote states. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of the contract and ticket rules and returns a verdict, every reason and the totals it computed.

Scope: Vodacom Business Tickets quotes: voice, data and prepaid lines, the Collaboration, Email, Email Plus, Navigation, Cloud Storage and Social tickets, tickets per line and the total the quote states. See everything this validator covers

This validator models Business Tickets quotes, not just the scenarios shown below.

  • Contract and lines — tickets can be added only to a voice or data business contract, not a prepaid line, and the quote needs at least one line.
  • Ticket combinations — a line takes one Collaboration size and one of the two Email tickets, at least one ticket and at most five tickets per line.
  • Totals and approvals — the total the quote states against the total computed from the ticket prices, and a manager review for a large ticket spend or a large number of lines.

Any Business Tickets quote that touches these rules is in scope — not only the scenarios pictured here. Not covered: other Vodacom products, device sales and airtime. The Collaboration, Email, Email Plus and Navigation ticket prices follow Vodacom's public business pages (rand, VAT included); the Cloud Storage and Social tickets, the per-line limits and the approval thresholds are modeled from comparable products and are not published by Vodacom, so those figures are illustrative.

The AI sales agentBuilds the Business Tickets 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
One Collaboration size per lineOnly with care
Four Collaboration sizes exist and a line takes only one, so a rule must count the sizes on each line whichever were added.		The four size counts are fields of one request and are checked together on every call.
Two Email tickets that exclude each otherOnly with care
Email and Email Plus cover the same mail apps, so choosing both is an error that needs its own rule.		Both counts are compared on every call, whatever order they were added in.
A limit on tickets per lineOnly with workarounds
The limit counts tickets of nine kinds across each line, so a rule must add them all up again whenever any count changes.		All nine counts sit in one request, so the per-line total is recomputed on every call.
A stated total that must match the ticket pricesOnly with workarounds
The total is the lines times the prices of every ticket chosen, so a separate rule must recompute it and compare it with the stated figure.		The stated total is a field of the request and is compared with the computed total on every call.
Approvals triggered by a large spend or many linesOnly with workarounds
A manager review depends on a total that moves with every ticket and every line, so the thresholds must be checked against a recomputed figure.		The thresholds are separate findings returned together with the blocking ones.

  

  

    
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.

    
1Business Tickets can be added only to an existing Vodacom Business voice or data contract; a prepaid line does not qualify.
2The quote has 0 lines; at least 1 contract line is needed.
3The quote has no tickets on it; choose at least one ticket per line.
4The quote has 2 different Collaboration ticket sizes on each line; a line takes one Collaboration size.
5Email (1 GB) and Email Plus (2 GB) cover the same mail apps; choose one of them for each line.
6The quote has 6 tickets per line; the limit is 5 tickets per line.
7The quote states R2,500; the ticket prices on it add up to R3,180 including VAT.
8The ticket total of R25,960 is at or above R25,000; a manager should approve it.
9The quote covers 100 lines; orders of 100 or more lines go to a manager for review.
10The quote states R1,000; the ticket prices on it add up to R25,960 including VAT.
11The quote has 3 different Collaboration ticket sizes on each line; a line takes one Collaboration size.

  

  

    
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. Contract, tickets and total: A prepaid quote for 10 lines with two Collaboration sizes, Email, Email Plus, Navigation and Cloud Storage

    
The agent's request. Please quote Business Tickets for 10 prepaid contract lines, with Collaboration 20 GB, Collaboration 50 GB, Email, Email Plus, Navigation and Cloud Storage on each line, for a total of R3,000 including VAT. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Tickets need a Vodacom Business contract. Business Tickets can be added only to an existing Vodacom Business voice or data contract; a prepaid line does not qualify.
    • 
      
  • One Collaboration size per line. The quote has 2 different Collaboration ticket sizes on each line; a line takes one Collaboration size.
    • 
      
  • One Email ticket per line. Email (1 GB) and Email Plus (2 GB) cover the same mail apps; choose one of them for each line.
    • 
      
  • Too many tickets per line. The quote has 6 tickets per line; the limit is 5 tickets per line.
    • 
      
  • Stated total does not match. The quote states R3,000; the ticket prices on it add up to R9,740 including VAT.
    • 
    

    
2. Contract, tickets and total: The agent resubmits after fixing the errors

    
The agent's request. Please quote Business Tickets for 10 voice contract lines, with Collaboration 50 GB, Email Plus and Navigation on each line, for a total of R5,770 including VAT. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • Order summary. 10 line(s), 30 ticket(s) in all, R5,770 including VAT.
    • 
    

    
3. Collaboration, Email and a large order: A 25-line data quote with two Collaboration sizes and both Email tickets

    
The agent's request. Please quote Business Tickets for 25 data contract lines, with Collaboration 50 GB, Collaboration 100 GB, Email and Email Plus on each line, for a total of R20,000 including VAT. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • One Collaboration size per line. The quote has 2 different Collaboration ticket sizes on each line; a line takes one Collaboration size.
    • 
      
  • One Email ticket per line. Email (1 GB) and Email Plus (2 GB) cover the same mail apps; choose one of them for each line.
    • 
      
  • Stated total does not match. The quote states R20,000; the ticket prices on it add up to R29,650 including VAT.
    • 
      
  • Large ticket spend. The ticket total of R29,650 is at or above R25,000; a manager should approve it.
    • 
    

    
4. Collaboration, Email and a large order: The agent resubmits after fixing the errors

    
The agent's request. Please quote Business Tickets for 25 data contract lines, with Collaboration 100 GB and Email Plus on each line, for a total of R18,450 including VAT. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • Order summary. 25 line(s), 50 ticket(s) in all, R18,450 including VAT.
    • 
    

    
5. Spend threshold and stated total: A 40-line voice quote with Collaboration 100 GB and Email

    
The agent's request. Please quote Business Tickets for 40 voice contract lines, with Collaboration 100 GB and Email on each line, for a total of R1,000 including VAT. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Stated total does not match. The quote states R1,000; the ticket prices on it add up to R28,320 including VAT.
    • 
      
  • Large ticket spend. The ticket total of R28,320 is at or above R25,000; a manager should approve it.
    • 
    

    
6. Spend threshold and stated total: The agent resubmits after fixing the errors

    
The agent's request. Please quote Business Tickets for 30 voice contract lines, with Collaboration 100 GB and Email on each line, for a total of R21,240 including VAT. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • Order summary. 30 line(s), 60 ticket(s) in all, R21,240 including VAT.
    • 
    

  

  

    
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 Tickets quote for a company with a number of contract lines, with Collaboration. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of the contract and ticket rules and returns a verdict, every reason and the totals it computed.
    2. 
      
  2. I will start with the first request by the agent.
    3. 
      
  3. The agent says. Please quote Business Tickets for 10 prepaid contract lines, with Collaboration 20 GB, Collaboration 50 GB, Email, Email Plus, Navigation and Cloud Storage on each line. It is ready to send. 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. Business Tickets can be added only to an existing Vodacom Business voice or data contract; a prepaid line does not qualify. The quote has 2 different Collaboration ticket sizes on each line; a line takes one Collaboration size. Email (1 GB) and Email Plus (2 GB) cover the same mail apps; choose one of them for each line. 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 and against the stated total.
    7. 
      
  7. What this shows: for one Collaboration size per line, a rules-based CPQ is error-prone for this.
    8. 
      
  8. Now the agent resubmits.
    9. 
      
  9. The corrected request. It changes the contract type to voice, the Collaboration 20 GB tickets per line to 0, the email tickets per line to 0, the Cloud Storage tickets per line to 0 and the total stated on the quote to 5,770 rand.
    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.