Kaleyra.io Campaigner

Enhancements

• Hidden the Import from Directory option for WhatsApp campaigns if the campaign is created by a user with a WhatsApp-Only role.
• Enabled the Filter functionality within the Import from Directory option for WhatsApp Campaigns.
• Added additional information about SMS Campaign Failures on the SMS Campaign Listing page.

Bug Fixes

• Corrected an issue that was preventing users from executing SMS Campaigns with a Draft status.
• Corrected an issue with the mapping for SNDR-NT-MTCH for the SMS Replay Campaigns feature.
• Corrected an issue where WhatsApp Campaigns could be launched with missing parameters.
• Improved validation to ensure the same Campaign can not be submitted multiple times.
• Corrected an issue where the SMS campaigns were stuck in an In Progress state when the batches associated with the campaign were deleted.
  The processing works as follows:
  • You can delete a scheduled Campaign entirely as long as the Campaign has not started processing (that is, the first batch has not started processing).
  • If a scheduled Campaign has started processing, you will not be able to delete the Campaign entirely; You will be able to delete batches, but
    • You cannot delete a batch once it has started processing.
    • You cannot delete the last batch.

Enhancements

• Enabled variable mapping between WhatsApp contact files and templates as part of the contact upload step in WhatsApp Campaigns.
  • Includes User Interface labeling improvements for Callback URL and Default Website URL Path fields in WhatsApp campaigns, so users know that these are default (aka static) values.
• Enabled XLSX files support for contact uploads.
• Enabled additional (regional) language support for Voice campaigns using the Text-to-Speech function.

Bug Fixes

• Corrected an issue where the Exclude option was automatically enabled when using Directory in SMS Campaigns.
• Corrected an issue where the contacts were not displayed when importing from Directory with pagination in SMS Campaigns.
• Modified the handling of contacts being created in the Directory as part of security improvements.
• Corrected an issue preventing users from searching the country by typing into the Country code drop-down menu.
• Corrected an issue with the City filter in the Import from Directory in SMS Campaigns.
• Corrected an issue with the batch label display in split WhatsApp Campaigns.

Enhancements

• The Sub-accounts feature has been enabled to launch WhatsApp campaigns.
• The Search and Filter options have been enabled in the Import from Directory option for Voice campaigns.
• The Upload .csv/Excel option has been enabled for Voice campaigns.

📘

Notes:

• There will be a maximum default limit of 100,000 contacts per campaign. The maximum default limit will be displayed in the Import Contact section along with a tool-tip.
• If an uploaded file exceeds the default limit, you will not be able to proceed with your campaign. You must restart the campaign and upload a file with fewer than the maximum limit displayed.

Bug Fixes

• Corrected an issue with WhatsApp campaigns where users were unable to continue their campaign if the number of contacts uploaded was equal to the tier limit.
• Corrected an issue with adding contacts to the Directory.

New Feature

• Enabled the Schedule for Later feature for WhatsApp Campaigns in Kaleyra.io. For more information on the Schedule for Later feature, see the Review and Send section of the Launch WhatsApp Campaign page.

Enhancement

• Reduced the internal interval for batching from 15 minutes to 5 minutes for Campaigns with more than 1 million contacts (regardless of the communication channel).

New Features

• Deployed WhatsApp Campaigns in Kaleyra.io. WhatsApp Campaigns allows you to send bulk WhatsApp messages to your worldwide end-users. To use WhatsApp Campaigns following are the prerequisites:
  • WhatsApp Business Account (WABA)
  • A phone number associated with the WABA
  • An approved message template
• If you want to manage conversations with end-users, you will need to configure a chatbot. It is recommended to implement STOP or OPT-OUT options in the Chatbot to remain in compliance with Meta's consent requirements. Following is the list of the features/functions that are available as part of this release:
  • Launch a campaign for a selected WABA ID. The templates and "from number" for the campaign will be those associated with the selected WABA ID. If your account is not active (that is in grace period status), still you will not be able to submit a campaign.
  • Compose the campaign by providing a title and selecting a template. Based on template selection, additional fields may be required.
    • Templates with a video require a video file to be uploaded. Supported file types are mp4 and 3gp. The maximum allowable size is 16 MB.
    • Templates with an image require an image file to be uploaded. Supported file types are jpeg and png. The maximum allowable size is 5 MB.
    • Templates with a document require a document file to be uploaded. Any valid MIME-type file will be supported. The maximum allowable size is 100 MB.
    • (Optional) You can enter a callback URL, where the statuses of WhatsApp messages are posted.

📘

Note:

A WhatsApp message has multiple statuses (for example, a successful WhatsApp message that is read by the end-user will have three statuses: Sent, Delivered, and Read).

• You can set the audience for the campaign by setting the "from number" and importing contacts. You are responsible for ensuring that they have received prior consent (also known as OPT-IN) from the numbers to which they are delivering messages. You can import the contacts any one of the following ways:
  • Upload
  • Import from Directory
  • Copy & Paste

📘

Note:

If the number of contacts identified exceeds the daily send limit for the WABA phone number, customers will not be able to launch the campaign.

• Review and then send the campaign by confirming the total recipients and estimated cost before launching the campaign. The estimated cost is based on the number of contacts uploaded and the country code for those records. The estimated cost puts a hold on the funds for customers in a pre-paid model. This ensures you have enough credit to run your campaigns. Actual deductions will be applied based on the message type and session statuses. For example, messages in an existing session are not billed and therefore will not get deducted. When the campaign is closed, final deductions will be made and the account will be credited for any messages that were not deducted.
• After launching the WhatsApp campaign, you can view the launched campaigns and their relevant statuses from the campaign list page. The following are the WhatsApp campaign statuses:
  • Submitted - Messages submitted to Meta
  • In Process - Messages are being sent from Kaleyra to Meta
  • Completed - All messages have been sent and statuses for each returned OR 3 days have passed since the launch of the campaign
  • Failed - Messages were unable to be submitted to Meta
• Reporting related to launched campaigns can be viewed from WA Channel Analytics.

Bug Fixes

• Corrected an issue that caused a delay in loading the directory and retrieving contacts in the directory.
• Corrected an issue with the select all feature in the directory for WhatsApp campaigns.
• Corrected an issue where customers could delete campaigns that were in In Progress status.

Enhancements

The following are changes made to the handling of the Set Default Variable feature:

• Enabled the support for setting variables identified by using { }.

  📘

  Note:

  Variables identified using the @ symbol was previously supported and will continue to be supported.

• Enabled support for adding new variables and setting default values ​​for newly added variables in Replayed Campaigns.

New Feature

• You can now set default values ​​for variables in SMS campaigns.

Bug Fixes

• Corrected an issue where variables were not populated if entered before the source file was uploaded.
• Corrected an issue where the voice campaign listing page was blank after returning to the page from the breadcrumb path.
• Corrected an issue that enabled CSV injection of malicious content.

Bug Fixes

• Corrected an issue where the SMS campaign estimated cost was not updated when additional contacts were added.

Bug Fixes

• Corrected an issue with the Variable Replacement Preview in Replayed Campaigns.

New Features

• Added variable replacement preview capability. For messages with dynamic variables, you can preview a sample message where the variables are replaced. This enables you to verify the message content is correct and satisfactory before sending it.

Enhancements

• Modified the newly launched Campaign Replay functionality. Earlier, the replay functionality was only available 3 days from the initial Campaign submission. Now, the waiting time has been reduced from 3 days to 1 day. Since Kaleyra may not have all DLRs before 3 days, the system displays a message advising you to wait for 72 hours for those DLRs to get updated. If you want, you can choose to continue without waiting for 3 days.

Bug Fixes

• Fixed an issue causing editing contacts in the Directory in the IN pod.

New Features

Added a Campaign Replay option for SMS Campaigns. The feature allows you to re-send a previous campaign to a selected set of original recipients based on their message delivery status.

The Replay Campaign feature will:

• be available from 3 days of Campaign submission to 30 days from Campaign submission (Waiting 3 days ensures all DLRs have been received).

• pre-populate Campaign details from the original Campaign, you can:

Enhancements

• Added visual page loaders to Voice Campaign pages to more clearly indicate when pages are loading.

Bug Fixes

• Corrected an issue that prevented Submitted Campaigns from showing on the SMS page.
• Corrected an issue that prevented Directory Contacts from showing for SMS Imports.