It is often used to mistake-proof. For example, in the service industry, you can use it to make sure tasks are done only one way through standardization.
Yes, the poka-yoke system is known as "control -measure" too and its objective is eliminate the "error-condition" of any process; the error -conditions are occasioned by incorrect activities with no control, you will have that find them obviously, and correct it applying "sop" (Standard Operation Systemss), in this case (service industry) the poka -yoke system solution maybe a "SOP", but there are others Mistake - proofing that you can apply, this is just a example.
Yes, its very much applicable in service context. But the magnitude of mistake proofing could vary based on the business context. It could be a detection, caution or show-stopper based on how critical % of error could be entertained in your service.