Controlled validation operation

FOR SYSTEM HOUSES · Partner model

You run the IT. ITBox closes the physical device case.

You keep the customer, the IT context and the existing service relationship. Depending on the model, ITBox takes over the ReturnKit, the physical return, the documented intake and the agreed closing documentation.

Models in the validation phase

  • Referral — you recommend, ITBox runs the case directly with the customer
  • Co-branding — joint communication in the pilot, after individual review
  • White-label — delivery under your brand, only after a clarified contract, liability and quality model

A clear boundary

ITBox does not take over Microsoft 365, helpdesk, network, backup or cybersecurity services and does no cross-selling into these areas. The ongoing IT mandate stays with the partner.

What a partner case needs

  • reviewable from a single case — no minimum volume
  • a clear scope of roles and responsibilities before the first case
  • a written review per case, no automatic partner approval

FAQ

Can a system house use the service under its own brand?

Referral and co-branding can already be reviewed in the validation phase. White-label delivery requires a clarified contract, liability, role and quality model. The IT partner keeps its customer relationship.

What does the partnership cost?

Prices, branding and responsibilities are fixed in writing only after scope, volume, liability and the split of tasks are clarified. There is no public partner price list.

Have the partner model reviewed in writing.

A non-binding written review. No partner approval yet and no minimum volume.