--- title: "Customer Phone Management" slug: "customer-phone-management" updated: 2024-11-13T21:07:24Z published: 2024-11-13T21:07:24Z canonical: "docs.relaynetwork.com/customer-phone-management" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.relaynetwork.com/llms.txt > Use this file to discover all available pages before exploring further. # Customer Phone Management The Customer Phone Management Data Extension can be used to add or remove phone numbers to/from accounts. Phone management is used to change phone numbers for Customers (add new phone number with consent, remove old phone number).This data extension formats the data for Relay batch file or Relay API triggered customer phone number changes. The Relay Custom Activity in SFMC Journey Builder does not source data from this data extension. #### **Setting Up the Automation** | Step # | Description | Salesforce Marketing Cloud | | --- | --- | --- | | 1 | - Complete the SQL Mapping Worsksheet. *Note: For details on each data field and the required format, please see the Data Fields section below this table.* | [](https://cdn.us.document360.io/6738087b-455d-402f-b70a-a44a4231547e/Images/Documentation/Customer Phone Management.xls)Customer Phone Management27.00 KB[](https://cdn.us.document360.io/6738087b-455d-402f-b70a-a44a4231547e/Images/Documentation/Customer Phone Management.xls) | | 2 | - Open Journey Builder > Automation Studio. | ![](https://cdn.us.document360.io/6738087b-455d-402f-b70a-a44a4231547e/Images/Documentation/journey-builder-automation-studio.png) | | 3 | - Select the Activities tab and open the list of SQL Queries. | ![](https://cdn.us.document360.io/6738087b-455d-402f-b70a-a44a4231547e/Images/Documentation/activities-tab-sql-queries.png) | | 4 | - Select the Relay Customer Phone Management SQL Query and select the edit icon (pencil). | ![](https://cdn.us.document360.io/6738087b-455d-402f-b70a-a44a4231547e/Images/Documentation/edit-phone-management(1).png) | | 5 | - Edit the SQL Activity shell. - All tablename.fieldname entries must be updated (or removed) based on your entries in the mapping worksheet. - The Test table name must be replaced with the actual table name where the data will be pulled from. (If more than one table is used to obtain data, a properly coded SQL 'join' statement can be used.) - All input_ parameters required for the trigger_id must be mapped. Add additional mappings for each input_ parameter to support the requirements of the experience. | ![](https://cdn.us.document360.io/6738087b-455d-402f-b70a-a44a4231547e/Images/Documentation/query-example-phone-management.png) | | 6 | - Click through to save the updated query. - Schedule the automation. | ![](https://cdn.us.document360.io/6738087b-455d-402f-b70a-a44a4231547e/Images/Documentation/schedule-phone-managment.png) | #### **Data Fields** | **Field Name** | **Data Type** | **Notes** | | --- | --- | --- | | CCID | Text (100) | Primary Key. **Required**. Uniquely identifies a Client’s Customer | | PHONE_NUMBER | Text (100) | Primary Key. **Required**. The phone number associated with the Customer. Example: “2155551234” | | ACTION | Text (100) | **Required**. Valid values include: add - to add the phone number to the ccid remove - to remove the phone number from the ccid | | CONSENT_TYPE | Text (100) | **Required** when action = add. The Customer’s consent to the phone number. Valid values include ‘express’ and ‘written’ |