LoftOS incorporates a notification e-mail system essential for platform operations. These e-mails, designed to align with your corporate identity, establish a connection between users and the platform's added value and advantages.

Two categories of system e-mails exist. The first group comprises automated e-mails triggered by user actions, including account registration, password reset, event registration, and network invitations.

The second group involves automated notifications about platform events, strategically designed to enhance user engagement. Examples include notifications about new messages, matches, or fresh platform content.

To ensure users stay informed, e-mails promoting new platform content are dispatched every two weeks, automatically notifying users and encouraging their return to the platform.

❓ FAQs

• Which e-mails are sent automatically?

  General Platform Functions

  • Confirm Platform registration
  • Password reset
  • Message Notification
  • Match Mail
  • Confirm Team Member
  • Confirm Second Mail
  • Confirmed Team Member Notification
  • Platform Report
  • Invite Team Member
  • Platform Invitation
  • Platform Access Request
  • Notifications

  Events

  • Meeting Requests
  • Confirm Event Registration w/ matchmaking
  • Confirm Event Registration w/o matchmaking
  • Event Reminder 48h before
  • Event Reminder 1h before
  • Speed-Dating info
  • Speed-Dating release match
  • Speed-Dating no match

  Groups

  • Membership Request for closed Groups
  • Membership rejected
  • Membership confirmed
  • Group Chat Message Notification
  • Group invites (for registered users)
  • Group invites (for non registered users)
  • New Group Admin

  Projects

  • Verification Projectpartner
  • Verification Customer References

  Accelerator/Awards

  • Verification Request Accelerator to Startup
  • Verification Request Startup to Accelerator
  • Verification Request Award to Startup
  • Verification Request Startup to Award

  Investor

  • Verification Request Investor

  Content

  • Reminder offer

  Pipelines

  • Added User To Pipeline Notification
  • Pipeline Invitation Request
  • User Added To Pipeline Notification
  • Card Invitation Request
  • User Added To Card Notification (to Admin)
  • User Added To Card Notification (to User)
  • New Card Added Notification
  • Card Moved
  • Mention In Comment
  • New Comment

  Forms

  • Invitation

• Can system e-mails be sent from my own domain?

  Sending system e-mails from your own e-mail domain is only available for Enterprise packages. Contact your Customer Success Manager (CSM) or Account Executive (AE) if you would like to receive an offer.

  ⚠️ Important Note for European Organizations: Please be aware that GDPR regulations prohibit sending e-mails without User consent. Communication is restricted to the integrated chat or the use of the platform's newsletter logic.

• Can I control which automated e-mails the platform sends to my users?

  Not on a per-event basis. Automated e-mail send triggers cannot currently be configured by admins for individual events.

  • To suppress the automated mails around a specific event, contact your CSM with the affected event URLs.
  • System e-mails cannot be suppressed at all — this includes registration confirmation and password reset, which are required for the account to function.

• Which platform events currently trigger an automatic e-mail?

  The most frequent ones are:

  • registration confirmation
  • password reset
  • direct messages
  • event registration confirmation
  • ticket purchase confirmation (including the invoice)
  • organisation join / approval requests
  • event reminders, 48 hours and 1 hour before the event starts

  The full list per module is in the first FAQ entry above.

• Why aren't attendees receiving event reminder e-mails, or why do they land in spam?

  Reminder e-mails are sent automatically 48 hours and 1 hour before an event starts.

  1. The most common cause of a "missing" reminder is the spam/junk folder. Ask the affected user to check there and, if found, to whitelist the sending address.
  2. Confirm the user is actually registered for the event — reminders only go to registered participants.
  3. If nothing arrived and it is not in spam, escalate it as a delivery bug via the Resource Center with the event URL, the user's e-mail address and the expected send time.