> For the complete documentation index, see [llms.txt](https://claimlane-docs.gitbook.io/claimlane-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://claimlane-docs.gitbook.io/claimlane-docs/troubleshooting-and-faqs/how-to-add-flow-tags-and-internal-tags-in-b2b.md).
# How to add flow tags and internal tags in B2B
{% hint style="info" %}
### This Guide is Only for 2B2, if you need to create tags for B2C check this guide:
{% endhint %}
### Navigate to Flow Tags & Add a tag
Go to Settings in the down left corner from Claimlane's inbox, navigate to Brands (1) (only available for supplier account types), and click Datasource (2) for the brand you want to edit.
You will now be directed to the data source for the brand.
From here, navigate to General Tags (1), select Flow tags (2) from the top menu. On this page, you can see the Flow tags, that have already been created for your brand.
\*creating internal tags is the same process – this guide will focus on flow tags.
To add a new field, that your partners can use to add data on their tickets towards you, click + Add tag (3).
This will create a new empty tag. Click the Pen icon (1) to set up the new tag.
### Customize the Flow tag
You will be presented with a pop-up window. Start by defining the name of the tag under Tag name (1), which will be the field label placed just above the field.
The Scope (2) should always be set to Product. This ensures that the field is enabled on each Add product page in the ticket creation flow, giving you the input from the field for each product added to the ticket.
For B2B tickets, the Channel (3) should be set to B2B.
Then, you need to select the type of data you wish to request under Select tag type (1). Here, we have 4 different options:
1. Single select - A dropdown menu, where your partners can select one option
2. Multi select - A dropdown menu, where your partners can select multiple options
3. Input - A single line text input
4. Multiline input - A larger text field
After selecting a tag type, you can define whether the field should be required from your partners, or optional, from the Required / optional (2) field.
### Managing options (Dropdowns)
For the Single select & Multi select, you will see a blue Manage options (1), where you can define the options your partners should be able to select from, clicking the field.
When clicking Manage Options, a new window will appear.
Add a new option to the dropdown by cliking Add item (1). Define the name of the option in the Text field (2) in the Tag column. Rearrange the order of the options with the up & down buttons (3).
When you have added the relevant options, click Done (4).
### Managing suggestions (Input)
For the Tag type Input, the blue Manage Options button will be replaced with a blue Manage suggestions button.
After clicking Manage suggestions, a new window will appear, where you can manage which suggestions should be shown o your partner, when they place their cursor in the Input Field.
Under Add suggestions as list here (1) you can paste or write any suggestions, that should be presented. Under Suggestions (2), you can see an example of how the suggestions will be presented to your partners.
When you have added the relevant suggestions, click Save (3).
### Setup a guide for the field (Optional)
If your partners require some assistance in gathering the information you are requesting in the field, it might be relevant to add a guide to the tag.
Flow tag guides consists of a text (1) and an image (2), which will be displayed as shown in the example (3).
Click Done. The field is now ready to be applied to the relevant flows.
### Add the field to a ticket type
To apply your new field to a B2B flow, select either Claim, Return or Delivery Issue from the menu under Request type rules (1).
When a request type is selected, go to Flow tags. This will display all Flow tags available for the Request type rule. By default, new Flow tags are disabled.
Check off the checkbox (3) in the Enable column for the new tag.
The tag is now:
* Displayed in the Ticket Creation Flow, for your partners to insert data on a prodcut level
* As an editable field on tickets
* As a column and filter in analytics
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://claimlane-docs.gitbook.io/claimlane-docs/troubleshooting-and-faqs/how-to-add-flow-tags-and-internal-tags-in-b2b.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.