As a marketer, you might want to archive the exact message that you have sent to your customers so that you can refer to the message in case a customer reaches out. You might also want to archive messages for compliance and for keeping records.
Blueshift offers you several different ways of archiving outgoing messages for future use.
- BCC feature for Emails
- Archive to an S3 location (Emails, SMS, and Push)
- Archive to a webhook location (Emails, SMS, and Push)
- Archived SMS messages as part of campaign activity reports
You can also send a blind copy (BCC) of every email sent to an internal recipient so that you can maintain a record of every email sent to every customer. You can learn more about the different types of BCC options offered by Blueshift here.
Archive to an S3 location
Blueshift offers integrations using Email, Push, and SMS CSV adapters. The CSV adapter exports a message into a CSV file in your S3 bucket instead of actually sending it to the customer. You can set up such an integration and in your campaign journey use such a trigger immediately after the messaging trigger (i.e. as a daisy chain) without adding any delay or filter criteria. In this way you can send an exact copy of the message sent to the customer to an S3 folder.
Important: This doubles the message volume and as a result doubles associated costs.
Archive to a webhook location
Blueshift offers integrations using Email, Push, and SMS webhook adapters. You can set up such an integration and in your campaign journey use such a trigger immediately after the messaging trigger (i.e. as a daisy chain) without adding any delay or filter criteria. In this way you can send an exact copy of the message to a dedicated API endpoint.
Important: This doubles the message volume and as a result doubles associated costs.
SMS copies in Campaign Activity Reports
If you are running SMS campaigns, you might want to retain copies of all SMS conversations, sent to and from customers, for regulatory reasons.
Outgoing messages
The campaign activity reports capture the message details for every 'sent' event for the SMS channel. These campaign activity reports can be exported to your S3 location or to Snowflake. By saving these message details, you can retain a copy of the exact SMS notification you sent to a customer.
These message details are captured via the following extended attributes:
- sms_message: The contents of the SMS or MMS message.
- sms_subject:The subject line for an MMS message.
- media_url: The URL of the media attachment in an MMS message.
Inbound messages
If you are using 2-way SMS messages, and a customer replies to an SMS campaign, the customer's reply is captured as an Inbound Message (bsft_inbound_message) event on the customer profile.
- You can export this SMS Inbound Message event as part of the campaign activity data from the Account Settings > Campaign Activity Export tab.
- The SMS Inbound Message event is also saved in the Amazon S3 bucket at the following location: bsft-customers/<site name>/events/inbound_message/<yyyy>/<mm>/<dd>
You can also view the inbound messages from your customers on the customer profile screen.
Comments
0 comments