separating Akka actors from implementation logic

Is there a design pattern that would be commonly applied to facilitate the separation of concerns between an Akka actor's message handling and the business logic that it implements?