1. Overview

The Bulk Actions Send Messages feature in Kemicard Console enables administrators to deliver push notifications to multiple pass holders simultaneously. This powerful tool streamlines communication by sending messages directly to users’ mobile wallets, ensuring instant delivery of important updates, announcements, or alerts.

Key Benefits:

• Send push notifications to multiple pass holders at once

• Use Salesforce reports to target specific audiences

• Automate message delivery to save time

• Track message delivery through Salesforce Activity timeline

• Real-time validation ensures data integrity

2. Accessing Bulk Actions – Send Messages

To access the Send Messages bulk action feature:

1. Navigate to Salesforce and log in to your Kemicard account

2. Click on the “Kemicard Console” tab in the main navigation bar

3. In the left sidebar under “Kemicard Admin”, locate and click on “Bulk Actions”

4. You will see the Bulk Actions homepage with two main options:

   • Generate Passes – Generate multiple passes at once using information from reports

   • Send Messages – Quickly compose and deliver Push Messages in bulk from a report

5. Click on the “Send Messages” card to begin the message sending workflow

3. Step-by-Step Workflow: Sending Messages

The Send Messages workflow consists of four clear steps, guiding you through message composition, report selection, review, and delivery confirmation.

3.1 Step 1: Compose Message

The first step involves composing the push notification message that will be sent to pass holders:

1. After clicking “Send Messages”, you’ll see the Configurations screen

2. The progress indicator shows you’re on step 1 of 4

3. In the “Message” field, type your notification text

4. Example message: “Important Update: Your pass has been successfully generated! You can now add it to your mobile wallet and enjoy seamless access to all event facilities. Thank you for being part of our community!”

5. The same message will be delivered to both Apple Wallet and Google Wallet users

6. Click “Next” to proceed to report selection

Best Practices for Message Composition:

• Keep messages concise and actionable

• Include relevant information about why users are receiving the notification

• Use clear, professional language

• Mention specific actions users should take if applicable

• Consider the character limits for mobile notifications

3.2 Step 2: Select Report and Validate Data

This step involves selecting the Salesforce report containing pass holder data:

1. The screen changes to “Report Selection & Validation”

2. In the “Select Report” field, type the report name to search

3. Example report: “Contacts for Pass Generation Custom”

4. Select the report from the dropdown

5. Once selected, two additional fields appear:

   • “Select the record id column from report” – Typically “Contact ID” (default)

   • “Select the template column from object” – Choose the appropriate template field (e.g., “Membership Pass Template”)

6. The system performs automatic validation with two key checks:

   • Object Match: Verifies that the object configured in the template matches the object associated with the selected report (indicated by a green checkmark)

   • Id Field Present: Confirms that the record ID column for the object configured in the template is present in the selected report (indicated by a green checkmark)

7. Both validation checks must pass before proceeding

8. Click “Next” to continue to the review step

3.3 Step 3: Review and Confirm

The final step before sending messages is to review all configuration details:

1. The “Review” screen displays a summary:

   • Report: Shows the selected report name (e.g., “Contacts for Pass Generation Custom”)

   • Number of Records affected: Indicates how many pass holders will receive the notification (e.g., “1”)

2. Review all information carefully to ensure accuracy

3. If you need to make changes, click “Back” to return to previous steps

4. When ready, click the blue “Send” button to initiate the message delivery process

5. A confirmation dialog will appear:

   • Message: “By initiating this batch, you will send 1 Push Messages to Passes in bulk. In addition, 1 Records of Object can be Updated. Once started, the action cannot be stopped or undone. Please confirm.”

   • Click “OK” to confirm and proceed

   • Click “Cancel” to abort the process

3.4 Step 4: Job Status & Results

After confirming the message delivery, the system processes the batch job:

1. The screen transitions to “Job Status & Result” showing:

   • A circular progress indicator displaying completion percentage (e.g., “100%”)

   • Total Records Processed: The number of records processed (e.g., “1”)

   • Successfully Completed: Count of successfully delivered messages (e.g., “1”)

   • Failed: Number of failed attempts (e.g., “0”)

   • Status: Current job status (e.g., “Processing” or “Completed”)

   • Job Id: A unique identifier for tracking the job (e.g., “707cb000004EbDAAM”)

2. The progress bar fills as the system processes each record

3. When complete, the circle shows 100% and all statistics are finalized

4. A “Send More Messages” button appears, allowing you to send additional notifications

5. The job remains accessible for audit and troubleshooting purposes

Success Confirmation:

• When “Successfully Completed” equals “Total Records Processed” and “Failed” is 0, the delivery was successful

• All push notifications have been sent to pass holders’ mobile wallets

• Recipients will receive the notification on their mobile devices

4. Verifying Message Delivery

After sending messages, it’s important to verify that notifications were delivered and tracked correctly:

4.1 Checking Contact Activity Tab

To verify message delivery on a specific contact:

1. Navigate to the contact record (e.g., Phoebe Buffay – Contact ID: 003cb00000RlAZ4AAN)

2. The contact page opens with Related and Details tabs on the left, and Activity/Chatter tabs on the right

3. The Activity tab displays all communication history for the contact

4. In the “Upcoming & Overdue” section, you’ll see:

   • “Push Notification Sent” – Today

   • “You have an upcoming task”

5. This entry confirms that the push notification was successfully logged

4.2 Viewing Notification Details

To see detailed information about the sent notification:

1. Click on the “Push Notification Sent” entry in the Activity timeline

2. The task record opens, showing:

   • Task: Push Notification Sent

   • Name: [Contact Name] (e.g., Phoebe Buffay)

   • Subject: Push Notification Sent

   • Due Date: [Date notification was sent]

   • Priority: Normal

   • Status: Not Started

   • Created By: [User who sent the notification]

   • Last Modified By: [User]

3. The Comments section displays the actual message content:

   • Apple Message: [Your notification text]

   • Google Message: [Your notification text]

4. This provides a complete audit trail of the notification

5. Best Practices and Tips

Message Content:

• Craft clear, actionable messages that provide value to recipients

• Include specific calls-to-action when appropriate

• Keep messages concise for better mobile readability

• Test message content with a small group before sending to large audiences

• Ensure messages are relevant to the target audience

Report Configuration:

• Create dedicated reports specifically for message campaigns

• Include only contacts who have active passes

• Ensure Contact ID is included in the report

• Test reports with small batches before processing large volumes

• Keep report criteria up to date to reflect current needs

Data Quality:

• Verify contact information is complete and accurate

• Ensure contacts have valid passes before sending notifications

• Check for duplicate records before sending messages

• Clean data regularly to maintain database integrity

Batch Processing:

• For large volumes, consider splitting into smaller batches

• Monitor job status during processing

• Review job ID for troubleshooting if issues arise

• Document message campaigns for future reference

Timing and Frequency:

• Consider time zones when scheduling message delivery

• Avoid sending too many notifications to prevent notification fatigue

• Space out campaigns appropriately

• Track engagement metrics to optimize future campaigns

6. Conclusion

The Kemicard Console Bulk Actions Send Messages feature provides a powerful and efficient way to communicate with pass holders at scale. By following the step-by-step workflow outlined in this documentation, administrators can streamline notification delivery while maintaining data integrity through automated validation.

Key Takeaways:

• The workflow consists of four clear steps: Compose Message, Report Selection & Validation, Review, and Job Status

• Real-time validation ensures compatibility between reports and pass templates

• The system provides comprehensive tracking through job IDs and status monitoring

• Success is easily confirmed through completion statistics

• All notifications are tracked in Salesforce Activity timeline for audit purposes

With this comprehensive guide, you’re now equipped to efficiently send push notifications to your pass holders using the Kemicard Console Bulk Actions feature.