Predictika · Remote connectivity licensing quotes

An AI sales agent's enterprise remote-access quote, checked before it goes out

An AI sales agent prepares a quote for a remote connectivity and device management subscription: the plan, the number of users, the add-ons and the usage the customer expects. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of the public product description and returns a verdict, every reason and the figures it computed.

Scope: TeamViewer Tensor quotes (Lite, Basic, Pro, Unlimited, Access, Support and Support Concurrent) with add-ons, user minimums, device policies, API limits and concurrent channels. See everything this validator covers

This validator models TeamViewer Tensor subscription quotes, not just the scenarios shown below.

  • Plans and minimums — a minimum of 5 licensed users on Lite and Basic, 10 on Pro and 15 on Unlimited; 3 managed devices per user on Access; concurrent channels of 1 per user on Access and Support and 1 per 3 users on Support Concurrent.
  • Limits by plan — device policies (60, 0 on Access, 1,000 on Support), Web API calls per 24 hours (48,000, or 36,000 on Support plans), 50 in-session scripts, two re-assignments per named user a year and the Light User connection limit.
  • Add-ons — single sign-on and the audit log as Lite add-ons, the SDK as a Pro add-on, the Conditional Access Router, and the add-ons that the product description does not list for the Access plan; device monitoring on Support plans goes to a person to confirm.

Any TeamViewer Tensor quote that touches these rules is in scope — not only the scenarios pictured here. Not covered: prices (TeamViewer publishes no Tensor list prices, so this validator produces no price build-up or line-item quote), TeamViewer ONE and other products, and contract terms. Assumptions: where the product description is unclear for the Access and Support plans (for example single sign-on, the audit log and the SDK) no rule is applied; a Support Concurrent channel count is read as one channel for each 3 users rounded up.

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

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
An add-on that depends on the plan: single sign-on, audit log and SDKOnly with care
Each add-on is included on some plans, optional on one and unavailable on others, so every combination needs its own product rule.		The plan and each add-on are in one request and compared together on every call.
Add-ons the product description does not list for one planOnly with care
A product rule per add-on for the Access plan, kept in step with the description as it changes.		Every add-on is checked against the plan on every call.
Limits that differ by plan: device policies, API calls, scripts, devices per userOnly with care
A different limit for each plan, so a lookup per plan has to be built and maintained.		The limits are looked up from the plan and every one is checked together.
A stated channel count that must follow the plan: 1 per user, or 1 per 3 usersOnly with workarounds
The expected count depends on the plan and the user count, and a stated figure is a free-entry field, so extra formulas are needed.		The stated count travels with the quote and is compared with the plan rule 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 4 licensed users; the minimum for this plan is 5.
2The quote has 9 licensed users; the minimum for this plan is 10.
3The quote has 31 managed devices; Tensor Access includes 3 per user, which gives 30.
4The customer needs 5 device policies; the plan includes 0.
5The quote states 6 concurrent channels; the plan gives 1 per user, or 1 per 3 users for Support Concurrent, which does not match 12 users.
6The quote states 9 concurrent channels; the plan gives 1 per user, or 1 per 3 users for Support Concurrent, which does not match 30 users.
7The customer needs 1,001 device policies; the plan includes 1,000.
8The customer needs 61 device policies; the plan includes 60.
9The customer plans 48,001 Web API calls per 24 hours; the plan allows 48,000.
10The customer expects 3 re-assignments per user in a calendar year; the named user license allows two.
11Single sign-on is an add-on on Tensor Lite and the quote does not include it.
12The audit log and API are an add-on on Tensor Lite and the quote does not include them.
13Single sign-on is already included in this plan; the add-on should be removed.
14The SDK is not available on Tensor Lite or Basic.
15The SDK is an add-on on Tensor Pro and the quote does not include it.
16The Conditional Access Router is not available on Lite and Basic and is included in Pro and Unlimited, so it is not sold as an add-on on this 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. Basic plan, SDK and API use: A 25-user Basic quote with the SDK, single sign-on and heavy API use

    
The agent's request. Please quote Tensor Basic for 25 licensed users, with single sign-on and the SDK as add-ons. The customer needs 80 device policies, expects about 60,000 Web API calls a day and 40 in-session scripts, and needs the SDK. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Device policies over the plan limit. The customer needs 80 device policies; the plan includes 60.
    • 
      
  • Web API calls over the daily limit. The customer plans 60,000 Web API calls per 24 hours; the plan allows 48,000.
    • 
      
  • SDK not available on Lite or Basic. The SDK is not available on Tensor Lite or Basic.
    • 
      
  • SSO add-on already included. Single sign-on is already included in this plan; the add-on should be removed.
    • 
    

    
2. Basic plan, SDK and API use: The agent resubmits after fixing the errors

    
The agent's request. Please quote Tensor Pro for 25 licensed users, with the SDK as add-ons. The customer needs 60 device policies, expects about 45,000 Web API calls a day and 40 in-session scripts, and needs the SDK. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • Plan summary. 25 licensed user(s); 60 device policies are included in the plan.
    • 
    

    
3. Access plan limits: A 40-user Access quote with 150 devices, DEX Essentials and AI services

    
The agent's request. Please quote Tensor Access for 40 licensed users, with DEX Essentials and Session Insights and Tia as add-ons, covering 150 managed devices. The customer needs 10 device policies. The quote states 40 concurrent channels. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Managed devices over the Access limit. The quote has 150 managed devices; Tensor Access includes 3 per user, which gives 120.
    • 
      
  • Device policies over the plan limit. The customer needs 10 device policies; the plan includes 0.
    • 
      
  • DEX Essentials not listed for Access. DEX Essentials is not listed for Tensor Access.
    • 
      
  • AI services not listed for Access. Session Insights and Tia are not listed for Tensor Access.
    • 
    

    
4. Access plan limits: The agent resubmits after fixing the errors

    
The agent's request. Please quote Tensor Access for 40 licensed users, covering 150 managed devices. The customer needs 10 device policies. The quote states 40 concurrent channels. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Managed devices over the Access limit. The quote has 150 managed devices; Tensor Access includes 3 per user, which gives 120.
    • 
      
  • Device policies over the plan limit. The customer needs 10 device policies; the plan includes 0.
    • 
    

    
5. Access plan limits: The agent resubmits after fixing the errors

    
The agent's request. Please quote Tensor Access for 40 licensed users, covering 120 managed devices. The customer needs 0 device policies. The quote states 40 concurrent channels. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • Plan summary. 40 licensed user(s); 0 device policies are included in the plan.
    • 
    

    
6. Support Concurrent channels: A 60-user Support Concurrent quote with endpoint protection and device monitoring

    
The agent's request. Please quote Tensor Support Concurrent for 60 licensed users, with Threatdown Endpoint Protection, Mobile Device Management and Remote Device Monitoring as add-ons. The customer needs 900 device policies. The quote states 18 concurrent channels. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Stated channels do not match the plan. The quote states 18 concurrent channels; the plan gives 1 per user, or 1 per 3 users for Support Concurrent, which does not match 60 users.
    • 
      
  • Endpoint Protection not listed for this plan. Threatdown Endpoint Protection is listed only for Tensor Lite, Basic, Pro and Unlimited.
    • 
      
  • Device monitoring depends on the contract. For Tensor Support plans, Remote Device Monitoring depends on the contract or add-on; a person should confirm which applies.
    • 
    

    
7. Support Concurrent channels: The agent resubmits after fixing the errors

    
The agent's request. Please quote Tensor Support Concurrent for 60 licensed users, with Mobile Device Management and Remote Device Monitoring as add-ons. The customer needs 900 device policies. The quote states 20 concurrent channels. It is ready to send.

    
Verdict: Needs approval.

    
    
      
  • Device monitoring depends on the contract. For Tensor Support plans, Remote Device Monitoring depends on the contract or add-on; a person should confirm which applies.
    • 
      
  • Plan summary. 60 licensed user(s); 1,000 device policies are included in the plan.
    • 
    

    
8. Support Concurrent channels: The agent resubmits after fixing the errors

    
The agent's request. Please quote Tensor Support Concurrent for 60 licensed users, with Mobile Device Management as add-ons. The customer needs 900 device policies. The quote states 20 concurrent channels. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • Plan summary. 60 licensed user(s); 1,000 device policies are included in the plan.
    • 
    

  

  

    
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 a remote connectivity and device management subscription: the plan, the number of users, the add-ons and the usage the customer expects. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of the public product description and returns a verdict, every reason and the figures it computed.
    2. 
      
  2. I will start with the first request by the agent.
    3. 
      
  3. The agent says. Please quote Tensor Access for 40 licensed users, with DEX Essentials and Session Insights and Tia as add-ons, covering 150 managed devices. The customer needs 10 device policies. The rest of the request is on screen.
    4. 
      
  4. Before it goes out, the agent calls the validator.
    5. 
      
  5. Blocked, with four findings, all in one answer. The quote has 150 managed devices; Tensor Access includes 3 per user, which gives 120. The customer needs 10 device policies; the plan includes 0. DEX Essentials is not listed for Tensor Access. The other one is on screen.
    6. 
      
  6. The validator returned four 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. 
      
  7. What this shows: for limits that differ by plan: device policies, API calls, scripts, devices per user, a rules-based CPQ is error-prone for this.
    8. 
      
  8. Now the agent resubmits.
    9. 
      
  9. The corrected request. It changes the add-ons on the quote to none.
    10. 
      
  10. It calls the validator again.
    11. 
      
  11. Still blocked, with two findings, all in one answer. The quote has 150 managed devices; Tensor Access includes 3 per user, which gives 120. The customer needs 10 device policies; the plan includes 0.
    12. 
      
  12. Two findings cleared. Still blocking: managed devices over the Access limit and device policies over the plan limit.
    13. 
      
  13. The agent resubmits once more.
    14. 
      
  14. The revised request. It changes the device policies needed to 0 and the managed devices to 120.
    15. 
      
  15. It calls the validator once more.
    16. 
      
  16. This time the validator clears it.
    17. 
      
  17. Both earlier findings are cleared, and the validator's figure matches the quote.
    18. 
      
  18. Four 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.
    19.