Predictika · Mobile plan quotes

An AI sales agent's mobile plan quote, checked before it goes out

An AI sales agent prepares a consumer mobile plan quote of the kind a carrier sends: an eximo, irumo or ahamo plan with a device, discounts and options, in Japanese yen. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of the plan rules, compares the monthly total the quote states with the computed one, and returns every finding together with the monthly total it computed. This is an illustrative model built from public plan information; it is not NTT docomo's internal rule set.

Scope: consumer mobile plan quotes for NTT docomo's eximo, irumo and ahamo plans, with devices, discounts and options, priced in yen. See everything this validator covers

This validator models one product line: consumer mobile plan quotes for eximo, irumo and ahamo, including the device, the discounts and the options on the same quote. It handles any quote that combines these plan, discount and device choices, not only the scenarios shown on this page. It does not cover docomo's business lines, IoT or machine-to-machine contracts, or other carriers' plans.

  • Plan fit — the data cap of each plan tier, the ahamo Oomori option, and call-option eligibility and redundancy.
  • Eligibility — holder age, the online-only channel for ahamo, and the family group limit.
  • Discounts and pricing — fiber, home 5G, electricity and d Card discounts with their eligibility and stacking rules, and the monthly total.
  • Devices — the Kaedoki return program's device eligibility, 24-installment payments, and credit screening above a price threshold.
  • Stated total and release — the monthly total the agent states against the computed total, and the release step, which is accepted only for an allowed quote or an approved one.

Not covered: business, IoT and other carriers' plans, promotions and campaigns, and real docomo price schedules. Other areas can be added. Every price, discount, fee, data cap and rule on this page is an illustrative estimate based on public plan structure, not docomo's data. The validator shows the computed monthly total in its summary; this page has no line-item table.

The AI sales agentBuilds the mobile plan 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

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
Rules that depend on which plan was chosenOnly with care
The age limit, the online-only channel, the call option and the Oomori option each need a rule keyed to the plan, and the list grows with every plan.		The plan and every choice are in one request and checked together on every call.
A fix that moves the plan, so other rules changeOnly with workarounds
Moving from ahamo to eximo drops some rules and brings in others (family discount, Oomori, device payment); a rep fixes one error and meets the next.		Every rule is checked against the whole quote on every call, so what the switch changes shows up in the same answer.
Two discounts that cannot stack, and a device paid on installmentsOnly with care
The set-discount exclusion and the credit-screening threshold each need their own rule, kept in step with the payment choice.		Both are fields of one request and are checked with the payment method on every call.
A stated total that must match the computed totalOnly with workarounds
The total is built from the plan, discounts, options and device, 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 monthly total on every call.
Every problem returned in one answerOnly with workarounds
Rules tend to fire as 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.

    
1Ahamo already includes 5-minute domestic calls; remove the 5-minute call option.
2Ahamo is sold online only; a docomo shop cannot take this application.
3Arrows We2 is not eligible for the Kaedoki return program.
4The docomo Hikari set discount and the home 5G set discount cannot both apply; pick one.
5IPhone 17 256GB at JPY 145,000 on installments needs installment credit screening.
6Stated monthly total does not match: the agent stated JPY 9,791; the validator computes JPY 9,291.
7Galaxy S26 at JPY 130,000 on installments needs installment credit screening.
85 GB expected use exceeds the 3 GB cap of irumo 3GB; choose a larger tier or plan.
9The Oomori 80GB option is only for ahamo, not eximo.
10An ahamo contract holder must be 20 or older; holder age is 19.
11A contract holder must be 18 or older; holder age is 17.
1221 lines exceed the 20-line family group limit.
132 GB expected use exceeds the 0.5 GB cap of irumo 0.5GB; choose a larger tier or plan.
1431 GB expected use exceeds the 30 GB cap of ahamo; choose a larger tier or plan.
15Stated monthly total does not match: the agent stated JPY 7,316; the validator computes JPY 7,315.

  

  

    
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. A 19-year-old's ahamo quote: An ahamo quote for a 19-year-old at a shop, with a 5-minute option, an arrows We2 on the return program, both set discounts and a 22-line family

    
The agent's request. Please quote ahamo with an expected 40 GB a month for a holder aged 19, applied for at a docomo shop, with arrows We2 paid by the Kaedoki return program, in a family group of 22 lines, claiming the fiber discount and the home 5G discount, with the 5-minute call option. The monthly total is JPY 5,454. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Stated monthly total does not match. Stated monthly total does not match: the agent stated JPY 5,454; the validator computes JPY 5,154.
    • 
      
  • Data need above the plan tier. 40 GB expected use exceeds the 30 GB cap of ahamo; choose a larger tier or plan.
    • 
      
  • 5-minute call option on ahamo. Ahamo already includes 5-minute domestic calls; remove the 5-minute call option.
    • 
      
  • ahamo applied for at a shop. Ahamo is sold online only; a docomo shop cannot take this application.
    • 
      
  • ahamo holder under 20. An ahamo contract holder must be 20 or older; holder age is 19.
    • 
      
  • Family group over 20 lines. 22 lines exceed the 20-line family group limit.
    • 
      
  • Return program on an ineligible device. Arrows We2 is not eligible for the Kaedoki return program.
    • 
      
  • Fiber and home 5G set discounts both claimed. The docomo Hikari set discount and the home 5G set discount cannot both apply; pick one.
    • 
    

    
2. A 19-year-old's ahamo quote: The agent resubmits after fixing the errors

    
The agent's request. Please quote eximo with an expected 40 GB a month for a holder aged 19, applied for online, with Google Pixel 10 paid by the Kaedoki return program, in a family group of 4 lines, claiming the fiber discount, with the 5-minute call option. The monthly total is JPY 8,821. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • Price summary. Total JPY 8,821 per month; JPY 0 due today; plan 5,995 and device 2,826 per month.
    • 
    

    
3. Stated total: A family eximo quote with fiber, electricity and d Card discounts and a monthly total that is 500 yen off

    
The agent's request. Please quote eximo with an expected 15 GB a month for a holder aged 42, applied for online, with Google Pixel 10 paid by 24 installments, in a family group of 3 lines, claiming the fiber discount, the electricity discount and the d Card discount. The monthly total is JPY 9,791. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Stated monthly total does not match. Stated monthly total does not match: the agent stated JPY 9,791; the validator computes JPY 9,291.
    • 
    

    
4. Stated total: The agent resubmits after fixing the errors

    
The agent's request. Please quote eximo with an expected 15 GB a month for a holder aged 42, applied for online, with Google Pixel 10 paid by 24 installments, in a family group of 3 lines, claiming the fiber discount, the electricity discount and the d Card discount. The monthly total is JPY 9,291. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • Price summary. Total JPY 9,291 per month; JPY 0 due today; plan 4,708 and device 4,583 per month.
    • 
    

    
5. iPhone with two set discounts: An iPhone 17 on the return program with both set discounts claimed

    
The agent's request. Please quote eximo with an expected 20 GB a month for a holder aged 45, applied for online, with iPhone 17 256GB paid by the Kaedoki return program, claiming the fiber discount and the home 5G discount. The monthly total is JPY 9,910. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Fiber and home 5G set discounts both claimed. The docomo Hikari set discount and the home 5G set discount cannot both apply; pick one.
    • 
      
  • Installment device above the credit-screening price. IPhone 17 256GB at JPY 145,000 on installments needs installment credit screening.
    • 
    

    
6. iPhone with two set discounts: The agent resubmits after fixing the errors

    
The agent's request. Please quote eximo with an expected 20 GB a month for a holder aged 45, applied for online, with iPhone 17 256GB paid by a lump sum, claiming the fiber discount. The monthly total is JPY 6,215. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • Price summary. Total JPY 6,215 per month; JPY 145,000 due today; plan 6,215 and device 0 per month.
    • 
    

    
7. Credit screening: A Galaxy S26 on installments with ahamo, credit screening approved

    
The agent's request. Please quote ahamo with an expected 20 GB a month for a holder aged 25, applied for online, with Galaxy S26 paid by 24 installments. The monthly total is JPY 8,386. It is ready to send.

    
Verdict: Needs approval.

    
    
      
  • Installment device above the credit-screening price. Galaxy S26 at JPY 130,000 on installments needs installment credit screening.
    • 
      
  • Price summary. Total JPY 8,386 per month; JPY 0 due today; plan 2,970 and device 5,416 per month.
    • 
    

  

  

    
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 consumer mobile plan quote of the kind a carrier sends: an eximo, irumo or ahamo plan with a device, discounts and options, and more. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of the plan rules, compares the monthly total the quote states with the computed one, and returns every finding together with the monthly total it computed. This is an illustrative model built from public plan information; it is not NTT docomo's internal rule set.
    2. 
      
  2. Each tab is a different request. We will start with the first one.
    3. 
      
  3. The agent says. Please quote ahamo with an expected 40 GB a month for a holder aged 19, applied for at a docomo shop. The monthly total is JPY 5,454. The rest of the request is on screen.
    4. 
      
  4. Before it goes out, the agent calls the validator.
    5. 
      
  5. Blocked, with eight findings, all in one answer. Stated monthly total does not match: the agent stated JPY 5,454; the validator computes JPY 5,154. 40 GB expected use exceeds the 30 GB cap of ahamo; choose a larger tier or plan. Ahamo already includes 5-minute domestic calls; remove the 5-minute call option. The other five are on screen.
    6. 
      
  6. The validator returned eight 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 a stated total that must match the computed total, a rules-based CPQ can do this only with workarounds.
    8. 
      
  8. Now the agent resubmits.
    9. 
      
  9. The corrected request. It changes the plan to eximo, the applied for to online, the device to Google Pixel 10, the family lines to 4, the home 5G discount to no and the stated monthly total to 8,821.
    10. 
      
  10. It calls the validator again.
    11. 
      
  11. This time the validator clears it.
    12. 
      
  12. All eight earlier findings are cleared.
    13. 
      
  13. Eight 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.
    14.