Plan the anatomy for your Interactive Communication
This tutorial is a step in the Create your first Interactive Communication series. It is recommended to follow the series in chronological sequence to understand, perform, and demonstrate the complete tutorial use case.
The first step in planning an Interactive Communication is to finalize the content of the Interactive Communication. Subject matter experts from departments such as legal, finance, support, or marketing can help you in finalizing the content. After the content is finalized, you must analyze it to identify the various asset types that are required to create the Interactive Communication.
An interactive communication includes the following elements:
Static text mostly includes the parts of the interactive communication that are generic in nature and are included in communication to all the customers. For example, header, footer, salutation, or disclaimers.
Data sourced from a backend system (form data model) is customer-specific and is dynamically merged with the interactive communication. For example, the policy number or address can be sourced using form data model.
Layout or templates for the Print and Web version of the Interactive Communication.
Order in which the various text paragraphs appear in the Interactive Communication.
Data entered by a frontline employee (Agent UI) who is customizing the communication before sending it out. For example, the payment due date.
Conditional data that gets populated based on predefined conditions. For example, the date when the interactive communication is generated.
Images stored in a repository, such as logos and signature images. Images such as corporate logos would appear in most or all interactive communication.
Charts and tables required to simplify the representation of complex data in an Interactive Communication
Once you have finalized the content and elements that are used to create your Interactive Communication, you can create an anatomy of the Interactive Communication. The anatomy must have the details listed in the Planning Considerations section. Based on our use case, the following is an example of an anatomy of the monthly bill that a telecom operator sends to its customers.
The anatomy includes data with the following modes of input:
In each section, the text in bold represents static text. The database includes customer, bills, and calls tables. A form data model can receive data from any of these tables. For more information, see Create form data model.
The following table illustrates the data source for each field in the anatomy of Interactive Communication:
Section | Static text | FDM | Agent UI | Images |
Bill Details | Invoice No Bill Date Bill Period Your Plan |
Value for Your Plan field Table - customer |
Values for the following fields:
|
-- |
Customer Details | Place of Supply State Code Mobile Number Alternate Contact Number Relationship Number Number of Connections |
Values for the following fields:
Table - customer |
Values for the following fields:
|
-- |
Bill Summary | Previous Balance Payments Adjustments Charges current bill period Amount Due Due Date |
Value for the Charges current bill period field Table - bills |
Values for the following fields:
|
-- |
Summary of charges | Call Charges Conference Call Charges SMS Charges Mobile Internet Charges National Roaming Charges International Roaming Charges Value Added Services Charges Total Charges TOTAL PAYABLE Condition on the Value Added Services Charges field |
Values for the following fields:
Table - bills |
No fields | -- |
Itemised calls - Outgoing | Column names:
|
All values Table - calls |
No fields | -- |
Pay Now | -- | -- | -- | PayNow |
Value Added Services | -- | -- | -- | ValueAddedServices |