Release Note: 1.253

The latest package version 1.253, includes the following updates:

Previously, the "From" address was blank when sending emails through a drip campaign. We have fixed this issue, and the "From" address will now be displayed in all emails sent through a drip campaign.

  • Previously, verifying a phone number would take some time, and once the verification was complete, the details could be updated. However, with the new functionality, if a user changes the value of a particular field (such as the phone number) and re-verifies the record, the latest details of the verified phone number will be instantly updated. The "Phone Status" field will show "Valid" and this information will be displayed in the Verify the Phone History.
  • Below screenshot can show how this functionality works:
    Let us update the Mobile number in respective field and then click to save in order to save the details.

    Fig 1: Verify the Phone
  • After saving the changes, the user needs to click on the button “Verify the Number”.

    Fig 2: Verify the Number in dropdown list
  • After Verification User can check the Status in respective field (In this case we check the field “Phone Status” )

    Fig 3: Phone Verified Status
  • You can now see the ‘WhatsApp profile name’ field on the SMS History.
  • WhatsApp providers will provide us with a "profile name" that will be saved in the SMS history. When the user sends a message to the WhatsApp number, the message will be received with the associated profile name.
  • Use case: When converting leads, we will map the SMS history field to the lead's name during the lead name mapping process. We will continue this mapping process during the conversion
  • Previously, if you chose a channel (such as SMS/MMS, or WhatsApp), it would show all templates in Template Folder picklist field, but now it can show only relevant template according to selected channel.
  • You can also choose different templates for different channels by going to the "Create SMS" page and selecting the template you want to create. We can select multiple channels for a particular template.

    Fig 4: Channel and template
  • This functionality allows users to include your signature only in bulk messages, such as in List View, SMS from Reports, Campaign, etc.

    Fig 5: Enable user signature

    Fig 6: Bulk messaging
  • Previously, only the user signature was displayed, but now you have the option to enable the functionality by enable the checkbox named as “Enable User Signature” in SMS General settings to send the record owner's signature.
  • This functionality won't work in the case of speed boosting and cross-automation.

Previously, we displayed a wide range of objects on the object setup page, which may not have been relevant to all clients. However, we have now streamlined the standard objects and reduced their number to ensure that only the most commonly used objects are displayed, providing a more focused and efficient setup experience.

Fig 7: Add objects
  • While scheduling a message, the message will be sent immediately if the time period is too short . We providing an option “Real Time Scheduling” in “General Setting” to set the respective value where the default time is set to 5 min.
  • Note- In case if user set the default value to 0 then this functionality will stop
  • This feature is only for single and automated messages

    Fig 8: Real Time Scheduling
  • Previously, when we sent a message using "all user assigned numbers," the next question triggered from iText would be automatically owned by the user who clicked on the IO (Incoming/Outgoing) button, instead of the user who sent the first outgoing message from iText. This issue has now been fixed.
  • A source field has been added for subsequent questions sent through iText. It will automatically consider the user who sent the first message as the source field, ensuring that subsequent questions are owned by the correct user.

Previously, sending voice messages was limited to real-time. Now, you can also schedule your voice drop, just like messages.

Fig 9: Schedule voice drop

  • This feature will automatically mark incoming messages as "Read" once a user sends an outgoing message in response to the same conversation thread.
  • To enable this functionality, enable "Mark Incoming as Read" in the General Settings.

    Fig 10: Mark incoming as read

Previously, in the conversation view, we could only see the number in the "To” field. Now, we have added the option to display the API associated with the number. For instance, if the number is a mobile number, the label "Mobile" will be displayed, and if it's a landline or home phone, the appropriate label will be displayed instead.

Fig 11: Number Label

Previously, we created custom settings in the client's org that only supported five formats of numbers. Now, the "General Setup" object supports more than five formats, providing greater flexibility in number formatting.

If two contacts have the same number, one contact's number is marked as a duplicate to prevent the same number from receiving a message twice.

Previously, we supported attachments up to 4.5 MB. Now, we have increased the maximum size of attachments that can be added to your message.

Fig 12: File attachment

  • New features have been added to the field mapping component when creating a new record. You can now view, edit, and delete a new record using a drop-down list (as shown in the image).
  • Use case: Whenever a user receives an incoming message, Case and Lead records will be automatically created using our "Field Mapping" data.

    Fig 13: Field Mapping

  • New Button
  • When a user clicks the New button, a pop-up window appears. The user needs to choose object accordingly and clicks the Save button.

    Fig 14: New field mapping
  • Now user needs to fill the required details accordingly.

    Fig 15: New field mapping details
  • If user wants to add field then they just need to click on the add field button.

    Fig 16: Add field button in New field mapping
  • If a number has been blacklisted, it will not be possible to send messages or voice notes to that number. If you attempt to send a message to a blacklisted number, an error pop-up will be displayed (as shown in the figure). The user can view the list of blacklisted numbers in SMS General Settings.
  • Note- If a user tries to add multiple numbers, some of which are blacklisted, the message will be sent to the non-blacklisted numbers. However, for the blacklisted numbers, the message will not be sent, and instead, an error message will be generated, creating an SMS History record with details of the failed delivery.

    Fig 17: Blacklist message

We have introduced three new channels with SMS Composing Module, i.e. WhatsApp, SMS, and VoiceMail (as shown in screenshot).

Fig 18: SMS Composing Utility

To send a message or voice drop through Apex Class in Process Builder, you must provide the necessary information in the designated fields, as illustrated in the image below.

Fig 19: Apex Class: Process Builder

You can now add keywords to the Restricted Keywords section in the SMS Setup under General Settings. Once added, these keywords will be prohibited from being sent to customers.

Fig 20: Restricted Keywords

  • Previously, if a number was not assigned to a user, it was not possible to send messages. However, with the introduction of the "Auto Assign Numbers" feature, this limitation has been addressed. This feature is now enabled by default.
  • With the new feature, when a record is updated, the number is automatically assigned to the user. This applies only to automation via process builder and flow.

    Fig 21: Auto Assign numbers

Release Note: 1.246.8

The latest patched version of 1.246, which is patch 1.246.8, includes the following updates:

Previously, Unicode character records were manually created in our organization. However, we have now introduced a new record type in the production org. The record type is a unique code character on the general setup object, where both Name and CC address are used. The CC address will be treated as a replacement for the name that needs to be replaced.

  • Previously, SMS templates would not work if the selected object in the template had more than 1,000 fields. However, this issue has been resolved and now the templates will work regardless of the number of fields in the selected object.
  • We have added a new feature to the SMS templates. We only displayed a few standard objects in the SMS template and there was no way to add any additional standard objects to the SMS template object picklist. However, this issue has now been resolved. To add a new object to the picklist, we simply need to add that object to the Object Setup page.

We faced an issue with WhatsApp outgoing messages where we sometimes received parallel hits for message delivery and recipient read status. At that time, only one checkbox would get updated, either the delivery or read checkbox. However, it has now been fixed

We were facing an issue with the schedule drip action due to different time zones, but it has now been fixed.

360 Sms App Whats App logoWhatsApp Live Chat