When using the Web SDK and Mobile SDK, some user flows allow for your
customers or prospects (referred to as consumer) to contact support
before logging into the website or app. Since the user didn't enter any
login credentials, there is no way to tie the user back to your exiting
database right away. CCAI Platform will track the anonymous user when possible
with a new temporary unique ID and merge to your existing user record/ID
once the user has logged in.

Unauthenticated consumers may include:

- Prospects contacting your support or sales team using your webpage

- Current customers who are logged out of your app and contacting
  support to get help with their login

- New users in the critical first stage of onboarding before a login
  has been created

1. Since no identifying information is passed to your CRM without the
   user logging in, they will be recognized anonymously as a **Web
   User**.

   > [!NOTE]
   > **Note:** Web SDK must be installed on your website to receive chats.

2. A ticket or case is created in your CRM with the following information
   for the consumer, and an internal process should dictate how the
   agent should edit the data so that the name of the contact is either
   updated to be correct or merged with an existing contact in your
   CRM.

   - First Name: Web User - {Month/Day Hour:Minute} (ex: Web User
   10/05 10:15)

   - Unique Visitor Identifier
3. If the same user comes back to the web SDK and then is able to sign
   in, the prior tickets while unauthenticated can be merged with ID
   they have now logged in with.

   > [!NOTE]
   > **Note:** If the end user clears their local storage, their unique visitor ID won't be recognized and a new contact will be created for this ticket

## Mobile: Unauthenticated Consumers

1. Since no identifying information is passed to your CRM without the
   user logging in, they will be recognized anonymously as a **Mobile
   User** *.*

   > [!NOTE]
   > **Note:** Mobile SDK must be installed on your website to receive calls and chats.

2. A ticket or case is created in your CRM with the following information
   for the consumer, and an internal process should dictate how the
   agent should edit the data so that the name of the contact is either
   updated to be correct or merged with an existing contact in your
   CRM.

   - First Name: Mobile User - {Month/Day Hour:Minute} (ex: Mobile
   User 10/05 10:15)

   - Mobile SDK Identifier
3. If the same user comes back to the Web SDK or Mobile SDK and then is
   able to sign in, the prior tickets while unauthenticated can be
   merged with ID they have now logged in with.

   **Note for Android Devices**: If the user uninstalls and reinstalls
   your app, their unique mobile SDK ID won't be recognized, and a
   new contact will be created.