MX Conversations

Find out more about what the conversation is and how / when to use it

Updated over a week ago

Conversations is a Business Premium feature that allows all the users involved in an MX transaction to exchange comments with one another, from within the transaction. All comments are then stored within the audit trail of the transaction (unlike emails, which can be deleted).

To enable this setting, please tick 'Allow recipients to see each other' and then 'Enable conversations'.

If you are dealing with just one supplier or even sending data between colleagues, conversations is a great way to retain the history of all discussion / actions.

It is an optional setting, so if you are sending a transaction where you do not want recipients to see each other or be able to see all comments, leave 'Allow recipients to see each other' switched OFF and your transaction will behave as it always has done (multiple recipients will not know that any other recipients exist).

Check before send

After you click Send - but before the upload starts - you will see a summary of any additional options you have switched on as a double check (if you leave them switched OFF, this pop-up will not be displayed). From here, you can either 'Continue editing', to make further changes, or, click 'Proceed' to start the upload.

Once you are familiar with the new MX functions, you can use the 'Do not ask again' option to stop seeing a reminder.

In keeping with our secure-by-design, easy-to-use approach, we want to be very clear that enabling conversations can only be done by allowing all users in a single transaction see one another.

Viewing / a transaction

On any transaction with conversations enabled, you will see this message as a helpful reminder that comments are visible to everyone.

Can I attach more data?


No, to keep transactions simple and focused on a single request, only comments are permitted. If you wish to send more data related to the original transaction, use the Reply / Linked transaction functionality (if enabled by the customer).

Why do I need to tick two options?

In keeping with our secure-by-design, easy-to-use approach, we want to be very clear that enabling conversations can only be done by allowing all users in a single transaction see one another.

Did this answer your question?