Communication & EngagementPurpose
1.2. Centralize communication to reduce information gaps between property management and occupants.
1.3. Support compliance with regulatory requirements for resident notification.
1.4. Streamline operational workflows by automating alert delivery across multiple channels (email, SMS, push, in-app).
1.5. Facilitate acknowledgement tracking and response management for critical updates.
Trigger Conditions
2.2. Modification to digital policy documents in document management systems.
2.3. Calendar events for scheduled maintenance or inspections.
2.4. Automated risk or incident detection (e.g., fire alarm, security breach).
2.5. Periodic scheduled reminders (e.g., annual policy changes, lease renewals).
Platform variants
• Feature/Setting: SMS API; configure event webhooks to trigger POST requests with alert text and recipient numbers.
3.2. SendGrid
• Feature/Setting: Email API; use dynamic transactional templates triggered via API on alert events.
3.3. Slack
• Feature/Setting: Incoming Webhooks; create channel-based notifications using blocks for formatting policy changes.
3.4. Microsoft Teams
• Feature/Setting: Teams Bot Framework; configure bot to send proactive messages to users or channels on building update events.
3.5. Mailgun
• Feature/Setting: Messages API; send batch email notifications to tenant groups; use log events for delivery tracking.
3.6. Pusher
• Feature/Setting: Channels; push real-time notification events to resident-facing web/mobile apps.
3.7. Firebase Cloud Messaging
• Feature/Setting: Send notification messages to registered user devices on relevant triggers via FCM API.
3.8. OneSignal
• Feature/Setting: REST API; segment users by role/unit and push targeted alerts instantly.
3.9. PagerDuty
• Feature/Setting: REST Events API; send critical incident alerts to on-duty staff via mobile push/SMS/email/call.
3.10. HubSpot
• Feature/Setting: Workflow Automation; configure custom workflows to deliver policy updates to contact lists triggered by property management actions.
3.11. Zendesk
• Feature/Setting: Triggers & Automations; auto-generate tickets and outbound notifications on building update events.
3.12. Outlook/Office 365
• Feature/Setting: Mail Send API (Microsoft Graph); push alert emails to distribution lists.
3.13. Zapier
• Feature/Setting: Zaps; configure multi-platform alert streams (e.g., trigger SMS via Twilio, email via Gmail).
3.14. Google Workspace Gmail
• Feature/Setting: Apps Script/SMTP relay; automate group email delivery when drive documents or calendar events change.
3.15. Telegram
• Feature/Setting: Bot API; broadcast policy updates as messages to tenant chat groups.
3.16. WhatsApp Business API
• Feature/Setting: Send Message function; deliver building updates as template or session messages.
3.17. Intercom
• Feature/Setting: Outbound Messages; automate push or in-app notifications on announcement publication.
3.18. Salesforce
• Feature/Setting: Process Builder or Flow; auto-send policy change communications to residents’ records.
3.19. Discord
• Feature/Setting: Webhook; post announcements in specific servers/channels for resident engagement.
3.20. Notion
• Feature/Setting: API Update/Watch; trigger alert on page or database updates, delivering notifications via webhook.
3.21. Monday.com
• Feature/Setting: Automation Recipes/Webhooks; alert residents and staff based on board item changes for building events.
3.22. Asana
• Feature/Setting: Rules; automatically notify assigned users for updated facility or community policies.
Benefits
4.2. Ensures consistency and reliability in message delivery across channels.
4.3. Enhances response to time-sensitive building or policy events.
4.4. Centralizes alert management for audit and compliance visibility.
4.5. Enables multi-language and tailored communications per resident segment.