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

You can set BCC recipients in the trigger settings and send a copy of the email to a set of specified email addresses whenever an email is sent to a customer.

If you need to archive every email sent out of the Blueshift platform, Blueshift allows you an automated way of doing so via the BCC settings on the email adapter config screen.

You can choose to BCC your message either natively or as a separate message

  • If you choose to BCC the email as a separate message:
    • It will be counted as an additional message and will double your send cost
    • Any campaign engagement stats associated with these BCC sends would be distinct from the actual campaign engagement stats. 
  • If you choose the native BCC option:
    • You will be paying for just one message. 
    • Any engagement with the BCC message would be indistinguishable from any engagement with your original message and will be included in your original campaign stats. 

Contact support@blueshift.com to determine the right BCC option for your account.

email_bcc.png

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.

email_copy_s3.png

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.

email_copy_webhook.png

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.

Was this article helpful?
0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.