---
schema_version: "1"
id: a4e7259afe47fd636c04e011f5229f59c47268afce5f1e8b63d368f56777eb90
title: Route Data to Objects in Bring Your Own Channel
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/service/264-0-0/partner_messaging_parameters.md
canonical_url: https://help.salesforce.com/s/articleView?id=service.partner_messaging_parameters.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 38a561c59b995e4bb49d91c0f104de229fcbd565711b56096389239201a4cf9c
description: Optionally, use parameters, parameter mappings, and flows to route customer data to Salesforce objects for Bring Your Own Channel for Messaging and Bring Your Own Channel for CCaaS. This data gives service reps more context for who they’re messaging with. For example, create a Support Reason dropdown menu, and then route the customer’s input to the Messaging Session object.
products:
  - Service Cloud
  - Digital Engagement
release: "264"
---
# Route Data to Objects in Bring Your Own Channel

Optionally, use parameters, parameter mappings, and flows to route customer data to Salesforce objects for Bring Your Own Channel for Messaging and Bring Your Own Channel for CCaaS. This data gives service reps more context for who they’re messaging with. For example, create a Support Reason dropdown menu, and then route the customer’s input to the Messaging Session object.

### 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;">
              <a name="partner_messaging_parameters__d1267e2132"><!-- --></a><span style="vertical-align:text-bottom;display:inline-block;"><img style="margin-bottom:0;" id="partner_messaging_parameters__d1267e2132" 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;">Bring Your Own Channel for Messaging and Bring Your Own Channel for CCaaS</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, Enhanced
              WhatsApp, Enhanced Facebook Messenger, Standard and Enhanced SMS, Enhanced Apple
              Messages for Business, and Enhanced LINE channels</td>

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

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-service-support_channels-264-0-0-production-enus/f3c4b3d2-ff86-4f7c-9fe2-3d8b23d35109/images/icon_note.png)

Note Bring Your Own Channel for Messaging is now Partner Messaging, and Bring Your Own Channel for CCaaS is now Partner Contact Center Messaging. You may see references to Bring Your Own Channel for Messaging and Bring Your Own Channel for CCaaS in Salesforce applications and documentation.

Because Bring Your Own Channel for Messaging and Bring Your Own Channel for CCaaS messaging channels aren’t using a Salesforce client, we don’t have full control over the mechanics. Your setup requirements may differ based on the needs of your implementation. Use this help topic to familiarize yourself with the basic building blocks that are hosted in Salesforce and how they work together. We’ve provided an example where a Messaging end user’s name is passed to the Messaging User object using a flow and custom parameters and mappings.

1. [Create an Omni-Channel flow from scratch](https://help.salesforce.com/s/articleView?id=service.omnichannel_create_a_flow.htm&language=en_US) with a variable that’s used to route data to an object. The Omni-Channel flow takes the flow variable, which receives data from the parameter, and sends that data from the flow variable to a Salesforce object. The flow then routes the work to a destination like a queue or rep. In this example, we use a variable named newEndUserName to update the Name field of a Messaging User object.
    
    1. In Flow Builder, add an `input_record` variable and `recordId` variable that are available for input.
    2. Create a new variable that will hold the value of the data you want to pass to the object. In this example, we name it `newEndUserName`. The variable is available for input.
    3. In the flow, include an Update Records action and a Route Work action.
    
    For reference, compare your flow to this example.
    
    **Update Records action example**
    
    ![Update Records action with Specify conditions to identify records and set fields individually selected, Messaging User as the Object, filtered by Id equals input\_record of Messaging User, and Set Name field as newEndUserName value](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-service-support_channels-264-0-0-production-enus/f3c4b3d2-ff86-4f7c-9fe2-3d8b23d35109/support_channels/images/messaging/messaging_route_data_example_update_records.png)
    
    **Route Work action example**
    
    ![Route Work action that routes a single record using an input\_record Id to a Service Channel, routing to a Queue](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-service-support_channels-264-0-0-production-enus/f3c4b3d2-ff86-4f7c-9fe2-3d8b23d35109/support_channels/images/messaging/messaging_route_data_example_route_work.png)
2. If your Bring Your Own Channel for CCaaS implementation uses partner-owned routing, determine the DurableId of your Omni-Channel flow and share it with your implementation partner. This isn’t required for Bring Your Own Channel for Messaging. The DurableId always starts with 300 and differs from the FlowId.
    1. To find the Omni-Channel flow ID, from Flow Builder, note the flowId value at the end of the URL in your browser window. For example, `https://salesforce-example-url/flowBuilder.app?flowId=301Hr000000Ay9EIAS`, where `301Hr000000Ay9EIAS` is the flow ID.
    2. To find the DurableId of the flow, execute a query in the Query Editor in the Developer Console. Use a query with this syntax, where LatestVersionId is the flow ID of your Omni-Channel flow.`SELECT ActiveVersionId, ApiName, ApiVersion, DurableId FROM FlowDefinitionView WHERE LatestVersionId = '301Hr000000Ay9EIAS'`
3. In Setup, in the Quick Find box, enter `Messaging Settings`, and select **Messaging Settings**.
4. Select your messaging channel.
5. Under Custom Parameters, add a custom parameter that matches the variable name in the Omni-Channel flow, for example newEndUserName. The parameter establishes the data that you want to collect from your customer.
    
    ![New custom parameter for newEndUserName parameter name, api name, and channel variable name with data type string and max length 128](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-service-support_channels-264-0-0-production-enus/f3c4b3d2-ff86-4f7c-9fe2-3d8b23d35109/support_channels/images/messaging/messaging_byoc_add_custom_parameter.png)
    
    1. Specify a **Maximum Length** for the custom parameter that’s less than or equal to 1500.
    2. When you create the parameter, note the **Channel Variable Name** and **Maximum Length** and share these with your implementation partner.
6. Under Parameter Mappings, add parameter mapping for the custom parameter. Parameter mapping connects a parameter to a flow variable. This mapping sends the data collected by the parameter into a flow, where it’s routed to a Salesforce object.
    
    ![New parameter mapping for the newEndUserName parameter and newEndUserName flow variable name](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-service-support_channels-264-0-0-production-enus/f3c4b3d2-ff86-4f7c-9fe2-3d8b23d35109/support_channels/images/messaging/messaging_byoc_add_parameter_mapping.png)

#### See Also

- [Developer Console Query Editor](https://help.salesforce.com/s/articleView?id=platform.code_dev_console_tab_query_editor.htm&language=en_US)
- [Bring Your Own Channel for Messaging Developer Guide: Add Support for Custom Parameters](https://developer.salesforce.com/docs/service/messaging-partner/guide/add-custom-objects.html)
- [Bring Your Own Channel for CCaaS Developer Guide: Add Support for Custom Parameters](https://developer.salesforce.com/docs/service/messaging-byoc-ccaas/guide/add-custom-objects.html)