As another example, the user may forget to move his music to the Kitchen and instead may travel to the Kitchen while the content is still playing in the bedroom. In this instance, the user can use the wake word/phrase and issue the vocal command “resume.” A request may be transmitted, this time by the Kitchen device and received by the content management engine (e.g., after potentially being routed by another service). The content management engine may determine that the request received at the bedroom device relates to moving content between devices and may utilize previously received state information that describes the content historically presented at the device(s) associated with the user profile with which the receiving device (e.g., the Kitchen device) is associated. The content management engine may attempt to identify, from the historical record of the content played at these devices, the content to which “resume” refers. Said another way, the content management engine may identify from the historical record the last content played was a song by Artist A at the bedroom device and may transmit a request to a service provider computer (e.g., a computer hosting a music service) to request the music be moved from the bedroom device to the kitchen device. In response to the request, the service provider computer may halt playback of the content at the bedroom device and may begin playback of the content at the Kitchen. In some embodiments, playback may begin at a last run time of the content reached at the bedroom device. Thus, playback at the kitchen device begins at the same run time as the run time at which the content was stopped in the bedroom.