The agent mapping repository 415 may store agent rules for a multi-agent entity. An administrator for the multi-agent entity may specify agent rules for the multi-agent entity using the user interface component 430 for the business application messaging client 420. The agent rules configure the handling of messages for the multi-agent entity. Upon receipt of a message, the message processing component 480 processes the message based at least in part on the agent rules for the multi-agent entity. The agent rules may specify a default set of agents for the multi-agent entity, in which the message processing component 480 automatically includes all of the default agents in any created message thread. The agent rules may specify one or more administrators for the multi-agent entity.
The agent rules may specify a thread locking rule, in which posting messages to, but not reading message from, a message thread is prevented for agents other than a first agent that responds in the message thread. A thread locking rule may specify that administrators are exempt from being prevented from posting.