> For the complete documentation index, see [llms.txt](https://docs-conversational-ai.syntphony.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs-conversational-ai.syntphony.com/syntphony-messaging-portal/messaging-tools/planning/contact-manager.md).

# Contact Manager

## Purpose

Maintain contact records used by groups and messaging campaigns.

## Who this is for

Operators and supervisors responsible for audience data quality.

## Prerequisites

* Permission to access Planning modules.
* Defined data standards for phone format (international format recommended) and required attributes.

## Steps

1. Open **Planning** and go to **Contact Manager**.
2. Review the contact list and apply filters (region, name, email domain, or combined criteria).
3. Create or edit a contact and update required attributes.
4. Import contacts from CSV when bulk onboarding is required (match column mapping to portal fields).
5. Remove or correct duplicates and invalid numbers before group creation.
6. Save changes and use filtered subsets when building groups in [Group Manager](/syntphony-messaging-portal/messaging-tools/planning/group-manager.md).

<figure><img src="https://3261478287-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXHkoH2WwcemdqskPI0KI%2Fuploads%2F6X9uKHnKFBhcE6egEoYl%2Fimage.png?alt=media&amp;token=a494f9a0-65ec-47d3-849b-cdb6bcd1698c" alt=""><figcaption><p>Contact list and filters</p></figcaption></figure>

## Key operations

* Review and update contact attributes.
* Validate data quality before campaign execution.
* Prepare filtered contact subsets for group creation.

## Data quality expectations

* Phone numbers should use international format where possible.
* Avoid duplicate records for the same recipient before broadcast sends.
* Keep optional attributes consistent to improve filter accuracy in Group Manager.

## Expected outcome

Contact data remains clean, segmentable, and ready for outbound communication.

## Related pages

* [Planning](/syntphony-messaging-portal/messaging-tools/planning.md)
* [Group Manager](/syntphony-messaging-portal/messaging-tools/planning/group-manager.md)
* [Broadcast Message](/syntphony-messaging-portal/messaging-tools/communication/broadcast-message.md)


---

# 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-conversational-ai.syntphony.com/syntphony-messaging-portal/messaging-tools/planning/contact-manager.md?ask=<question>&goal=<user_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.