Predictika · Maritime satellite terminal and service quotes

An AI sales agent's Iridium Certus quote, checked before it goes out

An AI sales agent prepares a quote for Iridium Certus maritime service with a terminal, a service tier, voice lines, a cable run, a data plan, a term and a discount. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of the terminals and service tiers and returns a verdict, every reason and the contract total it computed.

Scope: Iridium Certus 100, 200, 350 and 700 service with seven maritime terminals against speed, voice lines, GMDSS readiness, cable run, data plan, term, fleet size, discount and contract total. See everything this validator covers

This validator models Iridium Certus maritime quotes, not just the scenarios shown below.

  • Terminal and service tier — which Certus tier each terminal supports, the speed the customer needs against the speed of the tier, and the voice lines and GMDSS readiness each terminal offers.
  • Installation and data plan — the antenna cable run each terminal allows, the data plan each tier offers, and the use the customer expects against the plan.
  • Term, fleet, discount and total — approval steps for short terms on the faster tiers, for fleet orders and for larger discounts, a discount ceiling, and the contract total the quote states against the total computed from the modeled prices.

Any Iridium Certus maritime quote that touches these rules is in scope — not only the scenarios pictured here. Not covered: handsets, Iridium GO!, messaging and IoT, aviation and land terminals, and reseller-specific SKUs. The service class names and speeds, terminal names and voice lines come from public pages; the terminal-to-tier table, plan limits, thresholds and all prices are modeled, not published by Iridium or the terminal makers.

The AI sales agentBuilds the terminal and airtime 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
A terminal that supports only some service tiersOnly with care
Each terminal supports its own range of Certus tiers, so every terminal and tier pairing needs a rule.
The terminal and the tier are fields of one request and checked together on every call.
Speed, voice lines, cable run and GMDSS that depend on the terminalOnly with care
Each terminal has its own voice lines, cable limit and GMDSS status, so each customer need needs its own rule per terminal.
The customer needs and the terminal are fields of one request and compared on every call.
A data plan limited by the tier and checked against expected useOnly with care
The plan limit depends on the tier, and the expected use depends on the plan, so the rules chain together.
Plan, tier and expected use are fields of the request and checked together.
A stated contract total that must match the computed totalOnly with workarounds
The total is built from the terminal count, hardware, plan, per-GB airtime, term and discount, so a separate rule is needed to 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.
Every problem returned in one answerOnly with workarounds
Rules tend to fire as a 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.

1This terminal does not support the quoted Certus service tier.
2The customer needs 300 kbps; the quoted Certus tier gives 176 kbps.
3The customer needs 3 voice lines; the quoted terminal has 2.
4The customer needs a GMDSS-ready terminal and the quoted terminal is not listed as GMDSS-ready.
5The antenna cable run is 60 m; the quoted terminal allows 50 m.
6The quoted data plan is 15 GB a month; this Certus tier offers up to 10 GB.
7The customer expects 12 GB a month; the quoted plan includes 10 GB.
8The quote states a contract total of 20,000 dollars; the quoted items give 22,976.
9The discount is more than 10 percent of the contract subtotal; a sales manager must approve it.
10The discount is more than 25 percent of the contract subtotal.
11A term under 12 months on Certus 350 or 700 needs a commercial review.
12An order of 20 or more terminals needs a fleet rollout and activation plan.

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. Terminal and tier: Two SAILOR 4100 terminals on Certus 350 with a GMDSS need, three voice lines and a long cable run

The agent's request. Please quote 2 SAILOR 4100 terminals on Certus 350 for 12 months, with 3 voice lines, GMDSS, a 40 m antenna cable run, 300 kbps of speed, a 12 GB monthly data plan for about 8 GB of use, for a contract total of $15,336. It is ready to send.

Verdict: Blocked.

  • Service tier not supported by the terminal. This terminal does not support the quoted Certus service tier.
  • Voice lines exceeded. The customer needs 3 voice lines; the quoted terminal has 2.
  • GMDSS-ready terminal needed. The customer needs a GMDSS-ready terminal and the quoted terminal is not listed as GMDSS-ready.
  • Antenna cable run too long. The antenna cable run is 40 m; the quoted terminal allows 25 m.
  • Data plan over the tier limit. The quoted data plan is 12 GB a month; this Certus tier offers up to 10 GB.

2. Terminal and tier: The agent resubmits after fixing the errors

The agent's request. Please quote 2 Intellian C700 terminals on Certus 350 for 12 months, with 3 voice lines, GMDSS, a 40 m antenna cable run, 300 kbps of speed, a 10 GB monthly data plan for about 8 GB of use, for a contract total of $23,376. It is ready to send.

Verdict: Allowed.

  • Contract summary. 2 terminal(s); hardware 13,800 dollars, airtime 798 dollars a month for 12 months, discount 0 dollars, contract total 23,376 dollars (modeled illustrative prices).

3. Speed and data plan: A VesseLINK 200 on Certus 200 with a high speed need, a mismatched plan and a wrong contract total

The agent's request. Please quote 1 VesseLINK 200 terminal on Certus 200 for 24 months, with 2 voice lines, a 30 m antenna cable run, 300 kbps of speed, an 8 GB monthly data plan for about 10 GB of use, for a contract total of $9,576. It is ready to send.

Verdict: Blocked.

  • Speed needed exceeds the service tier. The customer needs 300 kbps; the quoted Certus tier gives 176 kbps.
  • Data plan over the tier limit. The quoted data plan is 8 GB a month; this Certus tier offers up to 5 GB.
  • Expected use exceeds the data plan. The customer expects 10 GB a month; the quoted plan includes 8 GB.
  • Stated contract total does not match. The quote states a contract total of 9,576 dollars; the quoted items give 11,076.

4. Speed and data plan: The agent resubmits after fixing the errors

The agent's request. Please quote 1 VesseLINK 700 terminal on Certus 350 for 24 months, with 3 voice lines, a 40 m antenna cable run, 300 kbps of speed, a 10 GB monthly data plan for about 10 GB of use, for a contract total of $15,076. It is ready to send.

Verdict: Allowed.

  • Contract summary. 1 terminal(s); hardware 5,500 dollars, airtime 399 dollars a month for 24 months, discount 0 dollars, contract total 15,076 dollars (modeled illustrative prices).

5. Fleet and short term: A twenty-terminal fleet on a six-month term with a larger discount

The agent's request. Please quote 20 VesseLINK 700 terminals on Certus 350 for 6 months, with 3 voice lines, a 40 m antenna cable run, 300 kbps of speed, a 10 GB monthly data plan for about 8 GB of use and a discount of $19,000, for a contract total of $138,880. It is ready to send.

Verdict: Needs approval.

  • Discount over 10 percent. The discount is more than 10 percent of the contract subtotal; a sales manager must approve it.
  • Short term on a high tier. A term under 12 months on Certus 350 or 700 needs a commercial review.
  • Fleet order. An order of 20 or more terminals needs a fleet rollout and activation plan.
  • Contract summary. 20 terminal(s); hardware 110,000 dollars, airtime 7,980 dollars a month for 6 months, discount 19,000 dollars, contract total 138,880 dollars (modeled illustrative prices).

6. Fleet and short term: The agent resubmits after fixing the errors

The agent's request. Please quote 12 VesseLINK 700 terminals on Certus 350 for 12 months, with 3 voice lines, a 40 m antenna cable run, 300 kbps of speed, a 10 GB monthly data plan for about 8 GB of use and a discount of $6,000, for a contract total of $117,456. It is ready to send.

Verdict: Allowed.

  • Contract summary. 12 terminal(s); hardware 66,000 dollars, airtime 4,788 dollars a month for 12 months, discount 6,000 dollars, contract total 117,456 dollars (modeled illustrative prices).

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 quote for Iridium Certus maritime service with a terminal, a service tier, voice lines. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of the terminals and service tiers and returns a verdict, every reason and the contract total it computed.
  2. I will start with the first request by the agent.
  3. The agent says. Please quote 2 SAILOR 4100 terminals on Certus 350 for 12 months, with 3 voice lines, GMDSS, a 40 m antenna cable run. It is ready to send. The rest of the request is on screen.
  4. Before it goes out, the agent calls the validator.
  5. Blocked, with five findings, all in one answer. This terminal does not support the quoted Certus service tier. The customer needs 3 voice lines; the quoted terminal has 2. The customer needs a GMDSS-ready terminal and the quoted terminal is not listed as GMDSS-ready. The other two are on screen.
  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.
  7. What this shows: for speed, voice lines, cable run and GMDSS that depend on the terminal, a rules-based CPQ is error-prone for this.
  8. Now the agent resubmits.
  9. The corrected request. It changes the terminal to Intellian C700, the data plan to 10 GB a month and the stated contract total to $23,376.
  10. It calls the validator again.
  11. This time the validator clears it.
  12. All five earlier findings are cleared.
  13. Five problems caught in one call, fixed in one pass, and a clean $23,376 quote. That is the value of Predictika's validator: catching mistakes before they reach the customer. Now you can try the other scenarios yourself.