ASAPP Messaging
ASAPP Messaging Updates - Customer Channels
New updates and improvements for ASAPP Messaging - Customer Channels
2024 - Form Messages for Apple Messages for Business
ASAPP enables Form Messages, a native Apple Messages for Business (AMB) format that replaces Omniforms (link to a web form) with a rich, multi-page interactive experience. You can gather customer information through customizable forms that present a single field per page and let your customers review their entries before submitting—all without leaving the Apple Messages application.This enables you to deliver a more seamless and aesthetically pleasing experience for your customers, consistent with other Apple applications.
How It Works
How It Works
How It Works
Watch the video walkthrough below to learn more about Form Messages:Supported Forms
When a form is sent to a customer in Apple Messages for Business, supported forms will display as a Form Message, which has a single form field on each page and allows the customer to review their form entries before submitting.Examples of supported form field types include:- Text
- Name
- Location
- Date
- Phone Number
- Numbers
- Selectors
Unsupported Forms
Customers will be sent an Omniform rather than an AMB Form Message if one of the following is true:- The customer is not on an iOS version that supports Form Messages
- It is a Secure Form
- The flow node is configured to have the form disappear when a new message is sent
- There are more than seven fields in the form; this limit exists because there is a known AMB Form Messages issue that requires a customer to start over if they background the Messages app while filling out a form and then return back to it
- Any field has a prefilled value
- Any field has password masking
- If the form has more than one submit button
- The form contains a scale, paragraph, or table field
Form Messages for multilingual forms are not yet supported. If using a Spanish Virtual Agent, Form Messages are not available.
FAQs
- Why did I have to start filling out my form from the start after leaving and coming back to it?
- Can I enable/disable an individual form to be a Form Message?
2024 - WhatsApp Business
ASAPP supports WhatsApp Business as a messaging channel, enabling your customers to interact with virtual agents and have conversations with live agents in their preferred messaging app.This expanded channel support gives you the ability to offer robust messaging experiences to your WhatsApp users, encouraging them to choose messaging more often and have more satisfying interactions in a familiar setting.
How It Works
How It Works
How It Works
ASAPP’s integration with WhatsApp Business supports similar functionality to what is available in other customer channels. At an overview level, see below for supported and unsupported features:Support included:- Automated flows
- Deeplinked entry points
- Free-text disambiguation
- Estimated wait time
- Live chat with agents
- Push notifications
- Secure forms
- End-of-chat feedback forms
- Customer authentication
- Customer history
- Chat Instead entry point
- Customer attributes for routing
- Customer typing preview for agents, typing indicator for customers
- Images sent by customers
- Carousels, attachment, images in automated flows
- New question/welcome back prompts
- Proactive messaging
- Co-browsing
[Integration documentation is published here](./messaging-plat. Reach out to your ASAPP account contact to get started with WhatsApp Business. They can also advise on specific expected behaviors for virtual agent and live chat features in WhatsApp Business as needed.
FAQs
- What are the basic setup steps for WhatsApp Business?
- How will my current automated flows be displayed in WhatsApp Business?
- Will agents know they are chatting with a customer using WhatsApp?
- Where can I learn more about WhatsApp Business?
2024 - Authentication in Apple Messages for Business
Authentication in Apple Messages for Business Feature Release
ASAPP now supports customer authentication in Apple Messages for Business. With this new functionality, customers can securely log in to their accounts during interactions, allowing them to access personalized experiences in automated flows and when speaking with agents.Customer authentication is intended for any interaction where making use of account information creates a better experience for the customer:- Any live interaction with an agent: Enable your agents to greet and validate who they’re speaking with, review historical customer conversations, and quickly reference relevant account attributes.
- Automated flows: Present data related to a customer’s account (e.g., booking details) or take actions on behalf of the customer (e.g., make a payment).
- Reduce the share of interactions that are directed to agents due to customers being unable to access automated flows that require authentication.
- Reduce the share of interactions that are directed to agents due to customers being unable to access automated flows that require authentication
- Expand the share of interactions with agents that benefit from account information and conversation history, reducing effort to identify customers and search for account information
 |  |
How It Works
How It Works
How It Works
User ExperienceOnce implemented, any instance in an ASAPP automated flow that triggers customer authentication today will do so during an interaction in Apple Messages for Business.When this occurs, Apple Messages for Business will ask the user to login via a button. Once the user clicks the button, they will be brought out of the iMessages app and redirected to a webpage/browser window to sign in. Users will have to sign-in with their credentials every time their authentication token expires.ArchitectureUser Authentication in Apple Messages for Business utilizes a standards-based approach using an OAuth 2.0 flow with additional key validation and OAuth token encryption steps.This approach requires companies to implement and host a login page to which Apple Messages for Business will direct the user for authentication.Visit Apple Messages for Business integration guide for more information.Reach out to your ASAPP account team to coordinate on the implementation of customer authentication in Apple Messages for Business.
FAQs
- What are the steps required to implement authentication? This primarily depends on if a suitable login page and token endpoint already exists or requires customer development. Your ASAPP account team can provide exact details on the specifications these must meet. Configuration is required by ASAPP and on the Apple Business Register. Chat flows that use APIs may require modification to match the rendering capabilities of Apple Messages for Business but this can be done incrementally. Testing of the feature can be done in a lower environment prior to production launch. ASAPP implementation time is 6-12 weeks depending on flow complexity, and total customer integration time is dependent on customer dependencies.
-
If our user base has a broad range of device versions and iOS versions, will they all have the same authentication experience? If not, what needs to be done to ensure that they do?
Yes. For iOS versions 15 & 16+, the user experience for authentication will be the same. However, users with devices that run iOS versions earlier than 12 will not be able to access authentication.
From a technical perspective, different token endpoints will need to be supported simultaneously to allow users across iOS versions 15 and 16+ to access authentication. More specifically, distinct endpoints will be needed to support users with iOS versions 15 or 16+, as well as devices running these iOS versions to test.
For iOS versions 16+, ASAPP will soon support Apple’s newest authentication architecture, which we strongly encourage implementing once it becomes available.
- Does authentication happen inline within the chat experience? No. In the current virtual agent experience, a user will see a login button and then be redirected to a webpage to enter their credentials and complete the login action. They will then be automatically redirected to the chat experience within 10 seconds of successfully authenticating.
- How many attempts will a user be given to authenticate? Are there configurable limits to this? This is governed by how many retries the customer login page allows.
-
When is conversation history carried across channels, both from the customer and agent’s perspectives?
- If a customer is authenticated in the Apple Messages for Business channel, they will see their conversation history for previous authenticated Apple sessions but not their history from other channels.
- If during an authenticated Apple session, the customer moves to another channel (e.g. Web SDK) and authenticates, the Apple conversation from that session will appear in the new channel. Additionally, as the customer engages via the Web SDK, agent responses will continue to appear in Apple Messages for Business until the token for the Apple session has expired.
- In all other instances, the conversation history from Apple Messages for Business will not be visible to customers when they start subsequent conversations in other channels.
- From the agent’s perspective, conversation history from all channels is visible in Agent Desk so long as customers have signed in using the same credentials.
2024 - Quick Replies in Apple Messages for Business
Quick Replies in Apple Messages for Business Feature Release
ASAPP’s automated flows support quick replies for customers that use the Apple Messages for Business channel. Quick replies display response options directly in the messaging interface, allowing customers to make an inline choice with a single tap during an ongoing conversation.As in ASAPP’s customer channels for web and mobile apps, quick replies are used to give customers a defined set of response options, each of which leads to a corresponding branch in an automated flow. Key use cases for quick replies in automated flows include the following:- Discovery questions to better specify a customer issue or account detail
- Ensuring the customer’s issue has been addressed by an automated flow
How It Works
How It Works
How It Works
Quick reply support in Apple Messages for Business is expected to function similarly to quick replies in ASAPP SDKs for web and mobile apps, with the following differences:Number of Quick RepliesApple Messages for Business supports a minimum of two quick replies and a maximum of five per node.Push Notification and Selection Confirmation
When quick reply options are sent, users receive a push notification if Messages is not open; the title of the message will be ‘Choose an option’. Once the user selects a response option, Apple displays a checkmark beside text ‘Choose an option’ in the Messages UI. This is a default behavior and is not configurable.Length of Quick Replies
All quick replies will render as a single line of text with a maximum of 24 characters; if the text exceeds 24 characters, it will be truncated with ellipses after the first 21 characters.OS Version Support
Quick replies are supported in iOS 15.1 and macOS 12.0 or higher; prior operating systems will use the list picker interface.
FAQs
- Is there any work required to adapt existing automated flows to support quick replies in Apple Messages for Business?
Once your ASAPP account team completes a small configuration change, all flows configured with quick replies today will automatically use them in Apple Messages for Business for supported iOS and macOS versions.
Flows with nodes that have more than five quick reply options will need to be edited to use five or fewer quick replies - any quick replies in excess of the first five will not be visible in this channel. Flows with quick reply text that exceeds 24 characters will need to be shortened or will be shown with ellipses after the first 21 characters in this channel.
- Can the list picker experience be selected in AI-Console for designated automated flows or are quick replies the only option?
Currently, if quick replies are enabled, they will be the only supported option across automated flows. The list picker experience will be used for older versions of iOS and macOS.