feat(docs): document customer relationship_level in 3.6 and v3.7 EUEE-1586 - #1686
Open
GGuinea wants to merge 3 commits into
Open
feat(docs): document customer relationship_level in 3.6 and v3.7 EUEE-1586#1686GGuinea wants to merge 3 commits into
GGuinea wants to merge 3 commits into
Conversation
…relationship-level
There was a problem hiding this comment.
Pull request overview
Documents relationship_level support for Agent Chat API v3.6 and v3.7.
Changes:
- Adds the field to Customer schemas and examples.
- Documents sparse
customer_updatedpushes. - Adds changelog entries for both versions.
Reviewed changes
Copilot reviewed 7 out of 7 changed files in this pull request and generated 2 comments.
Show a summary per file
| File | Description |
|---|---|
src/pages/messaging/agent-chat-api/v3.7/rtm-pushes/index.mdx |
Documents v3.7 relationship-level pushes. |
src/pages/messaging/agent-chat-api/v3.7/data-structures/index.mdx |
Adds the v3.7 Customer field. |
src/pages/messaging/agent-chat-api/rtm-pushes/index.mdx |
Documents v3.6 relationship-level pushes. |
src/pages/messaging/agent-chat-api/data-structures/index.mdx |
Adds the v3.6 Customer field. |
src/pages/messaging/agent-chat-api/changelog/index.mdx |
Records both API-version changes. |
payloads/messaging/v3.7/agent-chat-api/users/customer.json |
Updates the v3.7 Customer example. |
payloads/messaging/v3.6/agent-chat-api/users/customer.json |
Updates the v3.6 Customer example. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Copilot review: field was documented only in data-structures. Add it to v3.6/v3.7 Web and RTM get_customer response tables, matching the segment_memberships precedent.
oliwiapolec
reviewed
Sep 8, 2026
| | `omnichannel` | optional | | | ||
| | `address` | optional | An object of the customer's address data. | | ||
| | `customer_properties` | optional | An object where the keys are the IDs of the [customer properties](#customer-property) and the values are their data. | | ||
| | `relationship_level` | optional | The customer's relationship level. The only supported value is `vip`. Returned only if set. | |
Collaborator
There was a problem hiding this comment.
Suggested change
| | `relationship_level` | optional | The customer's relationship level. The only supported value is `vip`. Returned only if set. | | |
| | `relationship_level` | optional | The customer's relationship level. Possible values: `vip`. Returned only if set. | |
| | `carts` | optional | An array of customer's shopping carts. See [Cart](#cart) for the object structure. | | ||
| | `address` | optional | An object of the customer's address data. | | ||
| | `customer_properties` | optional | An object where the keys are the IDs of the [customer properties](#customer-property) and the values are their data. | | ||
| | `relationship_level` | optional | The customer's relationship level. The only supported value is `vip`. Returned only if set. | |
Collaborator
There was a problem hiding this comment.
Suggested change
| | `relationship_level` | optional | The customer's relationship level. The only supported value is `vip`. Returned only if set. | | |
| | `relationship_level` | optional | The customer's relationship level. Possible values: `vip`. Returned only if set. | |
| | `chat_ids` | []string | The IDs of the customer's chats. Returned only if the customer had at least one chat. | | ||
| | `omnichannel` | object | An object of the customer's [omnichannel data](/messaging/agent-chat-api/data-structures/#customer). | | ||
| | `address` | object | An object of the customer's address data. Returned only if set. | | ||
| | `relationship_level` | string | The customer's relationship level. The only supported value is `vip`. Returned only if set. | |
Collaborator
There was a problem hiding this comment.
Suggested change
| | `relationship_level` | string | The customer's relationship level. The only supported value is `vip`. Returned only if set. | | |
| | `relationship_level` | string | The customer's relationship level. Possible values: `vip`. Returned only if set. | |
| | `chat_ids` | []string | The IDs of a customer's chats. Returned only if the customer had at least one chat. | | ||
| | `omnichannel` | object | An object of the customer's [omnichannel data](/messaging/agent-chat-api/v3.7/data-structures/#customer). | | ||
| | `address` | object | An object of the customer's address data. Returned only if set. | | ||
| | `relationship_level` | string | The customer's relationship level. The only supported value is `vip`. Returned only if set. | |
Collaborator
There was a problem hiding this comment.
Suggested change
| | `relationship_level` | string | The customer's relationship level. The only supported value is `vip`. Returned only if set. | | |
| | `relationship_level` | string | The customer's relationship level. Possible values: `vip`. Returned only if set. | |
| | `chat_ids` | []string | IDs of a customer's chats. Returned only if the customer had at least one chat. | | ||
| | `omnichannel` | object | An object of the customer's [omnichannel data](/messaging/agent-chat-api/v3.7/data-structures/#customer). | | ||
| | `address` | object | An object of the customer's address data. Returned only if set. | | ||
| | `relationship_level` | string | The customer's relationship level. The only supported value is `vip`. Returned only if set. | |
Collaborator
There was a problem hiding this comment.
Suggested change
| | `relationship_level` | string | The customer's relationship level. The only supported value is `vip`. Returned only if set. | | |
| | `relationship_level` | string | The customer's relationship level. Possible values: `vip`. Returned only if set. | |
| | `chat_ids` | []string | The IDs of a customer's chats. Returned only if the customer had at least one chat. | | ||
| | `omnichannel` | object | An object of the customer's [omnichannel data](/messaging/agent-chat-api/data-structures/#customer). | | ||
| | `address` | object | An object of the customer's address data. Returned only if set. | | ||
| | `relationship_level` | string | The customer's relationship level. The only supported value is `vip`. Returned only if set. | |
Collaborator
There was a problem hiding this comment.
Suggested change
| | `relationship_level` | string | The customer's relationship level. The only supported value is `vip`. Returned only if set. | | |
| | `relationship_level` | string | The customer's relationship level. Possible values: `vip`. Returned only if set. | |
|
|
||
| </CodeResponse> | ||
|
|
||
| A change of the customer's `relationship_level` is reported in a separate push, which contains only `id`, `type`, and `relationship_level`. The value is `null` when the relationship level was removed. |
Collaborator
There was a problem hiding this comment.
Suggested change
| A change of the customer's `relationship_level` is reported in a separate push, which contains only `id`, `type`, and `relationship_level`. The value is `null` when the relationship level was removed. | |
| Changes to the customer's `relationship_level` are reported in a separate `customer_updated` push that includes only the `id`, `type`, and `relationship_level` fields. The `relationship_level` value is `null` when the relationship level is removed. |
|
|
||
| </CodeResponse> | ||
|
|
||
| A change of the customer's `relationship_level` is reported in a separate push, which contains only `id`, `type`, and `relationship_level`. The value is `null` when the relationship level was removed. |
Collaborator
There was a problem hiding this comment.
Suggested change
| A change of the customer's `relationship_level` is reported in a separate push, which contains only `id`, `type`, and `relationship_level`. The value is `null` when the relationship level was removed. | |
| Changes to the customer's `relationship_level` are reported in a separate `customer_updated` push that includes only the `id`, `type`, and `relationship_level` fields. The `relationship_level` value is `null` when the relationship level is removed. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Documents the native per-customer relationship level exposed by agent-api in versions 3.6 and 3.7 (EUEE-1586).
What is documented
relationship_leveladded to the Customer data structure table and to the sample Customer payload (3.6 and v3.7). String enum, the only supported value isvip, returned only when set.customer_updatedpush: a relationship level change arrives as a separate, sparse payload containing onlyid,type, andrelationship_level, wherenullmeans the level was removed. Added as its own sample payload instead of extending the existing one, because the CDP-sourced push never carries the monitoring fields shown there.Versions 3.4 and 3.5 are untouched — they neither expose the field nor receive the push.
Out of scope
POST /v1/update_customerin the Customer Data Platform API, scopecustomers:rw) is not documented here.src/configs/redoc/customer-data-platform-api/spec.ymlhas drifted from the service spec inlivechat/api(missing/v1/delete_customer_property_definition,/v1/set_customer_properties_values,/v1/has_sales_events), so syncing it is a separate task.segment_memberships(EUEE-1567) is still undocumented in the Customer data structure.phone_numberandomnichannelrows that v3.6 has.Prerequisites before merge
livechat/apiPR1/3 for EUEE-1586 (native relationship level: per-customer set + push) released to production.