April 25, 2024

The Customer Portal UI has been updated for a better user experience. A version of the Home page is provided for both our usage-based customers as well as one for subscribers to SmartProducts.

SmartEngage™ is available to both subscribers and non-subscribers.

Manage your SmartProduct numbers and order numbers without the need for a trunk or routing profile.

SmartProduct subscribers can set up SmartAgent™, SmartOffice™, and SmartWorker™ packages with DID and toll-free numbers for use with your flows to automate your enterprise. Functionality is similar to current usage-based SIP packages. Some limitations apply.

Numbers added to SmartAgent and SmartOffice packages are automatically CPaaS-enabled.

You can check your SmartProduct licenses and allocations right from the Home page.

MMS is now available for SmartCommunicator™, SmartFlows™, SmartEngage™, and APIs. For more information, check out SMS / MMS Message Management.

Important: To avoid having your MMS messages rejected, make sure you (1) keep your message size to 5MB or less for all attachments, and (2) check to make sure the URLs you use for your media go directly to the media file and the URLs are publicly accessible over the internet.All URLs must start with one of the following schemes: http://, https://, or cpaasmedia://.

The new action GenAI IVA is now available in the Intelligent Assistant section of the Actions menu.

• Use this action to incorporate a generative AI IVA (Intelligent Virtual Agent) from the IntelePeer AI Hub into your flow.

• You must have a SmartAgent Diamond or SmartOffice Diamond account to use this action.

You can now send and receive multimedia messages.

• The Inbound SMS action was renamed Inbound SMS/MMS and the Send SMS action was renamed Send SMS/MMS.

• The Send SMS/MMS action includes the Enable MMS check box , which exposes the attachment URL fields. You can include up to five URLs in an outbound message.

• When your flow is triggered by the Inbound SMS/MMS action, two new variables will appear in the Available Variables section for downstream actions:

  • $ISMS_{#}.media_is_present

  • $ISMS_{#}.media_count

    Note: {#} is a placeholder for the automatically assigned action ID number (e.g., $ISMS_6.media_count).

  Note: For both inbound and outbound MMS messages, the MMS file cannot exceed 5 MB.

The following updates were made to SmartProduct functionality:

• When you create a new flow, a SmartProduct Type pop-up appears, where you can select the product type you want to build.

  • Select SmartAgent, SmartOffice, or SmartWorker.

    Note: You will not be able to change the product type later.

  • Depending on the product type you select and your subscription level (e.g., Gold vs. Diamond), some options in the Actions menu will be unavailable.

• Phone numbers cannot be used across all SmartProduct types.

  • A SmartAgent number can only be used with a SmartAgent flow.

  • A SmartOffice number can only be used with a SmartOffice flow.

  • A SmartWorker number can be used with a SmartWorker or SmartOffice flow.

• On the Number assignment page, click the SmartProduct Numbers check box to view your phone numbers associated with SmartProducts. The Product Type column shows the SmartProduct type for each number (i.e., SmartAgent, SmartOffice, or SmartWorker).

  • If you select a number from the table and click the Assign Flow button, a new Product Type column appears on the Assign Flow pop-up. The flows that appear in the pop-up will depend on the SmartProduct type associated with the number you selected. For example, if you select a SmartAgent number, only SmartAgent flows will appear in the Assign Flow pop-up.

• When you assign a number to a trigger action, the new Product Type column appears on the Number Assignment pop-up.

  • The numbers that appear in the pop-up will depend on the SmartProduct type associated with the flow you're creating. For example, if you are building a SmartOffice flow, only SmartOffice and SmartWorker numbers will appear in the Number Assignment pop-up.

• The Deployed SmartAgent table on the Flows page was updated to represent the SmartProducts currently available.

  • The table was renamed Deployed SmartProducts.

  • The silver, Platinum, and SmartEngage columns were removed.

  • The SmartAgent Diamond, SmartOffice Gold, SmartOffice Diamond, and SmartWorker columns were added.

• The SmartAgent Package column on the Flows page was replaced by the Product Type and Product Tier columns.

Note: If you were previously a SmartAgent subscriber, you will automatically be converted to a SmartProduct subscriber (though some limitations apply). If you have existing flows, they will automatically be converted to the appropriate SmartProduct type/tier. The Versions and History sections of your legacy flows will be blank.

Users can now have read-only access to flows.

• Read-only users can view public flows or flows shared specifically with them, but can't make any edits.

• Assign or update user roles to the SmartFlows "read" Access Type via the User Management section of the Customer Portal.

  • From the User Management section, select Roles at the top of the page and click Create New Role. On the pop-up make sure the Services tab is selected and scroll down to find the SmartFlows Service. Deselect the other check boxes so only the "read" option is checked. If any other boxes are selected besides "read". the user will have full access.

    Note: If you want to change an admin user to read-only, you must first remove their admin role.

The following bugs were resolved:

• An issue causing flows triggered by the Schedule action to behave unexpectedly was resolved. Previously, scheduled flows were not executed when expected or were unexpectedly triggered multiple times.

• When the Sensitive check box is selected at the enterprise level, occasionally the Inputs section for the External Web Call action would not display due to concern that sensitive data is included. This issue was resolved, and the owner of a flow can now see the Inputs as expected.

• Previously, time out errors were observed when accessing the flow Version and History sections or Jump From action details. The data now appears as expected, in a timely manner.