SaaS Message Templates with Channel-Specific Content Fallbacks
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Developers face challenges in creating and sending messages across various communication channels due to differing formats and rules, requiring multiple message send requests and inefficient use of resources, with message failures occurring when channels do not support content types.
Innovation Solution
Implementing a content resource creation API that allows developers to create a single message content resource template in a common format, which is translated to specific formats for different communication channels, and includes dynamic variables for reusability and fallback content types.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If developers create separate message send requests for each communication channel, then message sending can be achieved across different channels, but the complexity of the system increases and resource usage becomes inefficient
Solution Approach 1:
The patent implements a universal message template system that can be used across multiple communication channels (SMS, MMS, IM, email). Instead of creating separate send requests for each channel, a single message template with channel-specific parameters can be reused across all channels, reducing system complexity while maintaining adaptability.
Solution Approach 2:
The message system is segmented into two independent components: message templates (content definition) and send requests (delivery execution). This separation allows the template to be defined once and reused across multiple channels through different send requests, reducing complexity while maintaining versatility.
2Adaptability or versatility
If developers create separate message send requests for each communication channel, then all channels can be supported, but the time and resources required for message creation increase
Solution Approach 1:
The patent implements preliminary action by allowing message templates to be pre-defined and stored in the system before actual sending. The template includes all content elements (text, media, buttons) that can be reused across multiple channels. When sending is needed, the pre-defined template is simply referenced and transmitted through the appropriate channel, dramatically improving productivity.
Solution Approach 2:
The patent enables copying of message templates across different communication channels. A single template definition can be copied and reused for SMS, MMS, IM, and email channels by simply specifying different channel parameters in the send request, eliminating the need to recreate messages for each channel and improving efficiency.
3Ease of manufacture
If message content is created without considering channel compatibility, then development is simpler, but message failures occur when channels do not support the content types
Solution Approach 1:
The patent implements parameter changes by allowing the same message template to dynamically adapt its content based on the target communication channel. The system automatically adjusts parameters such as media inclusion, character encoding, and supported content types according to channel capabilities, maintaining both development simplicity and delivery reliability.
Solution Approach 2:
The patent introduces an intermediary layer (the message template system with channel compatibility checks) between the developer and the communication channels. This intermediary automatically handles channel-specific requirements and compatibility issues, allowing developers to write simple, universal templates while ensuring reliable delivery across different channels through automated parameter adjustment and validation.
Data Source
AI summary
A first request to create a content template for messages to be sent via a plurality of communications channels via a software-as-a-service (SaaS) platform is received via a first application programming interface (API) call. The first request specifies an order of content types identifying a first content type and at least one alternative content type that is to be included in a message sent to a communication channel among the communication channels if the first content type is not permitted by the communication channel. The content template that is associated with the order of content types is created. The content template is stored at the SaaS platform.