Status (Action required) and main actions in a big data table

Recently i started creating a big data table for a booking company. Usually I don't really have big problems with data tables but this specific one drives me nuts.

It is a platform for restaurants. When the diner will come to your venue, you need to be able to send them a menu through SMS for example to order. Venues in general want to send the menu when they will change the booking status from "Expected" to "Seated" for example. the 1st column incorporates the booking status "Expected arrival", "late" etc and the time of the booking. The devs told me that it is not a good practise in general to trigger something with a status change which i disagree for the current situation at least

I don't want to add the action "send email" within the statuses dropdown, cause it doesn't make sense, plus when you select a booking status the dropdown panel closes and pressing the same button again to make an action it is not ideal.

Having the "send email" action at the far right, and make that column sticky is ok-ish, but the user will need to travel all the way to the end of the screen, which is not good UX. Most of the times "Send email" will only be used once for every booking. Below you can see some wireframes, Action at the end, action at the front incorporated within the 1st column and last one triggered by changing the status.

I am literally stuck. Any ideas please?