One of the features requested often is being able to link a conversation to a specific order number in your CRM. While custom fields is currently under consideration for our roadmap, this guide will explain you one way to work around this limitation using custom cards and internal notes.The LogicThe only two methods to store internal information inside a conversation without using custom fields are tags and internal notes. Since order numbers generally are unique per order, tags would be a very bad solution (you'd end up with hundreds if not thousands of different tags). Therefore, we'll make use of internal notes.The idea of this guide is to create a custom card, containing input fields or dropdowns to have an agent select or enter the order number manually, and then having the agent submit the form, creating an internal note inside the conversation using the Dixa API.Since the custom card would always enter the order number or fields in the exact same way, it makes it easier for your BI department to extract that information from the internal note and process it for further use in reports, dashboards and the likes. Manually entering the internal note could also be achieved, but that may make it harder for automatic extraction (you need to take into account human error).How to set upStep 1: create a Dixa API tokenRead on how to do so here. Once that's done, copy the token and store it somewhere safe for later use.Step 2: create a custom cardHead into Settings -> Integrations -> Custom Cards and create a new custom card.Come up with a logical name (e.g. Order Info linking).In the "Authorization header" field, enter the word "Bearer", followed by a space, followed by your API token from step 1. In the "Hook URL" field, enter the following URL:https://dev.dixa.io/v1/conversations/{{csid}}In the template content field, paste the following code:Add the API token from step 1 where it says "REPLACE_ME" in the code. If you want to add extra fields, just copy lines 6 until 10 (both included) and paste it before line 11. Replace "orderid" with any other name you want to name the field. If you'd like to add more data to the internal note, you can also use other HTML form input types (such as radio buttons, checkboxes, dropdowns etc). If you're not comfortable with HTML, ask your IT support department or engineers to help you out. The linked resource above is also a good starting point with examples.Step 3: try out the custom cardCreate the custom card and open any conversation in your account. The custom card should look like this:The note should look like this:Step 4: Talk to your BI departmentHere's the hard part - your BI department will have to create logic when they export Dixa data to search for orderid=YOURORDERID in the internal notes of the conversations (they're part of the conversation export API). The author of the note will always be system user, which is another way of trying to identify these notes.If you have any further questions around this, don't hesitate to reach out to Dixa support or your CSM. They can answer your questions or set up a call with one of our solutions consultants or engineers if they can't answer you directly.Known limitationsIt's currently not possible to make this field mandatory. There's 2 workarounds:Use webhooks (conversation closed) to then check if the note exists and if not, reopen the conversation through the APIModify the above code to also tag the conversation, and set up an automation to reopen the conversation if the tag is not present.The entered data will not show in Dixa Analytics, so you'll need your own BI software to extract and visualize it in the way you need it to be shown.Safety considerationsSince the API token is added inside the custom card template (which runs in the browser), it is possible to extract this token as an agent in your Dixa account with the right technical knowledge.