...
Users can select from a predefined list of filters to sort through conversions.
Partners have access to the same filter options, ensuring consistent communication.
...
Implementation Steps
Just provide your list of conversion notes (or cancellation reasons) to Ingenious via support ticket or slack. We will do the implementation to your platform.
A sample list view is provided, illustrating how conversion notes can be laid out:
Code | Title | Description | |||
|---|---|---|---|---|---|
INVALID_PHONENUMBER ORDER | Invalid Phone Number | ... | INFO_REQUEST | Information Request Order | Order was invalid and could not be fulfilled |
RETURNED | Order returned by customer | Customer sent back order | |||
... | ... | ||||
OTHER_REASON | Other |
Implementation Steps
Providing Conversion Notes List:
Partners are requested to send their list of conversion notes through Slack or a support ticket.Integration:
The provided list will be integrated into the backend of the partner's platform.
Parameter Transmission Improvements
The existing parameter
crewill be replaced by the new parameterconversionnote.When a conversion note is used, the corresponding code should be transmitted using this parameter.
Example: conversionnote=NO_INTEREST
Comments for Conversions
In addition to the notes, partners can leave comments for each conversion, especially useful for rejections. These comments are:
...
Displayed alongside the conversion status.
...
Translated into the platform languages.
...
Parameter Transmission
You may also transmit conversion notes with your conversion tracking tag (e.g. serverside). The name of the parameter isconversionnote. Value should be the Code.
Example: conversionnote=RETURNED
How to Use Comments
Status Changes: Clearly state the intention behind the status change by using a pre-defined comment or writing a custom one.
Rejections: When rejecting a conversion, provide a comment to offer the partner context for the decision.
...