"The thing about Erlang is that it's in some sense 2 languages, at least you program it 2 levels because one is the functional language that you use to write a single process and then there is what you think about all these processes and how do they interact, one process is sending messages to the other. At a higher level, that Erlang is object oriented, at the lowest level it's a pure functional language and that's how it got advertised for a long time."
[...]
"The only way in Smalltalk to interact with an object is send it a message, but the issue is what message do you have. It's the same thing in Erlang"
So it seems to me that he's saying that Erlang's processes are close to Smalltalk's objects.
I recommend reading all the transcript (much quicker than watching the video).