Yes they would be, you would get one row with loads and loads of columns, that is normal for a join, even if you used a MySQL VIEW it would give you the same sort of result as a join does, where it gives you a single row with many many columns.
So maybe I am not really understanding what exactly you want to achieve as your end result.
Are you wanting a single table as your final result or multiple tables, and what is the sorting parameter, I assume the ClientID.
Also does your application have multiple things a single client can do, in other words
Lets say you have a single client with a clientID of 222
222 makes 3 bookings over the course of a year, and all 3 bookings are stored in the bookings table and all 3 bookings have the same clienttID of 222
222 in the same year makes 5 transactions, and all 5 transactions are stored in the transactions table and all have the same clientID of 222
222 performs 11 tasks, and all 11 tasks are stored in the tasks table and all have the same clientID of 222
222 sends 4 emails, and all 4 emails are stored in your emails table, and all have the same clientID of 222
222 sends 8 messages, and all 8 messages are stored in your messages table, and all have the same clientID of 222
So now you want to show all activity for 222 over a year in a single table on your page therefore with the above examples you will have
222 did 3 bookings
222 did 5 transactions
222 did 11 tasks
222 did 4 emails
222 did 8 messages
Which will output 31 rows in a single table. Is that the correct idea?
EDIT: @Hyperbytes is our resident MySQL expert, because if my example is correct of what you would like then I am afraid that exceeds my MySQL knowledge.