# SyncSignature skills for AI assistants

Read this once after connecting. It is the workflow behind the SyncSignature MCP server (https://mcp.syncsignature.com/mcp).

## What SyncSignature is
A company email-signature manager. A workspace has **teammates** (people), **groups** (teams), **signature templates** (one per group), **banner campaigns** (a clickable banner added to signatures for a date range), **smart fields** (values synced from Google Workspace, Microsoft, Chili Piper or CSV) and **analytics** (views and clicks on signature links).

## Ground rules
- **Reads are safe.** `list_*`, `get_*` and `preview_signature` change nothing; call them freely.
- **Writes ask first.** Before any `create_*`, `update_*`, `delete_*`, `add_teammates_to_group`, `remove_teammates_from_group`, `pause_campaign` or `resume_campaign`, show the user what will change and wait for a clear yes.
- **Deletes are final.** Confirm each delete individually. Never delete in a batch from one confirmation.
- **Never invent ids.** Resolve teammates, groups, templates and campaigns by listing them first.
- **Start with `get_workspace`** to learn the workspace name, domain and seat usage.
- **A 403 means owner-only.** Tell the user which action needs a workspace owner; do not retry.
- **A 403 INSUFFICIENT_SCOPE means the connection is read-only.** The person turned off "Allow changes" when connecting. Lookups still work; for a change, tell them to remove and re-add the connector and leave "Allow changes" on. Do not retry.

## Workflows

### Add teammates
1. `list_groups` to find the target group (or ask which one).
2. `create_teammate` per person: name, email, job title, phone, department. Email must be unique.
3. `add_teammates_to_group` with the ids returned.
4. Tell the user the signature will be installed by the workspace's usual install path (Google/Microsoft sync or the invite email); the assistant does not install signatures itself.

### Audit missing data
1. `list_teammates` (paginated; page through everything).
2. Report who lacks a phone, title or photo. Offer to fill values the user provides via `update_teammate`.
3. If a field is a **smart field bound to a source**, say the next sync will overwrite a manual value; suggest fixing it at the source instead.

### Change a signature template
1. `list_workspace_templates` then `get_workspace_template` for the one in question.
2. Explain that the template is shared by every teammate in its group.
3. `preview_signature` with the proposed change and show the HTML result.
4. Only then `update_workspace_template`.

### Run a banner campaign
1. Ask for: banner image URL, click-through link, start and end date, target groups (default: all).
2. `list_groups` to resolve group ids; `list_campaigns` to avoid overlapping an active campaign on the same group.
3. `create_campaign`; confirm the dates read back correctly.
4. `pause_campaign` / `resume_campaign` take effect immediately in teammates' signatures.

### Report on analytics
1. `get_teammate_analytics` per teammate, or `list_signature_links` to see which links are tracked.
2. Summarise as a table: teammate, views, clicks, click-through rate. State the date range.

### Check integrations
`list_integrations` shows Google Workspace, Microsoft, Chili Piper, Keka: connected or not and last sync. Sync is triggered from the SyncSignature app, not from here.

## Example requests
- "Add Priya Shah, priya@acme.com, Sales Manager, to the Sales group."
- "Which teammates have no phone number?"
- "Show me the Sales template and preview it with Priya's details."
- "Start a webinar banner for Marketing from 1 to 15 October."
- "How many clicks did our signatures get last month?"
- "Is our Google Workspace sync connected?"