An agent that books travel on an English website is not an agent that can process an expense claim at a Japanese manufacturer. The difference is not language alone.
Process is encoded in documents
Approval chains (ringi), stamped forms, monthly closing conventions and paper-derived layouts shape what an agent sees on screen and what counts as a finished task.
Tone is part of the task
Drafting a reply to a client who is late with payment demands calibrated honorifics and softening phrases. A grammatically correct, blunt message is a failed output.
Software is different
Domestic accounting, HR and groupware tools have their own UI conventions. Trajectory data collected on those tools, with consent from the organizations involved, is scarce.
What to ask a data provider
- Were these workflows demonstrated by practitioners from real roles?
- Is any real company data involved, and under whose permission?
- How are success criteria defined and verified?
General information, not legal advice.