Our support thread is seeded by the client, and two of its five author values never survive the trip

When the in-app widget escalates, it replays the conversation it rendered into a new ticket. The endpoint's schema accepts every author value and the service layer drops two of them, which is not an oversight.