The name of the customer that the interaction has occurred with.

The email address that the Connect request should be sent to.

The email address that identifies the employee that had this interaction with the customer. ONLY ONE of either email or custom_id should be provided in each request.

A custom identifier for this employee that has also been set up within Stella Connect. ONLY ONE of either email or custom_id should be provided in each request.

The service channel in which this interaction occurred. This name must match the channel that is set up within Stella Connect.

Typically the interaction or ticket number, so you can easily look up this interaction later.

A URL to link the request back to a ticketing system where it originated. This link will be presented to users in the Stella Connect interface for easy access.

A collection of categories under which this interaction can be classified. Call reason or disposition are good uses. These are intended to be broad rather than uniquely identifying tags.

Only required for multibrand companies, the name that identifies a particular brand with subdomain that request will be associated with.

The standard ISO 639-1 language designator and optional 639-2 regional designator separated by hyphen. ex. en-US represents English US. This field is only required if you are setup with multiple languages.

The country of residence of the customer, if known. Must be provided in ISO-3166 alpha-2 format.

A flag to indicate that no feedback request email should be sent as a result of this interaction. This is used to ensure accurate reporting of interaction counts.

Limited Availability: Custom properties can be added in a flat object of keys and values. Please contact your Client Success Manager to discuss this feature.