supritgandhi

Hi, thanks for your comment!

But, people who are not much familiar or used to with email might find it very difficult and not so user-friendly to use email aliases and folders.

Hi,

Regarding, [email protected] - Yes, that is one of the feature I am trying to improve, given many people who are not that comfortable with email might find it difficult to configure it.

And for spam, a considerable amount of spam messages are automated using different tools or platforms. Sending automated messages won't be possible through RelayBeam, because marketing companies won't have any tools or APIs to do so.

This should solve the spam issue to a large extent.

Thanks for your comment!

Feel free to ask if you have any questions!

Please help me understand:

Are you asking if you have to share your contact details like phone number or email? - No you need to share any of those. You don't even need phone number or email address for creating account on RelayBeam. You just need to share relevant port address for communicating with someone.

Or are you asking about migrating all your existing conversations in other tools?

Hi, thanks for your comment!

You have exactly pointed out why I am building RelayBeam. You mentioned that you create multiple emails for different purpose, with RelayBeam you don't need to create multiple emails.

Now for naming, I can easily create a verification service, where certain port addresses can get verified, and if the port address gets verified, I can just share 'Verified' badge next to port address, and this badge will have all the details like which organization is this person related and so on.

And once you have the port address, you can save it to your address book with any name you feel comfortable. (Will be developing this address book feature)

Do let me know what other ideas do you have to solve this problem? Let's chat!

Hi, I think using "Ports" is the unique and differentiating way of messaging here.

Do you have suggestion on any additional features? I'd be happy to discuss.

> Now they must remember which address to use for what.

I will be introducing the address/contact book feature for each user, wherein users can save the port address with whatever name they feel comfortable. So, users just need to send a message to someone from the address book (if already added), this way users don't need to remember exact port address, rather just refer the address book.

> this solution requires all users to use the same platform

I think except email, most of the solutions will require all users to use specific platforms.

Hi, I'll try to explain it as follows:

> People switch between multiple apps and channel for different purpose, ports can help to distinguish messages based on context and purpose.

> Having different types of discussion in handful of channels makes it difficult to track important messages, with multiple ports you can just focus on the important ones and ignore others.

> Users generally use apps like Slack/MS Teams for internal communication and prefer email for external communication. RelayBeam can be used for both the purposes easily.

> Again using ports, this can simplify the information management, because users can search for information in the relevant port.

> Generally email addresses are available on many sales directories websites. And your work related emails can be searched through such directories. Using different ports, you can just display certain ports publicly, and even if you don't make any of your ports publicly available, then I don't think it would be easily discovered, which should solve the spam problem to some extent.

Let me know if you'd like to know more on any of the above.

You can start using RelayBeam whenever you think ports can help you organize the conversations.

Thanks for your comment! Fragmented communication as in, users need to jump across multiple apps or platforms for different context, simple example, people generally use platforms like Slack/Teams for internal communication and prefer email for external communication. With RelayBeam you can have single platform for both the purpose.

You can create project specific ports as well, as it can can segregate the messages as per the context. Another example: if joe is in sales & marketing department, then joe can have joe@sales and joe@marketing, which can be helpful in prioritizing the messages.

Do you have any suggestions for further improvements?

Thanks for your comment!

Using ports (as inbox) users can segregate the messages as per the context, this should simplify the information management, because users can search for information in the relevant port.

Users can compose new threads for different topics of discussion, hence these threads will only be relevant with respect to their topics.

As and when the new messages keep coming, there will be some threads where the discussion is no longer active, and users don't need to keep track of such thread discussions. This should solve the problem of overflowing inboxes.

Do you have any suggestions on how this can be further improved? I'd be happy to discuss.

Thanks for going through it! Will providing a self-hosted configuration for enterprise accounts solve this?

Yes, that is one of the feature I am trying to improve, given many people who are not that comfortable with email might find it difficult to configure it.

Also, email is generally used when people can't use apps like Slack or WhatsApp for communicating. Here, I'd like to provide a better alternative through RelayBeam.

Feel free to use RelayBeam and let me know what additional features you would like to see!