What is a good practice for working with different message types in the Azure service bus

I am new to using a Message based architecture such as the Azure Service Bus Topic/Subscription feature.

I am wondering how best to work with different message types.

E.g. Say I have two messages. One to create a new customer and another to delete a customer.

I could;

1. Create two topics. Each topic will have one subscription. The code that processes the message will deal with its message type independently.

2. Create one topic for customers. Create one subscription to receive all the messages. The code that processes the messages will need to determine the message type before processing it.

3. Create one topic for customers. Create two subscriptions, which filter the on the message type. The code that processes the message will deal with its message type independently.

I'm sure there is no right or wrong, but would appreciate some input from someone with experience in this area.

Many Thanks,

David