Currently, we are inserting the passport picture along the message
This email has been authenticated by Vereign. You will need to sign up to view the senders identity. It will only take a few minutes and you will then be able to start sending and receiving authentic email. Find out more!
like so this
And since it is not responsive, this is how it looks on mobile:
There is room for improvement here, and any improvement is likely going to go a long way toward convincing people.
Aspects that can be improved
For one, this should talk about the actual identity of the sender, not just include the picture.
Here is a mock-up of how I think this could look like:
The data in the mini-passport should be based on the actual data of the passport defined & used for the email sent. That data has some fields that are included by default if included in the passport:
Name
Email
Mobile phone number
Twitter
Linkedin
and are shown with verified checkmarks if actually verified. Fields that are not in the passport are not included, and the fields are then just omitted from the micro-passport.
The entire passport should be a link to the passport page in the Vereign dashboard.
Upper left corner could be with Vereign logo or some kind of "verified" iconography.
Message / text can be:
This email and the identity of the sender have been authenticated via Vereign. View blockchain audit trail. Not a user? Sign-up now, it takes less than a minute.
with "View blockchain audit trail" as a link to the conversation in dashboard and "sign-up now" being a link to registration.
All subject to further improvement, of course, but I think this would already increase the value a lot.
@georg.greve It would start to annoy me if I saw this giant header each time I received an email. The original design concept was to make it as compact as possible. I'm not against this new suggestion, I can make it look nice, but do we really need to display it every time.
An alternative... Links could take the recipient to that Vereign contact page and display their (passport) details there (their choice).
Another alternative... Can we display the full one on the first email and then a condensed version for each email in the same thread there after? This is very similar in the way we use signatures, attaching the full one each time is not good practice.
The value of our service comes from the verification of the identity.
It's also been the most common question by everyone who saw the demo thus far: Where do I see the verification of the identity. Right now there is no identity information (except the picture) included. But this is the core value we add. So we should show it. I would rather show this and then just add a
"What is this header? Learn more."
text to it.
As to size: The current header has
41 words
221 characters including spaces
whereas the new design proposed, using my own data for reference, has
32 words
210 characters including spaces
meaning it is actually LESS HUGE than what we currently have. ;)
We are talking about mail. The Vereign logo should be a bit larger, and applied more like a postal stamp on an envelope. Like a wax seal of authenticity.
I was under the impression, that this banner we are including now is for popularization purposes for a limited time. I now realize, that all messages will include our banner.
The banner is the single biggest contributor to virality and therefore generally assessable growth value our service has to offer. Putting thought into this user experience is therefore very well spent. The value of the content within the banner is the most sensitive, when the recipient is not a user yet. My first thought when receiving a mail like that is: What the heck, now I even get inside email spam from authentic looking emails-addresses ? This must be scam... That very first time has to be the most authentic of all. When both are users, it boils down to making it extremely lean almost invisible, because once everybody knows, it becomes a bother. Nevertheless, the relevant info respectively, even more relevant, the NOT verified stuff should be highlighted henceforth.
I was under the impression, that this banner we are including now is for popularization purposes for a limited time. I now realize, that all messages will include our banner.
The banner will be there for every message throughout the beta period.
It will likely evolve over time, though, including on feedback from users. For the live system, there may even be ways for power users to customise them. Plenty of options.
There are huge benefits to the banner: It helps to communicate what's special about these mails. So it is actually part of the value to the user.
So can we avoid sending the full one every time (the other alternative)?
I think it would make sense to user a more explanatory banner on first contact, and afterwards only include the "passport image with seal of authenticity" once people know what it is.
FWIW: We should even consider attaching / linking to a vCard for the passport. But this can be a further improvement. For now, making the banner transport actual value will be a huge step forward.
Side note: There are many people who have set their email clients to routinely include their vcard & image with each mail. This is like the "platinum" version of that.
For recipients that have no Vereign account, they will receive something similar to what we have already coded. The main difference here is the message and background colour.
Next up are two options for the recipient who has a Vereign account.
First, we have the passport concept. After careful consideration, I have moved the content to the bottom for all recipients with Vereign accounts. This makes perfect sense as we no longer need to push it in their face quite as much as they are already onboard. The design is simple to it renders across all clients as consistent as possible.
Most importantly, it also acts as a professional signature, a signature that self integrates and updates! Another advantage of the Vereign system.
Next up, this simplified version is used when the user opts not to share their personal data, but they still want the email to be authenticated.
@gilesvincent and @georg.greve what is the exact workflow, here? We send the first email, if the recipient doesn't have an email in our database and the other ones, if he has or?
@gilesvincent@georg.greve actually, what are recipients of emails from beta testers supposed to do, when they receive a vereigned email? Obviously, they can sign up, but what happens then? If we stop the process there, we are breaking the chain of virality and can't measure it, either.
They sign up and join the same viral loop. Long term we can provide a custom journey for these 'new users from a Vereign email', as some may have no idea what Vereign is. But that can be later, even I need to experience the existing UX before we design alternatives.
Our main blocker here though is having a working plugin for Gmail. None of the above is possible until that is finalised sadly (or the Roundcube version I guess - whichever comes first).
Next question: what's the difference between putting the first 50 users on and let the viral loops begin vs. putting all the 200 (?) currently queued people on? We are basically giving the accidental recipients of emails of the first batch of beta testers priority over those who have signed up for the beta test.
Yes. That is a bit of a loop hole. I'm not sure how to resolve that, but I guess it will be a nice problem to have if our email sign ups start to flood in when this is launched. Happy to hear ideas around that.
Still, I have my question not answered? When to send each version of the email? And do we want to mimic our behavior from the beta with the mailto, stuff?