The Bondle-Email Bridge is a significant achievement by our team that will now enable you to communicate with people who are / prefer to remain on emails. Here is a visual representation and a brief video of how the Bondle-Email Bridge works:

 There are a few new concepts and changes to system behaviour that we would like to outline in this post.

  • A new create conversation dialogue box

– The enhanced create conversation dialog box allows you to add the first message for the conversation as you create it

– Unlike the previous version where the personal message was not added to the conversation but was only sent via the invite email, this message is added to the conversation upon creation

– You also have the Advanced option where you can define the conversation purpose and depending on your license category specify the custom email for this conversation

  • Introducing the concept of an Email Participant

– Thus far, when you invited someone to a Bondle conversation, they could participate in the conversation only after they signed up to Bondle

– Going forward, the system will perform an act of “auto acceptance” of any person who is added to a conversation but does not have an account on Bondle

– From that point onwards messages and document related activities that happen within the conversation will be sent to the Email Participant via email

– Please note that the invitation email will NO LONGER be sent out to participants

– The Email Participant can choose to sign up to Bondle at any time and will be able to enjoy all the benefits of Bondle

  • A dedicated email address for every conversation

– You will notice (on the web version) that every conversation now has a unique email id that is prepopulated by the system

– This email will be of the format

– All emails emanating from this conversation will be sent using this email id. However, when the email participant receives the email, they will see your name in the inbox

– If you are on our COMPANY plan, then you can customise this email id in the following manner:

a) You can set a user-friendly prefix, instead of the alphanumeric string such as “sales_discussion” or “john_smith” or “project_delta”

b) Your emails are also sent out with the primary domain “”

c) Assign a custom sub-domain that can represent your company, ex: abcd

d) Now, for a given conversation, your email id can read “”

  • Outgoing emails

– Activities in a conversation are batched in 5-minute intervals. This ensures the Email Participant does not receive an email for every message

– The batched email is then queued for 10 minutes before being sent out. This is to cater for message edits / deletion

– Any document that is loaded into a conversation is sent in the email as a secure link

– When an email participant accesses the document, we capture this event in the Audit History

– If a document is deleted in the conversation (within 2 hours of loading) the link would inform the Email Participant that the document is no longer shared with them

– All secure links expire within 3 days for security reasons. The Email Participant can request for a new link and the same will be emailed across to them

  • Incoming emails

– An incoming email is parsed by the system and the contents are loaded into the specific conversation

– If there are any documents that have been sent as an attachment, they are extracted and loaded into the Documents section under a folder called “Email Attachments”

– All incoming emails and attachments are automatically scanned for viruses and deleted upon arrival

  • Incoming emails from users who are NOT part of a conversation

– This could happen in one of three cases:

a) An Email Participant CC’s a third party onto the email who then replies to the email

b) The Email Participant replies from a different underlying id

c) Someone is trying to spam your conversation having gotten hold of the conversation email

– Whenever such action occurs, the incoming response is added to the NOTIFICATION conversation that has been newly introduced

– This ensures NO ONE can spam your secure conversation

  • Co-existence of Bondle users and Email Participants in a conversation

– You can have a combination of Bondle users and Email Participants in a conversation and interact with them seamlessly

  • Changes to existing Bondle users

– Bondle users will no longer receive an invitation email when you are invited to a new conversation. However, you will receive an in-app notification

– If you are not logged into Bondle and have received an invite, you will receive an email that outlines the “Unaccepted invitation”

  • Tasks and Email Participants

– Tasks cannot be assigned to Email Participants

– If a task is assigned to a Bondle user who has enabled Email communications then they will be notified about the task only when they log into Bondle or via the task reminder email that will be sent out 24 hours prior to the due date (if one is set).