Predictika · IoT connectivity quotes

An AI sales agent's IoT connectivity quote, checked before it goes out

An AI sales agent prepares a monthly quote for a business that wants LTE and LPWA lines on KDDI IoT Access, with text messages and one-time fees. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of the published rate table and contract terms and returns a verdict, every reason, a line-item quote and the figures it computed.

Scope: KDDI IoT Access quotes: LTE and LPWA plans, included data and overage, SMS, contract and transfer fees, plan-type and total checks. See everything this validator covers

This validator models monthly quotes for KDDI IoT Access (IoT access communication service) as published in KDDI's contract terms (5th edition, July 31, 2026), not just the scenarios shown below.

  • Plans and usage — LTE plans (metered, 30 MB or 500 MB included) and LPWA plans (metered, 100 KB, 1,000 KB or 1,500 KB included), a monthly charge per line, and an overage charge per MB or KB beyond the included amount. Plan types cannot be swapped between line types.
  • Messages and one-time fees — SMS to the device at ¥0.75 and from the device at ¥60 each, a contract fee of ¥900 for a new contract, and a transfer fee of ¥3,000 plus ¥270 a line.
  • Totals and approvals — the recurring charge is rounded up to a whole yen, and a stated total must equal the computed one. Optional features and paper invoices have charges that are not in the rate table, so they go to a person.

Any KDDI IoT Access quote that touches these rules is in scope — not only the scenarios pictured here. Not covered: the solution-bundled plan, optional features priced under SORACOM terms, the paper-invoice fee, the renewal fee, device prices, first-month proration, consumption tax, and negotiated or volume pricing. Assumptions: the included data allowance is applied per line, and the contract fee is charged once per contract.

The AI sales agentBuilds the IoT 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.

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

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
A plan type that must match the line typeOnly with workarounds
LTE and LPWA plans are separate products, so a rule has to tie each plan to its line group; a mismatch is easy to miss when a rep copies a plan across lines.		Both plan types and both line counts are in one request and checked together.
Included data with an overage rateOnly with care
Each plan has its own allowance and overage rate in a table; a price rule per plan has to be kept in step with the rate card.		The allowance and rate come from the plan, and the overage is computed on every call.
Rounding the recurring charge up to a whole yenOnly with care
Per-unit rates in fractions of a yen add up across thousands of lines; a rounding rule has to be added by hand.		The total is built in hundredths of a yen and rounded up, and the quote shows the rounding line.
One-time fees that depend on the orderOnly with care
A contract fee and a transfer fee with a per-line part sit outside the monthly price rules.		One-time fees are computed with the monthly charge and shown on the quote.
Stated totals that must equal the computed totalOnly with workarounds
A stated figure is a free-entry field; a rule can compare it, but the computed total depends on plans, overage, messages and fees.		The stated total travels with the quote and is compared with the computed total on every call.
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 has no KDDI IoT Access lines; at least 1 is needed.
2The quote has 10 LTE lines but no LTE plan.
3The quote has 10 LPWA lines but no LPWA plan.
4An LTE plan is selected but the quote has no LTE lines.
5An LPWA plan is selected but the quote has no LPWA lines.
6The plan selected for the LTE lines is an LPWA plan; LTE lines take the LTE plans (metered, 30 MB or 500 MB included).
7The plan selected for the LPWA lines is an LTE plan; LPWA lines take the LPWA plans (metered, 100 KB, 1,000 KB or 1,500 KB included).
8The quote contains a negative data volume, message count or line count.
9The quote states a total of ¥192,899; the rates in the KDDI terms give ¥192,900, excluding consumption tax.
10The quote states a total of ¥192,901; the rates in the KDDI terms give ¥192,900, excluding consumption tax.
11The quote states a total of ¥192,000; the rates in the KDDI terms give ¥192,900, excluding consumption tax.
12The quote includes optional line features; their charges are set by the SORACOM terms that KDDI refers to and are not in the rate table, so a person should confirm them.
13The quote asks for paper invoices; the terms say a separate invoice fee applies but do not give the amount, so a person should confirm it.
14The quote states a total of ¥1,000; the rates in the KDDI terms give ¥192,900, excluding consumption tax.

  

  

    
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. Smart-meter lines on the wrong plan type: LTE and LPWA lines, with an LTE plan chosen for the LPWA smart-meter lines

    
The agent's request. Please quote KDDI IoT Access for 800 LTE lines on the LTE 30 MB included plan using 38 MB a line a month and 4,000 LPWA lines on the LTE 500 MB included plan using 900 KB a line a month, with 1,500 text messages to the devices and 120 from them a month, a new contract. The quote states a total of ¥3,118,985. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • LTE plan on LPWA lines. The plan selected for the LPWA lines is an LTE plan; LPWA lines take the LPWA plans (metered, 100 KB, 1,000 KB or 1,500 KB included).
    • 
    

    
2. Smart-meter lines on the wrong plan type: The agent resubmits after fixing the errors

    
The agent's request. Please quote KDDI IoT Access for 800 LTE lines on the LTE 30 MB included plan using 38 MB a line a month and 4,000 LPWA lines on the LPWA 1,000 KB included plan using 900 KB a line a month, with 1,500 text messages to the devices and 120 from them a month, a new contract. The quote states a total of ¥1,118,985. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • Quote summary. 4800 line(s); recurring charges of ¥1,118,085 a month and one-time fees of ¥900, ¥1,118,985 in total excluding consumption tax.
    • 
    

    
3. The total and the one-time fees: A large quote with a transfer, whose stated total leaves out the one-time fees

    
The agent's request. Please quote KDDI IoT Access for 600 LTE lines on the LTE 500 MB included plan using 650 MB a line a month and 3,000 LPWA lines on the LPWA 1,500 KB included plan using 1,700 KB a line a month, with 2,500 text messages to the devices and 150 from them a month, a new contract, and 25 lines transferred in. The quote states a total of ¥1,355,775. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Stated total does not match. The quote states a total of ¥1,355,775; the rates in the KDDI terms give ¥1,365,525, excluding consumption tax.
    • 
    

    
4. The total and the one-time fees: The agent resubmits after fixing the errors

    
The agent's request. Please quote KDDI IoT Access for 600 LTE lines on the LTE 500 MB included plan using 650 MB a line a month and 3,000 LPWA lines on the LPWA 1,500 KB included plan using 1,700 KB a line a month, with 2,500 text messages to the devices and 150 from them a month, a new contract, and 25 lines transferred in. The quote states a total of ¥1,365,525. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • Quote summary. 3600 line(s); recurring charges of ¥1,354,875 a month and one-time fees of ¥10,650, ¥1,365,525 in total excluding consumption tax.
    • 
    

    
5. Plan, optional features and invoices: LPWA lines with no plan, plus optional features and paper invoices

    
The agent's request. Please quote KDDI IoT Access for 1,500 LTE lines on the LTE 30 MB included plan using 34 MB a line a month and 6,000 LPWA lines on the none plan using 140 KB a line a month, with 3,000 text messages to the devices and 200 from them a month, a new contract, with optional line features, and paper invoices. The quote states a total of ¥290,550. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • LPWA lines without a plan. The quote has 6000 LPWA lines but no LPWA plan.
    • 
      
  • Optional features to confirm. The quote includes optional line features; their charges are set by the SORACOM terms that KDDI refers to and are not in the rate table, so a person should confirm them.
    • 
      
  • Paper invoice fee to confirm. The quote asks for paper invoices; the terms say a separate invoice fee applies but do not give the amount, so a person should confirm it.
    • 
    

    
6. Plan, optional features and invoices: The agent resubmits after fixing the errors

    
The agent's request. Please quote KDDI IoT Access for 1,500 LTE lines on the LTE 30 MB included plan using 34 MB a line a month and 6,000 LPWA lines on the LPWA 100 KB included plan using 140 KB a line a month, with 3,000 text messages to the devices and 200 from them a month, a new contract, with optional line features, and paper invoices. The quote states a total of ¥1,286,550. It is ready to send.

    
Verdict: Needs approval.

    
    
      
  • Optional features to confirm. The quote includes optional line features; their charges are set by the SORACOM terms that KDDI refers to and are not in the rate table, so a person should confirm them.
    • 
      
  • Paper invoice fee to confirm. The quote asks for paper invoices; the terms say a separate invoice fee applies but do not give the amount, so a person should confirm it.
    • 
      
  • Quote summary. 7500 line(s); recurring charges of ¥1,285,650 a month and one-time fees of ¥900, ¥1,286,550 in total excluding consumption tax.
    • 
    

    
7. Plan, optional features and invoices: The agent resubmits after fixing the errors

    
The agent's request. Please quote KDDI IoT Access for 1,500 LTE lines on the LTE 30 MB included plan using 34 MB a line a month and 6,000 LPWA lines on the LPWA 100 KB included plan using 140 KB a line a month, with 3,000 text messages to the devices and 200 from them a month, a new contract. The quote states a total of ¥1,286,550. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • Quote summary. 7500 line(s); recurring charges of ¥1,285,650 a month and one-time fees of ¥900, ¥1,286,550 in total excluding consumption tax.
    • 
    

  

  

    
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 monthly quote for a business that wants LTE and LPWA lines on KDDI IoT Access, with text messages and one-time fees. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of the published rate table and contract terms and returns a verdict, every reason, a line-item quote and the figures it computed.
    2. 
      
  2. I will start with the first request by the agent.
    3. 
      
  3. The agent says. Please quote KDDI IoT Access for 1,500 LTE lines on the LTE 30 MB included plan using 34 MB a line a month and 6,000 LPWA lines on the none plan using 140 KB a line a month. The quote states a total of ¥290,550. The rest of the request is on screen.
    4. 
      
  4. Before it goes out, the agent calls the validator.
    5. 
      
  5. Blocked, with one finding and two approvals, all in one answer. The quote has 6000 LPWA lines but no LPWA plan.
    6. 
      
  6. The validator returned one blocking finding and two approvals 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 a plan type that must match the line type, a rules-based CPQ can do this only with workarounds.
    8. 
      
  8. Now the agent resubmits.
    9. 
      
  9. The corrected request. It changes the LPWA plan to LPWA 100 KB included and the stated total to ¥1,286,550.
    10. 
      
  10. It calls the validator again.
    11. 
      
  11. Not blocked, but held for a person.
    12. 
      
  12. The validator also returns the line-item quote. It starts with LTE plan: 30 MB included and LTE data beyond the included amount (4 MB over; the other five lines are on screen.
    13. 
      
  13. The one blocking finding is cleared; two approvals remain for a person: optional features to confirm and paper invoice fee to confirm.
    14. 
      
  14. The agent resubmits once more.
    15. 
      
  15. The revised request. It changes the optional features requested to no and the paper invoices to no.
    16. 
      
  16. It calls the validator once more.
    17. 
      
  17. This time the validator clears it.
    18. 
      
  18. The validator also returns the line-item quote. It starts with LTE plan: 30 MB included and LTE data beyond the included amount (4 MB over; the other five lines are on screen.
    19. 
      
  19. Both earlier findings are cleared, and the validator's figure matches the quote.
    20. 
      
  20. Three problems caught in one call, fixed in two passes, 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.
    21.