You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When users are building interactions steps in campaigns, the message composer does not do a great job of communicating to the user the differences between SMS and MMS messages and the capabilities of MMS in general. We have some opportunities to improve clarity and communication around the process of crafting messages and guide users toward best practices, especially around training users on MMS.
Context
As a user, I should be able to understand what an MMS message is (and how it differs from a typical SMS) and when I should use it, so that I can make the most of my texting campaigns and of Spoke. I should be able to add images to my messages successfully and confidently.
Goals and Non-Goals
Main goals:
Promote MMS in the UI to be more discoverable - give users the option to add images/media upfront
Communicate the differences between SMS and MMS messages
Give the users additional in-context help to clarify message info (segments, encoding, message type)
Communicate MMS image requirements and limitations in the UI
Non-goals/out of scope for now (negotiable!)
Giving the user the ability to upload an image file from scratch
Screening file sizes and requirements - currently, we just inform and uplift the requirements around them, but can prioritize proactive warnings if we feel it's within scope
This design asks the user to select between SMS and MMS, with SMS selected by default. How do we feel about promoting this? Does it align with how we want to SMS and MMS to be used?
Detailed Scoping and Timeline
The text was updated successfully, but these errors were encountered:
Design doc for review @hiemanshu @politics-rewired/client-success
As far as design, this proposes changes for some wins around usability and clarity, but hopefully isn't blown up scope-wise. But very open to hearing about folks' grander wishlist items that we might be able to incorporate if not during this phase, later on!
Also realizing this has some overlap with #1516 and happy to scope either or combine them if needed (will defer to hiems!)
@kennyycheng this looks amazing! One suggestion from me, when selecting MMS, if we could add an "manage attachment" type button or similar. So we don't need good formatting rules to be setup for the attachment there. And the character count isn't affected by the length of the link.
Overview
When users are building interactions steps in campaigns, the message composer does not do a great job of communicating to the user the differences between SMS and MMS messages and the capabilities of MMS in general. We have some opportunities to improve clarity and communication around the process of crafting messages and guide users toward best practices, especially around training users on MMS.
Context
As a user, I should be able to understand what an MMS message is (and how it differs from a typical SMS) and when I should use it, so that I can make the most of my texting campaigns and of Spoke. I should be able to add images to my messages successfully and confidently.
Goals and Non-Goals
Main goals:
Non-goals/out of scope for now (negotiable!)
#Milestones
#Existing Solution
UI / Proposed Solution
Design doc
Figma Design File
Password: 3Wa@7CQL
Alternative Solutions
Design doc
Testability, Monitoring and Alerting
Cross-Team Impact
Open Questions
Detailed Scoping and Timeline
The text was updated successfully, but these errors were encountered: