Glossary
Following are common terms and their definitions frequently used in this tutorial.
| Term | Definition |
|---|---|
| agent | The receiving entity for a Messages for Business dialog. It can be a human customer support representative or an automated agent. |
| Apple ID | An Apple ID is the email address that has been preregistered at Apple: https://appleid.apple.com/. The email can be issued by an Apple domain, such as iCloud.com (http://icloud.com/) and apple.com, or a non-Apple domain. |
| bot | An automated agent. |
| business card | Business cards display the global contact details for your business, including your brand or logo, your business phone number, email, website URL, and Messages button. See Business and Place Cards. |
| business ID | Also known as a biz-ID, it is a unique business identifier assigned when Apple Register approves a Messages for Business account. |
| console | The view of a MSP seen by customer service agents. |
| conversation | A long-lived interaction between a unique user Apple ID and a unique business. A conversation may consist of multiple dialogs. |
| CSP ID | A unique customer service platform identifier assigned when Apple Business Register approves a CSP account. Now called MSP ID. |
| CSP Secret | A unique secret retrieved from Apple Business Register along with the CSP ID. |
| destination ID | A field describing a messages destination. It is the user’s opaque ID for messages sent to the client device or the Business ID for messages sent to the MSP. This field appears twice: once in the HTTPS header of the message as Destination-Id and once encrypted in the body as destinationId. |
| dialog | A set of interactions between a unique user Apple ID and a unique bot or customer service representative that is bound in time. For example, User A chats with Automated Agent #1, then CSR #15, who escalated to CSR #3, who then refers User A back to CSR #15. This would be considered four dialogs. |
| group ID | A value used in URLs that designates the department or individuals best qualified to handle a user’s particular question or problem. |
| iMessages | Apple’s secure messaging service for sending and receiving messages in the Messages app. |
| intent ID | A value used in URLs that define the purpose of the chat. |
| interactive message | A category of message within Messages for Business that includes List Picker, Time Picker, Apple Pay requests, custom app download requests, and authentication requests. |
| link previews | A Messages app feature that Messages for Business uses. The functionality of Link Previews has been found to be inconsistent, necessitating the creation of the Rich Link Messages feature in Messages for Business. |
| Messages app | The application for sending and receiving messages. This should not be confused with iMessages. |
| MSP | Messaging Service Platform. A messaging platform that provides the user interface for customer service agents and the connection to Messages for Business orthe company that sells a customer service product, such as Genesys Hub and LiveEngage by LivePerson. |
| MSP ID | A unique customer service platform identifier assigned when Apple Business Register approves a MSP account. |
| opaque ID | A 169-character string that uniquely identifies the interaction between a user and a business. It is passed in the HTTP header of each Messages for Business message. An opaque ID is created with each message associated with the conversation between the customer and a unique business. |
| OAuth | An industry-standard protocol used for authorization. Messages for Business supports OAuth 2.0. |
| place card | Place cards appear in iOS search results and display your business name and address. See Apple Maps place card. |
| POI | Point of Interest is a place of interest in Maps. |
| register | The portal site located at https://register.apple.com. |
| rich link | An MSP implemented Messages for Business feature to enhance user communications. This feature ensures that media, either an image or a video, arrives on the user’s device smoothly, without presenting the “Tap to Load” message. See Rich Link Messages. |
| source ID | A field describing where the message originates. It is the user’s opaque ID for messages from the client device or the Business ID for messages from the MSP. This field appears twice: once in the HTTPS header of the message as Source-Id and once encrypted in the body as sourceId. |