Predictika · Messaging quotes

An AI sales agent's US messaging quote, checked before it goes out

An AI sales agent prepares a monthly quote for sending text and picture messages in the United States: the sender type, A2P 10DLC registration, carrier volumes and any short codes. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of the published rates and rules and returns a verdict, every reason, a line-item quote and the figures it computed.

Scope: US outbound SMS and MMS quotes from local 10DLC numbers, toll-free numbers or short codes, with carrier surcharges, 10DLC campaign fees, short code leases and numbers per campaign. See everything this validator covers

This validator models monthly US outbound messaging quotes built on the rates and rules Bandwidth publishes, not just the scenarios shown below.

  • Rates and surcharges — the per-message rate by sender type (10DLC, short code or toll-free) and message type (SMS or MMS), plus the carrier surcharge for AT&T, T-Mobile, Verizon and U.S. Cellular, added into a line-item quote and compared with the total the agent states.
  • Registration and numbers — a 10DLC sender needs a brand and campaign registration (standard or low-volume; sole proprietor campaigns are not supported through Bandwidth), toll-free numbers and short codes do not use one, and a campaign that sends to T-Mobile is limited to 49 numbers unless a number pool request has been approved.
  • Short codes and discounts — random and vanity short code monthly leases are priced per code. A volume discount goes to a person, because its terms are not published.

Any US outbound SMS or MMS quote that touches these rules is in scope — not only the scenarios pictured here. Not covered: voice, authentication and other API products, carriers other than the four above, inbound messages, messages of more than one segment, number rental fees (not published on the pages read), one-time registration and short code carrier set-up fees, Bandwidth-side registration pricing, throughput limits, other countries and taxes. Assumptions: the surcharge and per-message rate apply to each outbound message, the 10DLC campaign monthly fee is the Campaign Service Provider route rate, and the totals are list-rate estimates.

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

8 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
Stated monthly totals that must equal what the published rates giveOnly with care
A stated figure is a free-entry field; a rule can compare it with a computed total, but the total depends on the carrier mix, message type and leases that have to be kept in step with the price pages.		The stated total travels with the quote and is compared with the computed total on every call.
Carrier surcharges that differ by carrier, message type and sender typeOnly with care
A price rule per carrier, message type and sender type. It works, but every change a carrier announces is another rule to maintain.		The surcharges are looked up from the sender and message type and each carrier line is priced and totaled together.
Registration that depends on the sender typeOnly with care
A rule that needs a registration for one sender type and rejects it for the others, plus a campaign type that is not supported.		The sender type, registration and campaign type are in one request and are checked with the rest.
A numbers-per-campaign limit that applies only when traffic goes to T-Mobile and no number pool is approvedOnly with workarounds
The limit depends on a count on one line, a volume on another and an approval flag on a third, so it needs a cross-line rule that interacts with the others.		The count, the T-Mobile volume and the number pool flag are in one request and the limit is checked with the rest.
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 sends from local 10DLC numbers but has no A2P 10DLC brand and campaign registration; unregistered traffic is being blocked.
2Sole proprietor campaigns are not supported through Bandwidth.
3A2P 10DLC registration applies to local 10DLC numbers only; it is quoted here with a toll-free number or short code.
4The quote has 0 sending numbers; at least 1 is needed.
5The quote has 0 thousand outbound messages a month; at least 1 thousand is needed.
6The quote puts 50 numbers on a campaign that sends to T-Mobile; the limit is 49 numbers unless a number pool request has been approved.
7The quote states a monthly total of $2,519.00; the list rates give $2,520.00.
8A volume-based discount is available from Bandwidth but its terms are not published; a person should confirm it.

  

  

    
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. Registration and numbers per campaign: Local 10DLC quote with no registration and 60 numbers on one campaign

    
The agent's request. Please quote monthly US outbound SMS messaging from 60 local 10DLC numbers, with monthly volumes of 300 thousand to AT&T, 250 thousand to T-Mobile, 300 thousand to Verizon and 20 thousand to U.S. Cellular subscribers. The quote states a monthly total of $7,255.00. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • 10DLC needs registration. The quote sends from local 10DLC numbers but has no A2P 10DLC brand and campaign registration; unregistered traffic is being blocked.
    • 
    

    
2. Registration and numbers per campaign: The agent resubmits after fixing the errors

    
The agent's request. Please quote monthly US outbound SMS messaging from 60 local 10DLC numbers under a standard A2P 10DLC brand and campaign registration, with monthly volumes of 300 thousand to AT&T, 250 thousand to T-Mobile, 300 thousand to Verizon and 20 thousand to U.S. Cellular subscribers. The quote states a monthly total of $7,265.00. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Too many numbers on a campaign. The quote puts 60 numbers on a campaign that sends to T-Mobile; the limit is 49 numbers unless a number pool request has been approved.
    • 
    

    
3. Registration and numbers per campaign: The agent resubmits after fixing the errors

    
The agent's request. Please quote monthly US outbound SMS messaging from 60 local 10DLC numbers under a standard A2P 10DLC brand and campaign registration, with monthly volumes of 300 thousand to AT&T, 250 thousand to T-Mobile, 300 thousand to Verizon and 20 thousand to U.S. Cellular subscribers. A number pool request has been approved for the campaign. The quote states a monthly total of $7,265.00. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • Order summary. 870,000 outbound messages a month, estimated monthly total of $7,265.00 at list rates.
    • 
    

    
4. Short code lease and stated total: Short code MMS quote with a stated total that leaves out the lease

    
The agent's request. Please quote monthly US outbound MMS messaging from 2 vanity short codes, with monthly volumes of 150 thousand to AT&T, 120 thousand to T-Mobile, 150 thousand to Verizon and 10 thousand to U.S. Cellular subscribers. The quote states a monthly total of $12,300.00. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Stated total does not match. The quote states a monthly total of $12,300.00; the list rates give $14,300.00.
    • 
    

    
5. Short code lease and stated total: The agent resubmits after fixing the errors

    
The agent's request. Please quote monthly US outbound MMS messaging from 2 vanity short codes, with monthly volumes of 150 thousand to AT&T, 120 thousand to T-Mobile, 150 thousand to Verizon and 10 thousand to U.S. Cellular subscribers. The quote states a monthly total of $14,300.00. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • Order summary. 430,000 outbound messages a month, estimated monthly total of $14,300.00 at list rates.
    • 
    

    
6. Toll-free and volume discount: Toll-free quote with a 10DLC registration and a volume discount

    
The agent's request. Please quote monthly US outbound SMS messaging from 6 toll-free numbers under a standard A2P 10DLC brand and campaign registration, with monthly volumes of 400 thousand to AT&T, 350 thousand to T-Mobile, 400 thousand to Verizon and 30 thousand to U.S. Cellular subscribers. The customer wants a volume discount. The quote states a monthly total of $13,370.00. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Registration on a non-10DLC sender. A2P 10DLC registration applies to local 10DLC numbers only; it is quoted here with a toll-free number or short code.
    • 
      
  • Volume discount to confirm. A volume-based discount is available from Bandwidth but its terms are not published; a person should confirm it.
    • 
    

    
7. Toll-free and volume discount: The agent resubmits after fixing the errors

    
The agent's request. Please quote monthly US outbound SMS messaging from 6 toll-free numbers, with monthly volumes of 400 thousand to AT&T, 350 thousand to T-Mobile, 400 thousand to Verizon and 30 thousand to U.S. Cellular subscribers. The customer wants a volume discount. The quote states a monthly total of $13,370.00. It is ready to send.

    
Verdict: Needs approval.

    
    
      
  • Volume discount to confirm. A volume-based discount is available from Bandwidth but its terms are not published; a person should confirm it.
    • 
      
  • Order summary. 1,180,000 outbound messages a month, estimated monthly total of $13,370.00 at list rates.
    • 
    

    
8. Toll-free and volume discount: The agent resubmits after fixing the errors

    
The agent's request. Please quote monthly US outbound SMS messaging from 6 toll-free numbers, with monthly volumes of 400 thousand to AT&T, 350 thousand to T-Mobile, 400 thousand to Verizon and 30 thousand to U.S. Cellular subscribers. The quote states a monthly total of $13,370.00. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • Order summary. 1,180,000 outbound messages a month, estimated monthly total of $13,370.00 at list rates.
    • 
    

  

  

    
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 sending text and picture messages in the United States: the sender type, A2P 10DLC registration, carrier volumes and any short codes. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of the published rates and rules 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 monthly US outbound SMS messaging from 60 local 10DLC numbers, with monthly volumes of 300 thousand to AT&T. Cellular subscribers. The rest of the request is on screen. The quote states a monthly total of $7,255.00.
    4. 
      
  4. Before it goes out, the agent calls the validator.
    5. 
      
  5. Blocked, with one finding, all in one answer. The quote sends from local 10DLC numbers but has no A2P 10DLC brand and campaign registration; unregistered traffic is being blocked.
    6. 
      
  6. The validator returned one blocking finding 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 registration that depends on the sender type, a rules-based CPQ is error-prone for this.
    8. 
      
  8. Now the agent resubmits.
    9. 
      
  9. The corrected request. It changes the A2P 10DLC registration to standard campaign and the stated monthly total to $7,265.00.
    10. 
      
  10. It calls the validator again.
    11. 
      
  11. Still blocked, with one finding, all in one answer. The quote puts 60 numbers on a campaign that sends to T-Mobile; the limit is 49 numbers unless a number pool request has been approved.
    12. 
      
  12. One finding cleared, but the change brings a different blocking finding: too many numbers on a campaign.
    13. 
      
  13. The agent resubmits once more.
    14. 
      
  14. The revised request. It sets the number pool request approved to yes.
    15. 
      
  15. It calls the validator once more.
    16. 
      
  16. This time the validator clears it.
    17. 
      
  17. The validator also returns the line-item quote. It starts with Outbound SMS to AT&T subscribers (Bandwidth rate $0.0040 plus carrier surcharge $0.0035) and Outbound SMS to T-Mobile subscribers (Bandwidth rate $0.0040 plus carrier surcharge $0.0045); the other three lines are on screen.
    18. 
      
  18. The earlier finding is cleared, and the validator's total, $7,265.00, matches the quote.
    19. 
      
  19. One problem caught in one call, fixed in two passes, and a clean $7,265.00 quote. That is the value of Predictika's validator: catching mistakes before they reach the customer. Now you can try the other scenarios yourself.
    20.