---
schema_version: "1"
id: 28a9b2c047a19d2f5299052cb106142a4a7e3978b4b4900b5ef531c808dc52b1
title: Maintain Conversation Continuity with Meta Contact Book for Service WhatsApp
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/service/264-0-0/messaging_wa_contact_book.md
canonical_url: https://help.salesforce.com/s/articleView?id=service.messaging_wa_contact_book.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: a860c70c85c223501d19231b9ffd4cc76c3a7b17df1e9855cf6218fdc8776ebf
description: Meta Contact Book helps maintain the association between a WhatsApp user’s BSUID and phone number. When both identifiers are available, Salesforce can more reliably match incoming messages to an existing messaging user and preserve conversation continuity.
products:
  - Service Cloud
  - Digital Engagement
release: "264"
---
# Maintain Conversation Continuity with Meta Contact Book for Service WhatsApp

Meta Contact Book helps maintain the association between a WhatsApp user’s BSUID and phone number. When both identifiers are available, Salesforce can more reliably match incoming messages to an existing messaging user and preserve conversation continuity.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition">
      <colgroup>
        <col style="width:50%">
        <col style="width:50%">
      </colgroup>
      <tbody>
        <tr class="">
          <td class="slds-cell-wrap" colspan="2" style="vertical-align:top;"><a href="https://help.salesforce.com/s/articleView?id=service.messaging_editions.htm&amp;type=5&amp;language=en_US" target="_blank">View supported editions.</a></td>

        </tr>
        <tr class="">
          <td class="slds-cell-wrap" style="vertical-align:top;">
            <span style="vertical-align:text-bottom;display:inline-block;"><img style="margin-bottom:0;" src="https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-service-support_channels-264-0-0-production-enus/f3c4b3d2-ff86-4f7c-9fe2-3d8b23d35109/resources-global/_corporate/images/checkmark.png" alt="Checkmark"></span>
            <strong>This article applies to:</strong>
          </td>

          <td class="slds-cell-wrap" style="vertical-align:top;">Enhanced WhatsApp channels</td>

        </tr>
        <tr class="">
          <td class="slds-cell-wrap" style="vertical-align:top;">
            <span style="vertical-align:text-bottom;display:inline-block;"><img style="margin-bottom:0;" src="https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-service-support_channels-264-0-0-production-enus/f3c4b3d2-ff86-4f7c-9fe2-3d8b23d35109/resources-global/_corporate/images/crossmark.png" alt="X icon"></span>
            <strong>This article doesn’t apply to:</strong>
          </td>

          <td class="slds-cell-wrap" style="vertical-align:top;">Enhanced In-App Chat, Enhanced Web Chat v1, Enhanced Web Chat v2, Standard and
            Enhanced Facebook Messenger, Standard and Enhanced SMS, Enhanced Apple Messages for
            Business, Enhanced LINE, and Bring Your Own Channel</td>

        </tr>
      </tbody>
    </table>

## Why Use Contact Book?

Meta includes the user’s BSUID in WhatsApp message webhooks. Whether Meta also includes the user’s phone number depends on the user’s interaction history and whether the user is in your Contact Book.

If a user is in your Contact Book, Meta includes both the BSUID and phone number in webhook payloads, including after the user adopts a username. Salesforce can use the phone number to match the user to an existing MessagingEndUser record and maintain conversation history.

Without the Contact Book, Meta can stop including the phone number after the applicable 30 day interaction period. Salesforce may then receive only the BSUID. If Salesforce cannot associate that BSUID with an existing MessagingEndUser record, the user’s messages can be associated with a separate record, resulting in fragmented conversation history.

Contact Book is provided and hosted by Meta, and no Salesforce integration work is required. Meta adds a user’s phone number and BSUID to the Contact Book when your business sends a message or makes a call to the user’s phone number, or receives a message or call from that phone number. Contact Book is enabled by default. We recommend confirming that it remains enabled in WhatsApp Business Manager.

[Learn more about Contact Book in Meta’s documentation](https://developers.facebook.com/documentation/business-messaging/whatsapp/business-scoped-user-ids/#contact-book).

## How does a BSUID relate to a Username in Meta?

A user can optionally add a username that displays in place of a phone number in the customer-facing app. It's a privacy tool. On the back-end, the phone number is still associated with a BSUID as the two unique identifiers that maintain conversation continuity. If a user doesn't add a username, they'll still be associated to a BSUID. Changing a user's username won't affect the BSUID and phone number connection.

## What Features Did Salesforce Build for BSUID?

While BSUIDs and Contact Books are Meta features, Salesforce has added a new MessagingExternalUserKey field to the MessagingEndUser object to store a BSUID. The user’s phone number is still stored in the MessagingPlatformKey field on the same object. Both fields are auto-populated and stored in Salesforce after Meta shares the inputs.

[Learn more about the MessagingEndUser fields for this feature](https://developer.salesforce.com/docs/atlas.en-us.object_reference.meta/object_reference/sforce_api_objects_messagingenduser.htm).