Christian I.

Different uses. Sometimes uploading to other platforms when setup within Clay is lacking or faster via csv. Sometimes to perform semi-manual sanity checks on sensitive data (e.g. matching campaign targeting vs job title where the AI categorisation might have made mistakes. Sometimes to reformat (e.g. colors) before sending in password protected way to client.

Mitch, I find the solution impractical. Imagine a table with 5k contacts. But I’ll give it a try.

Hi Marina, for us using a tool to use less tools, I would expect this issue to be fixed. Love that you are referencing an issue of many years ago Mac/Numbers/Excel. I am sure a solution has been found since then. I hope it will be implemented in Clay soon. My thought was that many of the current users are working in US/English contacts mostly, hence nobody (or a few) really pointed at this issue. But as Vlay goes more and more international, this issue becomes more relevant.

No. It was not helpful. Please add an "export UTF-8" functionality so we do not need to add an extra step to a simple operation done quite often. Tnxs.