Understanding the Problem

The original flow was an Automation Event Triggered flow with Apex personalization, and the concern was whether adding create consent in the same flow would introduce a delay. The worry was that DC triggered flows have a 15-minute delay while records are being added to DC.

Root Cause of Delay

The root cause of the potential delay is the way DC triggered flows handle record additions, which can take up to 15 minutes. However, Automation Event Triggered Flows do not have this delay, making them suitable for use cases that require immediate action, such as sending transactional SMS.

Using Automation Event Triggered Flows

For emails, Form Triggered Flows (which are Automation Event Triggered Flows) can create the CRM record and consent in the same flow, allowing emails to be sent quickly, typically within 1-2 minutes. This approach can also work for SMS use cases, including transactional SMS, as long as the necessary consent is created in the same flow.

Implementing the Solution

To implement this solution, you can add a create consent action in your Automation Event Triggered Flow, ensuring that the necessary consent is obtained before sending the transactional SMS. This approach eliminates the need for DC triggered flows and the associated delay.

Example Create Consent Action

/* Example Create Consent Action */
// Create consent for transactional SMS
consent = [SELECT Id, ContactId, ConsentDate FROM Consent WHERE ContactId = :contactId AND Channel = 'SMS'];
if (consent.isEmpty()) {
    // Create new consent record
    Consent newConsent = new Consent(ContactId = contactId, Channel = 'SMS', ConsentDate = System.now());
    insert newConsent;
}

Best Practices and Considerations

Heads up: When using Automation Event Triggered Flows for transactional SMS, ensure that you have the necessary consent and comply with relevant regulations, such as GDPR and TCPA.

Checklist for Implementation

Checklist for Implementing Automation Event Triggered Flows for Transactional SMS

• Use Automation Event Triggered Flows instead of DC triggered flows to avoid delays
• Create consent in the same flow as the transactional SMS
• Ensure necessary consent is obtained before sending transactional SMS
• Comply with relevant regulations, such as GDPR and TCPA
• Test your flow to ensure it works as expected
• Monitor your flow for any issues or errors

Frequently Asked Questions

What is the delay associated with DC triggered flows?

The delay associated with DC triggered flows is up to 15 minutes while records are being added to DC.

Can I use Automation Event Triggered Flows for transactional SMS?

Yes, you can use Automation Event Triggered Flows for transactional SMS, as long as you create the necessary consent in the same flow.

Do I need consent for transactional SMS?

Yes, you need consent for transactional SMS, even if the message is transactional in nature.

How do I ensure compliance with regulations?

To ensure compliance with regulations, such as GDPR and TCPA, you must obtain the necessary consent and follow relevant guidelines for sending transactional SMS.