It's probably their CS Twitter client that's coded without proper awareness of threads (likely only letting staff reply to the original message)