Separate Message Templates for Email and SMS in Team Notifications Problem

Team notifications currently use the same message template for both email and SMS. This limits clarity and effectiveness, as SMS and email are consumed differently and serve different purposes in operations.

SMS messages need to be short, actionable, and time-sensitive, while emails are better suited for detailed context, instructions, and summaries. Using a single template for both often results in SMS messages that are too long or emails that lack useful detail.

Proposed Solution
Allow operators to create separate, channel-specific templates for team notifications:

• One template for SMS

• One template for Email

Each template would support the same variables (property name, date, time, notes, etc.) but be independently editable to match the communication channel.

Use Cases

• SMS: “Clean today at Gazeley Gem, start after 10:30am. See app for details.”

• Email: Full task details, notes, access instructions, and weekly summaries.

Why This Matters

• Improves clarity and response rates

• Reduces SMS overload and truncation

• Enables richer operational communication via email

• Aligns messaging with real-world team workflows

Outcome
Teams receive the right level of information in the right channel, reducing confusion and improving task execution without increasing notification volume.