My team and I develop software that our customers will use to interact with their customers.  Additionally, we also eat our own dogfood and use the software ourselves to interact with our customers.Therefore, it can sometimes be difficult to explain use cases and scenarios, as our employees can be operators, our customers can be operators, and our customers' customers can be visitors.However, our customers can also be visitors interacting with our operator employees, our customers' customers can be visitors interacting with our customer or our employee.Here is a model where:A is an employeeB is a customerC is our customers' customerX  interacts with  YOperator --> Visitor      A  -->  B      A  -->  C      B  -->  CBecause sometimes our customers can play different roles, it's sometimes necessary to refer to the specific role, Operator or Visitor, instead of Employee and Customer.It's also a mouthful to say customer's customer all the time.I was wondering how other development shops handle these semantic details when writing their use cases and scenarios.  Are there any one-word, generic terms that can apply to any product that involves a third-level actor?Other than using the specific roles, Operator and Visitor, what words could be used to identify a customer of a customer?  The word would need to be short enough as to be adopted within an organization.  If longer than a couple syllables, it's shortened form must still differentiate it from the other actors.
What do you call a customer's customer in a specification document, use case, or scenario?
communication;naming;specifications
to explain use cases and scenariosThat's the key: use the terminology of the domain, i.e. the names of the roles. Who can play the roles is not important. Make sure that the roles are well-defined (for each scenario).It is entirely possible for me to visit my own website and purchase my own products. It's silly, but it's possible [but I've done it to test the e-commerce software!]. That fact that I am the provider, host, author, webmaster, copywriter, programmer, client, customer, visitor, purchaser, guest, owner, and employee all at the same time does not alter the terminology of the use-case: customer buys product from owner via web form