> For the complete documentation index, see [llms.txt](https://help.stringeex.com/stringeex-tong-dai-cham-soc-and-quan-ly-khach-hang/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.stringeex.com/stringeex-tong-dai-cham-soc-and-quan-ly-khach-hang/en/ii.-system-features/1.-dashboard/1.5.-campaign.md).

# 1.5. Campaign

## Campaign interface

<figure><img src="/files/9b0baArSoCUG3Zx0haWP" alt=""><figcaption></figcaption></figure>

### (1) Filter and search

* **Campaign name:** The user filters results by Name campaign
* **Start time:** The user filters by the campaign start time
* **Search:** After selecting the filter parameter, the user clicks Search to display the results
* **Export a report:** Export the searched campaign report. Note: this report only includes contacts called out during the campaign and entered into the survey report by the agent.

### (2) Results

* **Agent name:** The customer name in the contact dataset is added to the campaign (add via a filter, an excel file, add directly,...). It acts as the contact name on the portal.
* **Campaign ID:** Campaign identifier after initiating the campaign successfully. This ID is for use when there is a request or problem that needs support from the StringeeX contact center
* **Campaign name:** The name of the initiated campaign
* **Call type:** Call-in type, StringeeX supports Outbound campaign
* **Phone number:** The customer phone number. Depending on the settings, the phone number can be shown in full or as a hidden number (84xxxxxxxxx) to portal users (agents).
* **Call status:** The status of call (Successful - Failed - Undone)

### (3) Switch to the result page

Go to the next page of results


---

# 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://help.stringeex.com/stringeex-tong-dai-cham-soc-and-quan-ly-khach-hang/en/ii.-system-features/1.-dashboard/1.5.-campaign.md?ask=<question>&goal=<endgoal>
```

`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.