You should consider having a version that does not print the email in the invocation - it may get picked up and be spammed. one might not want to publicize the backend email recipient of the support/feedback. Another reason is that if someone figures out the fig api, they can send emails to arbitrary recipients thus blacklisting the fig domain.<p>One thought is that it ought to be a service that works with a hash/UUID and that value maps to a recipient email on your database. so the only people who know my email is fig itself. Still - one can in theory spam every fig user by scraping for fig js. that brings me to some sort of recaptcha, i'm not a robot support.<p>Added bonus: backend can route the message via any channel not just email.