> For the complete documentation index, see [llms.txt](https://docs.nexthink.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nexthink.com/user-guide/campaigns/managing-campaigns/creating-campaigns/types-of-questions/authoring-and-formatting-campaign-content.md).
# Authoring and formatting campaign content
### Rich text formatting
Enhance employee experience by formatting campaign questions and the campaign’s final message using the rich text editor of the **Text** field.
Text formatting options include:
* Bold on macOS endpoints
* Underline, italics, hyperlinks, different font sizes, bullet points, and line breaks on macOS and Windows endpoints
These are some useful tips to consider:
* Leverage different text sizes by using larger text to emphasize the question and smaller text for greetings and introductory text.
* Resize the rich text editor on both the **Content** and **Translation** tabs by clicking the small diagonal lines icon in the bottom right corner of the text box and dragging it downward.
### Personalizing questions and final message
Personalize your campaign questions by including the employee's name. To achieve this, use placeholders such as `{colleague}` or `{user}`within the **Text** fields—do not use these placeholders in the **Choice text** fields reserved for campaign answers.
Consider the following when using `{colleague}` or `{user}` placeholders:
* The system first attempts to retrieve the user given name from the operating system.
* If the given name is unavailable or a security restriction blocks that request, the system tries to retrieve the user full name instead.
* If the full name is also unavailable, the system defaults to the current user login name (generally, the username used for signing in the device). When [previewing the campaign](#creatingcampaigns-previewingacampaign) the placeholder is not substituted and appears as is.
For parametric campaigns, personalize question-related **Text** fields further by including the `{{parameter_id}}` placeholder. The system replaces this placeholder with the parameter ID given when sending the campaign.
### Formatting hyperlinks
A hyperlink must have the appropriate format depending on the link type. Currently, Nexthink supports http, https, mailto, im:sip and schemes links.
**Examples**
* Web link:\
`https://www.example.com/campaign-info`
* Email link:\
`mailto:someone@example.com?subject=Optional%20subject`
* Instant messaging links:\
`im:sip:username`
* Self-service software portals links:\
`softwarecenter:SoftwareID=ScopeId_/Application_`\
`companyportal:ApplicationId=`\
`jamfselfservice://content?entity=&id=&action=view`
Enter the desired text into the **Text** field and select part of it. Click on the insert icon to provide an URL. Click on the **Add link** button to insert the link into the selected part of the text.
{% hint style="info" %}
If you want to parametrize the destination URL of a hyperlink in your campaign text, refer to the appropriate use cases in the [Types of campaigns](/user-guide/campaigns/managing-campaigns/creating-campaigns/types-of-campaigns.md#use-case-passing-urls-as-parameters) documentation.
{% endhint %}
When an employee clicks a link in a campaign, the operating system opens the application associated with the protocol.
Refer to the [Types of questions](/user-guide/campaigns/managing-campaigns/creating-campaigns/types-of-questions.md) and [Controlling the flow of questions](broken://pages/1cYy5LXa2KfwaRnPwTM0) documentation for more information.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.nexthink.com/user-guide/campaigns/managing-campaigns/creating-campaigns/types-of-questions/authoring-and-formatting-campaign-content.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
