Abstract The conversation model captures interactions among the components of a composite web service. A conversation is the global sequence of messages exchanged among the components. We discuss the impact of asynchronous communication on the conversation behavior. It turns out that the conversation behavior is significantly different for synchronous and asynchronous communication and demands new techniques for static analysis of composite web services. We outline strategies of model checking service composition for both bottom-up and top-down design approaches.