I'd be interested in how you'd propose to make that work when operators may be jumping in to a robot anywhere on the planet from one minute to the next. Require logging and reporting on when remote labor was used to support the tax jurisdiction you're operating in? It seems that would also require reporting to every locality you operate robots in individually, which is currently not necessary.
Would you propose to use the same method for other remote services such as call center support?
That would be a problem for these companies to figure.
> It seems that would also require reporting to every locality you operate robots in individually
Yes, exactly. That should be required. Also your call center idea is pretty good too, though I think not quite as clear cut as having remote laborers use robotic bodies to circumvent minimum wage laws.
The call center example is actually more relevant than you might imagine. The jobs often look very similar to remote tech support in practice. In fact, some companies running call centers have begun offering remote support to autonomous systems as an expansion of their market.
This type of labor falls pretty squarely in the "information work" category, and often (as in your Kiwi example) looks mostly like operators performing a high-level task like specifying waypoints on a map.
Would you propose to use the same method for other remote services such as call center support?