Here's an illustrative example of what happens when an email is sent from the communication center.
Context: Marcus is looking to send an email to his members.
Step 1: Marcus sends an email to an email group.
Email Masking: Marcus' true email ID is hidden ("masked") to protect his privacy and to authenticate the email's origin.
Recipient's Perspective: Emails appear to come from a trusted Almabase-associated domain, such as marcus@alumni.regencyacademy.org.
Note: This also allows any replies to the email to be tracked.
Step 2: Tim replies to Marcus
Almabase Routing: Tim's response is channeled through Almabase, employing unique IDs for Marcus and the specific email thread.
Directing to Marcus: Security checks are performed before Tim's response is sent on to Marcus' actual email address, like marcus@gmail.com.
Step 3: Marcus replies to Tim
Marcus' subsequent replies are also concealed and routed through the Almabase platform.
Step 4: Going back and forth on email.
The exchange of emails continues securely under Almabase's supervision, ensuring the exchange remains private and verified.
Assurance of Security
Authentication Checks: Only emails from recognized database senders are relayed; others are intercepted to prevent unauthorized communication.
Authority Checks: Should an unrecognized sender attempt to connect, Almabase intervenes with an automated message about the sender's insufficient privileges.
The platform allows the customization of the sender's email ID and username in automated emails for consistency and to uphold institutional branding. Find out more about Primary Communication ID here.
Please write to us at help@almabase.com or through the Intercom Chat 💬 if you have any queries or concerns😄.