Ah, you wish to PARTIALLY copy information - but not everything. You need to keep the unique parts unique but copy the common parts.
One easy way to do this is to make a combo box that shows you recent bookings so you can select one of those records to become your template. If the desired information is then kept in the extra columns of the combo box, you can use some code, perhaps behind a button-click (that says "COPY FROM SELECTED RECORD") to copy from the columns of that selected combo row into the relevant fields of a new record on the booking form.
Another way is to have a command button that you would use when the data from the first booking is still on screen. Have code behind the button click event that will store relevant customer data in the form's class module declaration area. Then have ANOTHER button such that you can recall the stored customer data. Since you will know ahead of time that you intend to copy that information, you can use the buttons or not, as needed.
Both of these methods will work. Neither one is the preferred method for long-term stability.
Another way that is more technically correct (better normalized) but might require some structural rework is that you FIRST define your customer in a customer table. THEN when you book the rooms, you can use a combo box to select your customer and, instead of repeating the customer info, just store a customer ID for each booking. Then when needed, use the customer ID to retrieve the rest of the information.
The preferred method uses the power of a relational database (which Access is) to split out things in a way to reduce duplication. By keeping the customer data separate from the room data, you accomplish something called normalization. If you have no familiarity with that term, it is time that you did some reading. For this forum, which IS a database site, search for "Normalization." (SEARCH button is top-right in the menu bar.) For a more general web search, use "Database Normalization" because other disciplines use "normalization" differently - for example, in chemistry, politics, economics, psychology, mathematics, ... you get the idea. When reading about normalization, you usually only need to get to 3rd normal form for Access to be perfectly happy.
To build reports (where you expect or even need data duplication) you can build a JOIN query where the booking record and customer record can be logically joined together - only during the execution of the query - to have everything you need for the report in a single (virtual) record.