# HomeOfficePro MCP server: usage guide

## What this is

This is the HomeOfficePro (HOP) MCP server. It lets an AI agent work with a HOP member's account through the Model Context Protocol. Today it gives access to the member's weekly **Social Media Drops** (ready-made posts, stories, reels and carousels), the member's own **contacts** (search, details, appointments, history and where they came from), their **notifications**, their **Send Information library** (the videos, articles, websites and funnels they send to contacts), whether their profile photo and bio are done, and when the member last signed in to HOP. Everything is read-only except **adding a contact** (add_contact), which the agent does only when the member asks.

## How to connect

Server URL:

```
https://mcp.platinumsynergy.dev/mcp
```

- **Claude** (claude.ai, desktop or mobile): add a custom connector and paste the server URL.
- **ChatGPT**: add the server URL as a connector (developer mode).
- **Any other MCP client**: add a remote MCP server using the Streamable HTTP transport and the server URL. The client must support MCP authorization (OAuth); it discovers the sign-in page automatically.

The client then opens a HomeOfficePro sign-in page. The member signs in with their usual HOP team domain, username and password. The password goes only to HOP; the app never sees it.

## Permissions and what it can see

- **Read-only, except adding contacts.** add_contact adds a new contact the way HOP's Add Contact page does (duplicate check first; the list it goes on starts its email sequence, as in HOP). No tool edits, deletes or emails anything.
- **Only the signed-in member's own data.** No tool takes an account, member or team id. Every call is tied to the member who signed in, so an agent can't look up anyone else.
- **Social Media Drops depend on the member's team.** Members whose team doesn't get drops will see "Social Media Drops aren't available for this member's team."
- **Contacts need an active HOP subscription.** Members whose subscription has lapsed, or who have no contacts account, get a message saying which.
- **Sessions renew on their own.** Access lasts 30 minutes and the client renews it automatically, until the member disconnects.
- **Disconnecting:** the member can disconnect any app at [Connected apps](https://mcp.platinumsynergy.dev/connections). Changing the HOP password disconnects every app within about 30 minutes.

## Tools

### `get_last_login`: Get last login

Returns when the signed-in HOP member last logged in to HOP (null if never recorded). Standalone: takes no input and needs no other tool first. Use it to check whether the member has been active in HOP lately, e.g. before suggesting they log in to finish something there.

**Input:** none.

**Example call:**

```
{}
```

**Example result** (abbreviated):

```
{
  "lastLogin": "2026-10-14 09:12:33"
}
```

### `list_drops`: List Social Media Drops

Lists the weekly Social Media Drops (ready-made social content packages) available to the signed-in HOP member, newest first, with the brands they belong to (key, display name and accepted aliases) and how many posts, stories, reels and carousels each contains. Use this to browse or compare weeks; to get the captions and media call get_drop with a dropId from here. If you just want the current drop for one brand, call get_latest_drop instead (one call).

| Input | Type | Required | Description |
| --- | --- | --- | --- |
| `brand` | string, max 100 chars | no | Only list drops for this brand. Accepts the brand key, display name or an alias in any case (e.g. "MomsWithaPlan", "Moms With a Plan", "MWAP"). An unrecognized brand returns no drops; check brands[]. |

**Example call:**

```
{"brand":"MWAP"}
```

**Example result** (abbreviated):

```
{
  "brands": [
    {
      "key": "momswithaplan",
      "name": "Moms With a Plan",
      "description": "…",
      "aliases": [
        "MWAP"
      ]
    }
  ],
  "drops": [
    {
      "dropId": "<opaque id>",
      "brandKey": "momswithaplan",
      "brandName": "Moms With a Plan",
      "dropDate": "2026-10-15",
      "isUpcoming": true,
      "counts": {
        "posts": 5,
        "stories": 5,
        "reels": 1,
        "carousels": 1,
        "total": 12
      }
    },
    "… more weeks, newest first"
  ]
}
```

### `get_drop`: Get Social Media Drop

Returns one Social Media Drop: every piece (post, story, reel or carousel) in posting order with its hook, caption and media URLs (images, videos, carousel slides), plus the member's personalized funnelUrl to use as the call-to-action link. Captions are ready to post as written. Needs a dropId from list_drops; for the current drop of a brand, get_latest_drop does this in one call.

| Input | Type | Required | Description |
| --- | --- | --- | --- |
| `dropId` | string, max 255 chars | yes | The dropId from list_drops. |

**Example call:**

```
{"dropId":"<dropId from list_drops>"}
```

**Example result** (abbreviated):

```
{
  "dropId": "<dropId from list_drops>",
  "brandKey": "americaonamission",
  "brandName": "America on a Mission",
  "dropDate": "2026-10-15",
  "isUpcoming": true,
  "counts": {
    "posts": 5,
    "stories": 5,
    "reels": 1,
    "carousels": 1,
    "total": 12
  },
  "funnelUrl": "https://yourteam.com/...",
  "pieces": [
    {
      "pieceId": "…",
      "type": "post",
      "position": 1,
      "hook": "Short attention-grabbing first line",
      "caption": "Ready-to-post caption text…",
      "assets": [
        {
          "kind": "image",
          "url": "https://…/post-1.png"
        }
      ]
    },
    "… one entry per piece, in posting order"
  ]
}
```

### `get_latest_drop`: Get latest Social Media Drop for a brand

Returns the current Social Media Drop for one brand in a single call: the brand's upcoming drop if one is scheduled, otherwise its most recent one (isUpcoming says which). Same content as get_drop: every piece in posting order with hook, caption and media URLs, plus the member's personalized funnelUrl. Start here when the member asks for "this week's" or "the latest" drop; use list_drops only to browse older weeks or discover which brands exist.

| Input | Type | Required | Description |
| --- | --- | --- | --- |
| `brand` | string, max 100 chars | yes | The brand: key, display name or alias, any case (e.g. "AmericaonaMission", "America on a Mission", "AOAM"). Brands available to the member are listed by list_drops. |

**Example call:**

```
{"brand":"AOAM"}
```

**Result:** Same shape as get_drop.

### `search_contacts`: Search contacts

Searches the signed-in HOP member's own contacts (their prospects and leads), newest first. Every word of query must match the start of a first name, last name, phone number or email, so "jane smi" finds Jane Smith. Email domains ("gmail.com", "@acme") and phone numbers in any format ("5199001234", "900-1234") also work. If nothing matches, the search retries matching anywhere in the name or email and says so with matchedLoosely: true (tell the member these are near matches). Filters narrow the results: status, emailable, addedSince, addedBefore; with no query or filters it lists the newest contacts. Each result has a contactId, name, email, phone, location, the contact status the member set, the autoresponder list, and emailStatus (active, inactive, pending, opted_out or bounced; never email opted_out or bounced contacts). total is the number of matches across all pages. Start here whenever the member mentions a contact by name. Page with offset while hasMore is true.

| Input | Type | Required | Description |
| --- | --- | --- | --- |
| `query` | string, max 100 chars | no | Name, phone, email or email domain to look for, e.g. "jane smith", "900-1234" or "gmail.com". Leave out to list the newest contacts. |
| `status` | string, max 100 chars | no | Only contacts with this contact status, by the name the member sees in HOP (any case), e.g. "Hot Prospect". An unknown name returns an error listing the member's statuses. |
| `emailable` | boolean | no | true: only contacts that can be emailed (emailStatus active or inactive; leaves out pending, opted_out and bounced). |
| `addedSince` | string | no | Only contacts added on or after this date, YYYY-MM-DD. |
| `addedBefore` | string | no | Only contacts added before this date (not including it), YYYY-MM-DD. |
| `limit` | integer | no | How many contacts to return, 1-50 (default 20). |
| `offset` | integer | no | How many contacts to skip, for the next page (default 0). |

**Example call:**

```
{"query":"jane smi"}
```

**Example result** (abbreviated):

```
{
  "contacts": [
    {
      "contactId": 1234567,
      "firstName": "Jane",
      "lastName": "Smith",
      "email": "jane@example.com",
      "phone": "555-123-4567",
      "city": "Toronto",
      "state": "ON",
      "country": "Canada",
      "status": "Hot Prospect",
      "list": "Main list",
      "emailStatus": "active",
      "dateAdded": "2026-10-01"
    }
  ],
  "total": 1,
  "offset": 0,
  "hasMore": false,
  "matchedLoosely": false
}
```

### `get_contact_profile`: Get contact profile

Returns everything HOP knows about one of the signed-in member's contacts: details (email, phone, address, origin, timezone, best time to call, when they were last called and whether that call connected, contact status, list, emailStatus, and isNowMember if the contact has since joined as a member), up to 5 upcoming appointments with the member, and the contact history newest first (calls with outcomes, notes, status and list changes, emails, Send Information links, link clicks), and the answers the contact gave on HOP forms and questionnaires (survey: each question with its answers; empty if none), and sendInfoSent: every Send Information item the contact was sent (title and newest date, one per title), so you can avoid repeats when choosing what to send next from list_send_info_items. Needs a contactId from search_contacts. Use it before advising the member on a contact, e.g. "what happened with Jane?" or "when should I follow up?". History records what HOP logged: a Send Information entry means a link was generated, not that a message was sent.

| Input | Type | Required | Description |
| --- | --- | --- | --- |
| `contactId` | integer | yes | The contactId from search_contacts. |
| `historyLimit` | integer | no | How many history entries to return, newest first, 0-100 (default 20). historyTotal says how many exist. |

**Example call:**

```
{"contactId":1234567}
```

**Example result** (abbreviated):

```
{
  "contact": {
    "contactId": 1234567,
    "firstName": "Jane",
    "lastName": "Smith",
    "email": "jane@example.com",
    "phone": "555-123-4567",
    "status": "Appointment Set",
    "emailStatus": "active",
    "…": "plus the other search_contacts fields",
    "address": "1 Main St",
    "zip": "M1M 1M1",
    "origin": "Facebook ad",
    "timezone": "Eastern Time",
    "bestTimeToCall": "Evening Weekdays",
    "lastCalled": "2026-10-14 18:30",
    "lastCallConnected": true,
    "isNowMember": false
  },
  "upcomingAppointments": [
    {
      "appointmentId": 991,
      "subject": "Overview call",
      "date": "2026-10-17",
      "time": "19:00:00",
      "durationMinutes": 30,
      "type": "Appointment"
    }
  ],
  "history": [
    {
      "date": "2026-10-14 18:30:00",
      "action": "Call",
      "notes": "Interested, wants to see the overview with her husband.",
      "listChangedTo": null,
      "statusChangedTo": "Appointment Set",
      "emailSent": null,
      "outcome": "Connected - Set Appointment"
    },
    "… newest first"
  ],
  "historyTotal": 6,
  "survey": [
    {
      "question": "Why are you interested?",
      "answers": [
        "Extra income",
        "Work from home"
      ]
    }
  ],
  "sendInfoSent": [
    {
      "title": "Moms with a Plan Business Overview",
      "date": "2026-10-12 10:15:03"
    }
  ]
}
```

### `list_send_info_categories`: List Send Information categories

Lists the categories of the signed-in HOP member's Send Information library (the videos, articles, websites and funnels a member sends to contacts), in the order HOP shows them, with a description and how many items each holds. Standalone: takes no input. Call it to see what kinds of content the member has, then list_send_info_items with a categoryId. If you already know roughly what you are looking for, list_send_info_items with a query is one call.

**Input:** none.

**Example call:**

```
{}
```

**Example result** (abbreviated):

```
{
  "categories": [
    {
      "categoryId": 12,
      "name": "Business Overview",
      "description": "Videos that explain the opportunity",
      "itemCount": 6
    },
    "… in HOP order"
  ]
}
```

### `list_send_info_items`: List Send Information items

Lists items in the signed-in HOP member's Send Information library: everything in one category (categoryId from list_send_info_categories, in HOP order), and/or the items whose title or category contains every word of query, across all categories. Give categoryId, query, or both. Each item has a type (article, message, website or funnel), isVideo, its title and category, and typeId + resourceId, which identify the item. description is what HOP says the item is about (null when HOP has none). exampleMessage is the approved wording HOP puts in the message box when the member sends that item; only messages have one. Merge fields in it like ~~firstname~~ are filled in per contact by HOP: keep them, or write the name yourself, never leave a half-filled field. missing lists what HOP lacks for the item and missingCounts totals it over every match; when wording is missing, write a short personal message yourself and say it is your suggestion, not HOP wording. previewUrl (videos only, null when the member's team has no viewing page) opens the video in a player so the member can watch it before choosing; it is not tracked, so a contact opening it does not show up in HOP. The member's own website links are not Send Information items: use list_my_websites. Use it to suggest what to send a contact, e.g. "a video about the business" -> {"query": "overview"}. Read-only: this does not send anything.

| Input | Type | Required | Description |
| --- | --- | --- | --- |
| `categoryId` | integer | no | Only this category (categoryId from list_send_info_categories). |
| `query` | string, max 100 chars | no | Words that must all appear in the item title or category name, any case, e.g. "webinar" or "work from home". |

**Example call:**

```
{"query":"overview"}
```

**Example result** (abbreviated):

```
{
  "items": [
    {
      "typeId": 2,
      "resourceId": 345,
      "type": "message",
      "title": "Business Overview Video",
      "description": null,
      "exampleMessage": "Hi ~~firstname~~, here is the short video I mentioned. Let me know what you think!",
      "missing": [
        "description"
      ],
      "isVideo": true,
      "previewUrl": "https://www.enhancemarketingsystem.com/videoplayer-message?jane&messageid=345",
      "categoryId": 12,
      "category": "Business Overview"
    }
  ],
  "total": 1,
  "missingCounts": {
    "description": 1,
    "exampleMessage": 0
  }
}
```

### `list_recorded_overviews`: List recorded overviews

Lists the signed-in member's recorded business overviews: the overview videos in their team's Send Information library (e.g. "Recorded Overviews"), in HOP order. Standalone: takes no input. Each overview has its title, description (the team's own note on what it is and who it is for, when the title doesn't say it all; null otherwise), playsOn (the site its link opens: only where it is hosted, not who it is for), exampleMessage (the approved HOP wording sent with it; its link expires, e.g. after 24 hours), previewUrl (lets the member watch it first, not tracked) and typeId + resourceId (as a list_send_info_items item). This tool does not pick one for a contact: you choose. For a contact, use what you know about them (get_contact_origin for the site or ad they came in through, get_contact_profile for their status and history, and the conversation) and match it to the overviews' titles and descriptions; say why you chose it, and if nothing points to one, ask the member about the contact or offer the choices. playbook is how the team uses overviews (e.g. set up a call or Zoom and show it live rather than only sending the link); pass that on whenever you suggest one. An empty list means the team has no overviews in Send Information. Read-only: this does not send anything.

**Input:** none.

**Example call:**

```
{}
```

**Example result** (abbreviated):

```
{
  "overviews": [
    {
      "overviewId": 47,
      "typeId": 2,
      "resourceId": 47,
      "title": "Moms with a Plan Business Overview",
      "description": null,
      "playsOn": "momswithaplan.net",
      "isVideo": true,
      "exampleMessage": "Here is the link to the video\n\nhttps://www.momswithaplan.net/e-player?~~ownersusername~~\n\nThis presentation is by invite only and will expire in 24 hours.",
      "categoryId": 8,
      "category": "Recorded Overviews",
      "previewUrl": "https://www.enhancemarketingsystem.com/videoplayer-message?jane&messageid=47"
    },
    {
      "overviewId": 46,
      "title": "Generic (Non-Branded) Business Overview",
      "description": "Generic (non-branded) business overview: the shared presentation used for both Families With a Plan and America on a Mission contacts (there is no separate overview for either). It opens on familieswithaplan.com, but that is only where it is hosted; it is not Families-branded.",
      "playsOn": "familieswithaplan.com",
      "…": "…"
    }
  ],
  "playbook": "Best used live: set up a call or Zoom with the contact and show the overview together, rather than only sending the link."
}
```

### `get_contact_origin`: Get contact origin

Shows where one of the signed-in member's contacts came from: the origin text stored on the contact, the site they landed on and the pages they viewed before signing up (visits), and any promo/ad code they arrived with (promoCodes), with the site, team, lead rotator and linked ad campaign behind that code. A page that is one of the websites on the My Websites page carries its name there in myWebsite (e.g. "Moms with a Plan" or "Scheduling Page"); the visit's myWebsite is the first such page, usually where they landed. An alternate or test version of one of those pages (e.g. home-alt, home-turnstile) carries the base page's name too, with variantOf naming the base page; page is always the page they actually saw. Other pages (thank-you pages, questionnaires) have myWebsite null. Each code has a status: resolved (explained by matches), unresolved (HOP has no site or rotator for that code; say so rather than guessing where it came from) or lookup_failed (try again later). Needs a contactId from search_contacts. Use it for questions like "how did Jane find me?" or "which ad brought this lead in?". Empty visits/promoCodes means HOP has no tracking for that contact (e.g. added by hand or imported).

| Input | Type | Required | Description |
| --- | --- | --- | --- |
| `contactId` | integer | yes | The contactId from search_contacts. |

**Example call:**

```
{"contactId":1234567}
```

**Example result** (abbreviated):

```
{
  "contactId": 1234567,
  "origin": "momswithaplan.net",
  "dateAdded": "2026-10-01",
  "visits": [
    {
      "site": "momswithaplan.net",
      "myWebsite": "Moms with a Plan",
      "firstVisitAt": "2026-10-01T14:02:11Z",
      "pages": [
        {
          "page": "home-alt",
          "myWebsite": "Moms with a Plan",
          "variantOf": "home",
          "visitedAt": "2026-10-01T14:02:11Z"
        },
        {
          "page": "thank-you",
          "myWebsite": null,
          "variantOf": null,
          "visitedAt": "2026-10-01T14:05:40Z"
        }
      ]
    }
  ],
  "promoCodes": [
    {
      "code": "FBOCT",
      "status": "resolved",
      "firstSeenAt": "2026-10-01T14:02:11Z",
      "matches": [
        {
          "site": "momswithaplan.net",
          "team": "Team A",
          "rotator": "Facebook rotator",
          "classification": "paid_campaign",
          "adCampaigns": [
            "Meta ads October"
          ]
        }
      ]
    }
  ]
}
```

### `get_notifications`: Get notifications

Returns the signed-in HOP member's notification history, newest first (the last 7 days unless since says otherwise): new contacts, repeat requests, signups and sales (theirs and their team's), webinar watched, presentation viewed, calendar viewed, questionnaire and checklist completed, product page viewed, training started/completed, team news and new articles. Each has a type, title, description, date and, when it is about one of their contacts, a contactId for get_contact_profile. Filter with type and since. Use it for "what happened since yesterday?" or "who looked at my presentation?". type "other" covers notifications whose title the member wrote themselves (e.g. a Send Information link set to notify them). Hot prospects: a calendar_viewed, presentation_viewed or webinar_watched entry for a contact with no booked appointment since (check upcomingAppointments in get_contact_profile) means they were interested but did not act; that is the moment for a personal follow-up. Surface, don't spam: point these out to the member and suggest one short, personal message per person, not a burst of messages.

| Input | Type | Required | Description |
| --- | --- | --- | --- |
| `type` | string | no | Only this kind of notification: new_contact, repeat_request, signup, team_signup, sale, team_sale, webinar_watched, team_news, new_article, presentation_viewed, training_started, training_completed, checklist_completed, questionnaire_completed, calendar_viewed, product_page_viewed, other. |
| `since` | string | no | Only notifications on or after this date, YYYY-MM-DD (default: 7 days ago; the result echoes the since used). |
| `limit` | integer | no | How many to return, 1-100 (default 50). |

**Example call:**

```
{"type":"presentation_viewed","since":"2026-10-14"}
```

**Example result** (abbreviated):

```
{
  "since": "2026-10-14",
  "notifications": [
    {
      "date": "2026-10-15 09:12:44",
      "type": "presentation_viewed",
      "title": "Prospect is watching your presentation",
      "description": "Jane Smith clicked your presentation link",
      "contactId": 1234567
    }
  ]
}
```

### `get_contact_email_engagement`: Get contact email engagement

Shows how one of the signed-in member's contacts engages with their email and links, from Response Magic: where they are in their list's drip sequence (sent, next email with its day number and send time, finished), sequence emails and broadcasts received, scheduled one-off emails still to go, opens (which email, how many times), email link clicks, and tracked link clicks (the contact opening one of the member's tracked links, e.g. Send Information; the member's own test clicks are left out). score is a simple, transparent engagement number over the last days days (default 90): emails opened x1 + email link clicks x3 + tracked link clicks x2, with each part shown. 0 means no recorded engagement, not an error. Needs a contactId from search_contacts. Use it for "is Jane reading my emails?", "who is most engaged?" or before suggesting a follow-up: someone who opens and clicks is warm even if they never replied. Opens are only counted for HTML emails that load images, so a low open count is not proof they are ignoring the member.

| Input | Type | Required | Description |
| --- | --- | --- | --- |
| `contactId` | integer | yes | The contactId from search_contacts. |
| `days` | integer | no | Window for the score, in days (default 90). The lists of opens and clicks are not limited by it. |

**Example call:**

```
{"contactId":1234567}
```

**Example result** (abbreviated):

```
{
  "contactId": 1234567,
  "since": "2026-07-19",
  "score": {
    "total": 9,
    "days": 90,
    "parts": {
      "emailsOpened": {
        "count": 4,
        "weight": 1,
        "points": 4
      },
      "emailClicks": {
        "count": 1,
        "weight": 3,
        "points": 3
      },
      "trackedLinkClicks": {
        "count": 1,
        "weight": 2,
        "points": 2
      }
    },
    "formula": "emails opened x1 + email link clicks x3 + tracked link clicks x2, last 90 days"
  },
  "sequence": {
    "list": "Moms With a Plan",
    "emailsInSequence": 12,
    "sent": 5,
    "upcoming": 7,
    "next": {
      "subject": "Have you seen this?",
      "day": 21,
      "at": "2026-10-20 09:00:00"
    },
    "finished": false
  },
  "received": {
    "sequenceEmails": {
      "total": 5,
      "last": "2026-10-10",
      "recent": [
        {
          "date": "2026-10-10",
          "subject": "Ten days in"
        }
      ]
    },
    "broadcasts": {
      "total": 3,
      "last": "2026-10-14 18:00:00",
      "recent": [
        {
          "date": "2026-10-14 18:00:00",
          "subject": "October update"
        }
      ]
    }
  },
  "scheduled": [],
  "opens": {
    "emailsOpened": 4,
    "totalOpens": 7,
    "last": "2026-10-14 19:12:03",
    "recent": [
      {
        "date": "2026-10-14 19:12:03",
        "kind": "broadcast",
        "subject": "October update",
        "timesOpened": 2
      }
    ]
  },
  "emailClicks": {
    "total": 1,
    "last": "2026-10-14",
    "recent": [
      {
        "date": "2026-10-14",
        "link": "https://…",
        "from": "broadcast"
      }
    ]
  },
  "trackedLinkClicks": {
    "total": 1,
    "last": "2026-10-12 20:01:44",
    "recent": [
      {
        "date": "2026-10-12 20:01:44",
        "notes": "Clicked \"Business Overview\" - …"
      }
    ]
  }
}
```

### `get_quiet_contacts`: Get quiet contacts

Lists the signed-in member's contacts who have gone quiet: the member reached out before, but no personal outreach is logged in HOP for daysWithoutMessage days (default 14), oldest outreach first. Outreach means what the member logged: Send Information links, calls, and notes. The contact's own clicks and form fills, contact edits, automatic list moves and autoresponder emails do not count. Contacts the member never reached out to (e.g. imports) are not listed. Each contact has the search_contacts fields (status is the pipeline stage the member set) plus lastOutreach and daysQuiet. Limitation: HOP only knows what was logged. Texts, Facebook messages and personal emails sent outside HOP are invisible unless the member logged a note, so ask before assuming someone was ignored. Narrow with status (e.g. "Hot Prospect") and emailable. To re-engage someone, check get_contact_profile first, then suggest an item with list_send_info_items; suggest one personal message per contact, not a blast. Page with offset while hasMore is true.

| Input | Type | Required | Description |
| --- | --- | --- | --- |
| `daysWithoutMessage` | integer | no | Quiet means no outreach for this many days, 1-3650 (default 14). The result says which date that starts from (quietSince). |
| `status` | string, max 100 chars | no | Only contacts with this contact status, by the name the member sees in HOP (any case), e.g. "Hot Prospect". |
| `emailable` | boolean | no | true: only contacts that can be emailed (emailStatus active or inactive). |
| `limit` | integer | no | How many contacts to return, 1-50 (default 20). |
| `offset` | integer | no | How many contacts to skip, for the next page (default 0). |

**Example call:**

```
{"daysWithoutMessage":30,"status":"Hot Prospect"}
```

**Example result** (abbreviated):

```
{
  "days": 30,
  "quietSince": "2026-09-17",
  "contacts": [
    {
      "contactId": 1234567,
      "firstName": "Jane",
      "lastName": "Smith",
      "status": "Hot Prospect",
      "emailStatus": "active",
      "…": "plus the other search_contacts fields",
      "lastOutreach": "2026-08-02 18:30:00",
      "daysQuiet": 75
    }
  ],
  "total": 1,
  "offset": 0,
  "hasMore": false
}
```

### `list_lead_rotators`: List lead rotators

Lists the signed-in member's lead rotators (HOP Marketing > Lead Rotators): rotators that take the leads from the member's ad links and hand them out in turn to the team members in them. Each has rotatorId, name, members and activeMembers (inactive members get no leads), leadsReceived (all time, as the HOP page counts it), leadsInPeriod (the last `days`, default 30) and adLinks (how many ad links feed it). An empty list means the member has no rotators. Next: get_rotator_distribution {rotatorId} for who got the leads and how each ad link performs. Read-only: creating or changing rotators is done in HOP for now.

| Input | Type | Required | Description |
| --- | --- | --- | --- |
| `days` | integer | no | How many recent days leadsInPeriod covers (1-365, default 30). |

**Example call:**

```
{}
```

**Example result** (abbreviated):

```
{
  "days": 30,
  "rotators": [
    {
      "rotatorId": 7,
      "name": "Team Facebook ads",
      "members": 4,
      "activeMembers": 3,
      "leadsReceived": 212,
      "leadsInPeriod": 18,
      "adLinks": 2
    }
  ]
}
```

### `get_rotator_distribution`: Get rotator distribution

Shows how one of the signed-in member's lead rotators has shared out its leads. Needs a rotatorId from list_lead_rotators. memberList is each team member in it, as on the HOP page (active first, then whoever has waited longest for a lead): name, username, active, lastLeadAt, leadsReceived (all time), leadsInPeriod (the last `days`, default 30) and sharePercent of the period's leads. ads are the rotator's ad links (the link to use in ads, landing page, unique visitors, leads, conversionPercent = leads / visitors). notes flags problems in plain words: no members, everyone inactive, no ad links, or an active member who got none of the period's leads. It never shows the leads themselves (they belong to the members who received them). Use it for "is my rotator sharing leads fairly?" or "which ad brings the most leads?". Read-only: adding members or switching them on/off is done in HOP for now.

| Input | Type | Required | Description |
| --- | --- | --- | --- |
| `rotatorId` | integer | yes | The rotatorId from list_lead_rotators. |
| `days` | integer | no | How many recent days leadsInPeriod covers (1-365, default 30). |

**Example call:**

```
{"rotatorId":7}
```

**Example result** (abbreviated):

```
{
  "rotatorId": 7,
  "name": "Team Facebook ads",
  "members": 3,
  "activeMembers": 2,
  "leadsReceived": 212,
  "leadsInPeriod": 18,
  "adLinks": 1,
  "days": 30,
  "memberList": [
    {
      "shareId": 41,
      "name": "Jane Doe",
      "username": "janedoe",
      "active": true,
      "lastLeadAt": "2026-10-19 14:02:11",
      "leadsReceived": 120,
      "leadsInPeriod": 10,
      "sharePercent": 55.6
    },
    {
      "shareId": 42,
      "name": "Sam Lee",
      "username": "samlee",
      "active": true,
      "lastLeadAt": "2026-10-18 09:40:00",
      "leadsReceived": 80,
      "leadsInPeriod": 8,
      "sharePercent": 44.4
    },
    {
      "shareId": 43,
      "name": "Cy Tan",
      "username": "cytan",
      "active": false,
      "lastLeadAt": "2026-06-02 11:15:30",
      "leadsReceived": 12,
      "leadsInPeriod": 0,
      "sharePercent": 0
    }
  ],
  "ads": [
    {
      "name": "October FB ad",
      "url": "http://momswithaplan.net/p=AB12CD",
      "page": "home",
      "uniqueVisitors": 940,
      "leads": 212,
      "leadsInPeriod": 18,
      "conversionPercent": 22.55
    }
  ],
  "notes": []
}
```

### `get_daily_outreach_actions`: Get daily outreach actions

The signed-in member's outreach list for today: their hottest contacts, best first (default 10). Call it when the member asks "who should I reach out to today?", "what should I do today?", or at the start of a daily routine. Contacts are ranked by what they did in the last 14 days: looked at the booking calendar, completed the questionnaire, watched a presentation, clicked or opened an email, and for team members, reached a milestone (e.g. "achieved 5 Meeting Invites": congratulate them) or an onboarding step. Recent and strong signals count most, a pipeline stage that needs action adds a little, and contacts the member already reached out to after their latest signal drop lower. If there are not enough active contacts, the list is filled with contacts the member last reached out to 14-60 days ago. Each action has contact (name, email, phone, status, pipelineStage, emailStatus), why (one line citing the signal and its date: quote it, do not invent other reasons), followUp (what to do for that kind of signal), sendInfoSent (the Send Information items they already got, with dates), lastOutreach and signals. It does not pick what to send: if something should go with the follow-up, choose it yourself from list_send_info_items to fit what the contact just did and who they are (e.g. after a calendar view, help them book rather than send more content), avoiding what they already got; a personal note is often better. Present it as a short to-do list: name, why, and what to say or send. For more on one contact call get_contact_profile {contactId}. Never email a contact whose emailStatus is opted_out or bounced (suggest a call or text instead), and never send anything without the member's OK. sourcesUnavailable lists data HOP could not read this time; mention it if the list looks short. Read-only.

| Input | Type | Required | Description |
| --- | --- | --- | --- |
| `limit` | integer | no | How many actions to return (1-25, default 10). |

**Example call:**

```
{}
```

**Example result** (abbreviated):

```
{
  "date": "2026-10-21",
  "windowDays": 14,
  "contactsWithSignals": 23,
  "actions": [
    {
      "contact": {
        "contactId": 87290012,
        "firstName": "Jane",
        "lastName": "Doe",
        "email": "jane@example.com",
        "phone": "555-0101",
        "city": "Boise",
        "state": "ID",
        "country": "US",
        "status": "Hot Prospect",
        "emailStatus": "active",
        "dateAdded": "2026-10-02",
        "pipelineStage": "Needs Appointment"
      },
      "score": 103.5,
      "why": "Jane Doe looked at your booking calendar yesterday (2026-10-20). Plus 1 more sign of interest in the last 14 days. In your \"Needs Appointment\" stage.",
      "followUp": "They were close to booking: reach out personally and offer to help them pick a time.",
      "sendInfoSent": [
        {
          "title": "Moms with a Plan Business Overview",
          "date": "2026-10-08 14:02:11"
        }
      ],
      "lastOutreach": "2026-10-08 14:02:11",
      "signals": [
        {
          "type": "calendar_viewed",
          "date": "2026-10-20 15:04:00",
          "detail": null
        },
        {
          "type": "email_clicked",
          "date": "2026-10-20",
          "detail": null
        }
      ]
    }
  ],
  "sourcesUnavailable": [],
  "elapsedMs": 840
}
```

### `get_upcoming_leadership_connection`: Get upcoming Leadership Connection

When the next live Leadership Connection is, for the signed-in member's team (Enhance): next (title, start/end in Eastern time with startLocal, startsInMinutes, inProgress, link to join or register, description) and upcoming (the next few sessions), from the Enhance Community Calendar. Leadership Connection is for members currently enrolled in Melaleuca (audience), not prospects: never suggest inviting a prospect to it. Use it to REMIND the member before a session: when next.startsInMinutes is within a day, mention it with the time and link; convert the Eastern time to the member's time zone if you know it. Quote times and links as given, never guess them. If the member missed a session (it has passed and they did not attend), call get_latest_replay and offer the replay. schedule.available false or next null comes with a note (feed not set up or nothing scheduled): point them to the Events calendar in HOP (calendarPage). configured false means their team has no Leadership Connection. Read-only.

**Input:** none.

**Example call:**

```
{}
```

**Example result** (abbreviated):

```
{
  "configured": true,
  "name": "Leadership Connection",
  "audience": "Members currently enrolled in Melaleuca (not prospects).",
  "calendarPage": "https://www.homeofficepro.net/v3/calendar/enhancecal",
  "next": {
    "title": "Enhance Leadership Connection",
    "start": "2026-10-25T11:00:00-04:00",
    "end": "2026-10-25T12:00:00-04:00",
    "startLocal": "Sun Oct 25, 2026 11:00 AM EDT",
    "timezone": "America/New_York",
    "startsInMinutes": 5340,
    "inProgress": false,
    "link": "https://www.enhanceleadershipconnection.com/",
    "description": "Join us live for this week's Leadership Connection."
  },
  "upcoming": [
    "…the next 3 sessions, same shape as next…"
  ],
  "note": null
}
```

### `get_latest_replay`: Get latest Leadership Connection replay

The most recent Leadership Connection replay for the signed-in member's team (Enhance): headline, recordedOn (a short date like "Thu Aug 27"), url (the video player link to share or open) and accessPolicy ("latest_free_until_replaced": the latest replay is free until the next one replaces it). Use it after the member missed a session, or when they ask for the replay: give the link and when it was recorded. url null comes with replayNote (e.g. replays are for subscribers only right now, or none has been posted). For when the next live session is, call get_upcoming_leadership_connection. Read-only.

**Input:** none.

**Example call:**

```
{}
```

**Example result** (abbreviated):

```
{
  "configured": true,
  "name": "Leadership Connection",
  "latestReplay": {
    "headline": "Latest Leadership Connection Replay",
    "recordedOn": "Thu Aug 27",
    "url": "https://play.vidyard.com/LvuodGrotYM31Cp1fbGWVU.html",
    "accessPolicy": "latest_free_until_replaced",
    "feedGeneratedAt": "2026-08-31T20:41:19.880Z"
  },
  "replayNote": null
}
```

### `get_team_status`: Get team status

Shows the signed-in member's team (the people they personally sponsored, as on HOP's Mentor Report) and who is set up on the system, so the member can help their business builders get onboarded. Each team member has a status: not_set_up (no Enhance contacts account), lapsed (subscription not active), never_logged_in, inactive (no sign-in in inactiveDays, default 30) or active, plus lastLoginAt, companyStatus (e.g. their rank), email, phone, contactId (their record in the member's own contacts, for get_contact_profile) and suggestedActions. Members come sorted with who needs something first; summary has the counts. scope "downline" covers the whole downline instead of personal enrollees. FREE RESOURCES COME FIRST: everyone on the team should be sent the free resources (freeResources.url, enhancebyplatinum.com/free). freeResources.sent per member is true when the member already sent that link through Send Information, false when they have not, and null when HOP cannot tell (no Send Information item for it, the person is not in their contacts, or it went out in a Response Magic email). Treat null as "probably not sent" but say it may have gone by email. To share it, use the member's Send Information item (freeResources.sendInfoItem) or their own email/list tools; never send anything without the member's OK. Keep the message exciting and helpful, never salesy, e.g.: "Hey {first name}! I wanted to make sure you have these: our free resources are a great way to get the most out of everything available to you. Take a look when you get a minute: {link}". Other actions: invite_to_set_up (help them get their Enhance account going), reactivate_subscription, help_first_login, check_in (a friendly personal note, not a reminder to log in). Read-only.

| Input | Type | Required | Description |
| --- | --- | --- | --- |
| `scope` | string | no | direct (default): people the member personally sponsored. downline: everyone below them. |
| `inactiveDays` | integer | no | No sign-in for more than this many days counts as inactive (1-365, default 30). |

**Example call:**

```
{}
```

**Example result** (abbreviated):

```
{
  "scope": "direct",
  "inactiveDays": 30,
  "freeResources": {
    "url": "https://www.enhancebyplatinum.com/free",
    "sendInfoItem": {
      "typeId": 2,
      "resourceId": 311,
      "title": "Free Resources",
      "category": "Team"
    },
    "trackedVia": "send_information"
  },
  "summary": {
    "total": 2,
    "byStatus": {
      "not_set_up": 1,
      "lapsed": 0,
      "never_logged_in": 0,
      "inactive": 0,
      "active": 1
    },
    "freeResourcesNotSent": 1,
    "freeResourcesUnknown": 0
  },
  "members": [
    {
      "resellerId": 5512,
      "name": "Dana Ruiz",
      "username": "danaruiz",
      "email": "dana@example.com",
      "phone": null,
      "sponsorResellerId": 4410,
      "joinedAt": "2026-09-02",
      "companyStatus": "Director",
      "status": "not_set_up",
      "hasContactsAccount": false,
      "subscriptionActive": false,
      "lastLoginAt": "2026-10-11 19:02:44",
      "contactId": 87290012,
      "freeResources": {
        "sent": false,
        "lastSentAt": null
      },
      "suggestedActions": [
        "send_free_resources",
        "invite_to_set_up"
      ]
    },
    {
      "resellerId": 5390,
      "name": "Lee Park",
      "username": "leepark",
      "email": "lee@example.com",
      "phone": "555-0101",
      "sponsorResellerId": 4410,
      "joinedAt": "2026-03-14",
      "companyStatus": "Senior Director",
      "status": "active",
      "hasContactsAccount": true,
      "subscriptionActive": true,
      "lastLoginAt": "2026-10-20 08:15:10",
      "contactId": 87201144,
      "freeResources": {
        "sent": true,
        "lastSentAt": "2026-10-02"
      },
      "suggestedActions": []
    }
  ],
  "truncated": false
}
```

### `get_ad_tracking_codes`: Get ad tracking codes

Shows the signed-in member's ad and analytics tracking codes (e.g. Meta / Facebook pixel, Google Analytics or Ads tag, TikTok pixel) for each of their sites, as on HOP My Settings > Tracking Codes. Codes are saved per site (domain), not per funnel: every page on that site shares them. Each site has two codes: home (Home/Capture Page Code, on the landing pages) and conversion (Conversion/Thank You Page Code, on the page after someone signs up, where ad platforms count a lead). Each code is null when nothing is saved, or tags (type + id, e.g. meta_pixel 1234567890123, google_analytics G-…, google_ads AW-…), metaEvents (the Meta events it fires, e.g. PageView, Lead), recognized, and the saved code itself. shownOnPages false means that site does not put tracking codes on its pages at all, so saved codes there are not running. problems lists what is wrong in plain words (codes not running, no conversion code, a conversion code that fires no Meta conversion event, an unrecognized code, old Universal Analytics ids). Optional siteId (a domainId from a previous call) limits it to one site. Use it for "is my Facebook pixel set up?" or before running ads: a missing conversion code means the ad platform cannot see signups. Read-only: changing codes is done in HOP for now (My Settings > Tracking Codes).

| Input | Type | Required | Description |
| --- | --- | --- | --- |
| `siteId` | integer | no | Only this site: a domainId from a previous get_ad_tracking_codes call. |

**Example call:**

```
{}
```

**Example result** (abbreviated):

```
{
  "sites": [
    {
      "domainId": 1373,
      "domain": "momswithaplan.net",
      "shownOnPages": true,
      "isSet": true,
      "home": {
        "tags": [
          {
            "type": "meta_pixel",
            "id": "1234567890123"
          }
        ],
        "metaEvents": [
          "PageView"
        ],
        "recognized": true,
        "code": "<script>…</script>",
        "truncated": false
      },
      "conversion": {
        "tags": [
          {
            "type": "meta_pixel",
            "id": "1234567890123"
          }
        ],
        "metaEvents": [
          "PageView",
          "Lead"
        ],
        "recognized": true,
        "code": "<script>…</script>",
        "truncated": false
      }
    },
    {
      "domainId": 1374,
      "domain": "familieswithaplan.com",
      "shownOnPages": true,
      "isSet": false,
      "home": null,
      "conversion": null
    }
  ],
  "problems": []
}
```

### `verify_scheduler_embed`: Verify scheduler embed

Checks whether the signed-in member's funnel pages carry a scheduler: the booking widget (Calendly or Elevate / HighLevel) that lets prospects self-book an overview call. Standalone: takes no input. The scheduler is the member's Custom Value "Calendly/Scheduler Embed Code" (HOP: My Settings > Custom Values; label says which). scheduler is what the member saved: saved, provider (calendly, highlevel = Elevate booking widget, other, unrecognized = saved but no booking link in it, none) and bookingUrl, their own booking link. funnels lists each of their funnel sites (domain, the websites on it) with status: ok; missing (no scheduler: prospects cannot book from those pages); team_default (the member never saved one, so the pages show the team owner's calendar and prospects would book with the team owner, not the member: treat as a problem); unrecognized (something is saved but it is not a working embed); custom_values_off (that site does not use Custom Values). problems says what is wrong in plain words. configured: false means the team has no scheduler Custom Value. It checks the saved setting, not the live page: it cannot tell whether a Calendly or Elevate calendar has open times. Next: for missing, team_default or unrecognized, walk the member through copying the embed code from their Calendly or Elevate calendar's share / embed option into My Settings > Custom Values, then call this again; open bookingUrl to try a booking. Read-only.

**Input:** none.

**Example call:**

```
{}
```

**Example result** (abbreviated):

```
{
  "configured": true,
  "label": {
    "name": "Calendly/Scheduler Embed Code",
    "kind": "text",
    "memberEditable": true
  },
  "scheduler": {
    "saved": true,
    "provider": "calendly",
    "bookingUrl": "https://calendly.com/jane-doe/30min"
  },
  "funnels": [
    {
      "domainId": 1373,
      "domain": "momswithaplan.net",
      "websites": [
        "Moms with a Plan",
        "Scheduling Page"
      ],
      "status": "ok",
      "provider": "calendly",
      "source": "member"
    },
    {
      "domainId": 1390,
      "domain": "americaonamission.info",
      "websites": [
        "America on a Mission"
      ],
      "status": "ok",
      "provider": "calendly",
      "source": "member"
    }
  ],
  "problems": []
}
```

### `get_elevate_webhook_status`: Get Elevate webhook status

Checks the signed-in member's Elevate webhook: the link that auto-posts every lead from their website forms into their Elevate (HighLevel / LeadConnector) system, set in HOP under My Settings > Elevate Integration. Standalone: takes no input. health is the answer: not_configured (no webhook saved: leads stay in HOP only), broken (leads are NOT reaching Elevate now: the saved link is wrong, or the newest lead was lost), retrying (the newest lead is queued and being retried), lost_leads (working now, but some earlier leads never arrived), ok, no_recent_leads (set up, but no leads in the last days to prove it), or unknown (HOP could not read the delivery records). problems says why in plain words; for broken and lost_leads, say it plainly and pass on what to fix. webhook describes the saved link (host, isLeadConnector, hasLeadFields) without revealing it. counts and recent cover the last `days` days of leads (recent: newest 5, each delivered, queued, failed or not_configured); retries and lostLeads come from the retry queue (lostLeads = given up after about a day, with the contact email so the member can add them to Elevate by hand). offered: false means the team has no Elevate Integration page. Limits: delivered means our relay (Hookdeck) accepted the lead, which then delivers it to Elevate and retries on its own; a workflow deleted or switched off in Elevate does not show here, so if health is ok but leads are missing in Elevate, have the member check the inbound-webhook workflow there. Read-only: it never sends a test lead. Next: for not_configured or a wrong link, walk the member through copying the inbound webhook URL from their Elevate workflow trigger into My Settings > Elevate Integration; for lost leads, look the contacts up with search_contacts.

**Input:** none.

**Example call:**

```
{}
```

**Example result** (abbreviated):

```
{
  "offered": true,
  "configured": true,
  "health": "lost_leads",
  "problems": [
    "1 lead(s) in the last 30 days were retried for about a day and then given up: they never reached HighLevel (see lostLeads)."
  ],
  "webhook": {
    "host": "services.leadconnectorhq.com",
    "isLeadConnector": true,
    "hasLeadFields": true
  },
  "days": 30,
  "lastLeadAt": "2026-10-18 10:02:11",
  "lastDeliveredAt": "2026-10-18 10:02:11",
  "counts": {
    "leadsSent": 14,
    "delivered": 13,
    "queuedForRetry": 1,
    "failed": 0,
    "notConfigured": 0
  },
  "retries": {
    "waiting": 0,
    "deliveredLater": 0,
    "gaveUp": 1
  },
  "recent": [
    {
      "at": "2026-10-18 10:02:11",
      "site": "momswithaplan.net",
      "contactEmail": "jane@example.com",
      "outcome": "delivered",
      "detail": null
    },
    "… newest 5"
  ],
  "lostLeads": [
    {
      "at": "2026-10-03 21:40:05",
      "contactEmail": "sam@example.com",
      "lastError": "curl 6: Could not resolve host"
    }
  ],
  "unavailable": []
}
```

### `get_profile_completeness`: Get profile completeness

Checks whether the signed-in member's HOP profile is ready for activation: a profile photo uploaded and approved, and a bio written, submitted and approved (an approved bio shows on their website, e.g. the About Me section). Standalone: takes no input. Returns photo and bio (each with status approved, pending, denied, or not_uploaded / not_submitted), complete, and missing: exactly what is left, each with a todo saying what to do and where in HOP (My Profile, and its Bio tab). A denied bio may carry the administrator's denialComment; pass it on. pending means it is waiting for an administrator, so there is nothing for the member to do but wait. offered: false means the team does not use that item, and it is never listed as missing. Use it when coaching a new member through setup or when they ask "what do I still need to do?".

**Input:** none.

**Example call:**

```
{}
```

**Example result** (abbreviated):

```
{
  "photo": {
    "offered": true,
    "uploaded": true,
    "approved": false,
    "status": "pending"
  },
  "bio": {
    "offered": true,
    "submitted": false,
    "approved": false,
    "status": "not_submitted",
    "denialComment": null
  },
  "complete": false,
  "missing": [
    {
      "item": "photo",
      "status": "pending",
      "todo": "Wait for an administrator to approve the profile photo."
    },
    {
      "item": "bio",
      "status": "not_submitted",
      "todo": "Write a bio on My Profile > Bio and submit it."
    }
  ]
}
```

### `add_contact`: Add contact

Adds a person to the signed-in member's HOP contacts, the same way HOP's own Add Contact page does. This is a WRITE: it creates a real contact. Use it when the member met someone outside their funnels (a Facebook or Instagram conversation, an event, a referral) and wants them in Enhance. BEFORE CALLING: show the member exactly what you will add (name, email, phone, list, status) and get their OK; never add people on your own initiative or in bulk. Only firstName is required: add an email, phone, last name and facebookId when the member has them. A name-only contact (e.g. someone met in a Facebook conversation) is saved with a placeholder @noemail.com address, as bounced, so HOP never emails them until a real email is added. IMPORTANT: being on a list starts that list's email sequence, as in HOP: when sequence is set in the result, the first email goes out at sequence.firstEmailAt (often right away). Tell the member which list you will use before adding, and choose a list without a sequence if they only want the contact saved (listName; unknown names are refused with the member's list names). With no email, or an email domain that cannot receive mail, the contact is saved as bounced and gets no emails. status is the contact status by the name the member sees (default: the first one). sourceNote says where they met (stored in the origin as "Added via agent: ..."); note adds a note to the contact history. No confirmation or other email is sent by this tool. It checks for duplicates first (facebookId, then email, then phone, then exact name): created false means the person is already in their contacts; say so and use contactId (get_contact_profile) instead of adding again, so calling it twice is safe. Refusals (invalid email, a globally opted-out email, an active member, or another member's contact when the team does not transfer contacts) come back as an error with the reason in plain words: pass it on. Another member's inactive contact follows the team's HOP lead transfer setting, as Add Contact: teamRecord "transferred" means the person now belongs to this member (tell the member), "kept_other_sponsor" means they were added but stay with the other sponsor. After adding, the contact is in search_contacts right away; next steps are usually a personal message or an item from list_send_info_items. facebookId stores the person's numeric Facebook id on the contact (facebookIdSaved in the result); Instagram ids and message threads are not stored yet.

| Input | Type | Required | Description |
| --- | --- | --- | --- |
| `firstName` | string, max 30 chars | yes | First name (required, at most 30 characters). |
| `lastName` | string, max 30 chars | no | Last name (at most 30 characters). |
| `email` | string, max 100 chars | no | Email address. Leave out if unknown. |
| `phone` | string, max 25 chars | no | Phone number, any format. Leave out if unknown. |
| `facebookId` | string | no | The person's numeric Facebook id (digits only, e.g. 100012345678901). Not a profile name or link; leave out if unknown. |
| `listName` | string, max 100 chars | no | The member's list to put them on, by name (default: their first list, usually New Prospects, which has no emails). Being on a list starts its email sequence. |
| `status` | string, max 100 chars | no | Contact status by the name the member sees (default: the first one, usually New Prospect). |
| `sourceNote` | string, max 200 chars | no | Where the member met them, e.g. "Facebook message" or "Moms group meetup". Stored in the origin. |
| `note` | string, max 2000 chars | no | A note for the contact history. |

**Example call:**

```
{"firstName":"Jane","lastName":"Doe","email":"jane@example.com","phone":"519-555-0101","listName":"MomsWithaPlan Prospects","sourceNote":"Facebook message"}
```

**Example result** (abbreviated):

```
{
  "created": true,
  "contactId": 87310455,
  "contact": {
    "contactId": 87310455,
    "firstName": "Jane",
    "lastName": "Doe",
    "email": "jane@example.com",
    "phone": "519-555-0101",
    "status": "New Prospect",
    "list": "MomsWithaPlan Prospects",
    "emailStatus": "active",
    "dateAdded": "2026-10-21"
  },
  "list": "MomsWithaPlan Prospects",
  "status": "New Prospect",
  "origin": "Added via agent: Facebook message",
  "facebookId": null,
  "facebookIdSaved": null,
  "emailSaved": "jane@example.com",
  "bounced": false,
  "bouncedReason": null,
  "sequence": {
    "list": "MomsWithaPlan Prospects",
    "firstEmailInDays": 0,
    "firstEmailAt": "2026-10-21 14:05:12",
    "held": false
  },
  "teamRecord": "created",
  "warnings": []
}
```

**Result:** Already in their contacts: {created: false, matchedOn: "facebookId" | "email" | "phone" | "name", contactId, contact, message}. Name only ({firstName: "Jane", lastName: "Doe"}): created with emailSaved like "janedoe48213@noemail.com" and bounced true.

### `get_activation_status`: Get activation status

Where the signed-in member is in getting their business going: ten first-time milestones, in order, each with whether it was reached, when, and the evidence (source, detail, contactId). Milestones: signup, first_view (first tracked visit to their site), first_lead (first contact), first_outbound (first personal outreach: Send Information, call, notes), first_response (a contact opened a link, clicked an email, or looked at the calendar / presentation), questionnaire (a contact completed a questionnaire or reached the Questionnaires tab), first_appointment (a contact booked a call through their scheduler, an appointment in their HOP calendar, or a contact in the Scheduled tab), first_overview (a contact saw the presentation / overview), first_customer (a contact the team counts as a customer: on Enhance a Category One / Two / Three status; on other teams a shopper / enrolled / builder tab, or a sale) and first_business_builder (someone joined their team). Standalone: takes no input. stage is the furthest milestone reached; skipped lists earlier milestones HOP never saw (e.g. no tracked site visit when every lead was added by hand: an established member is not held back by them); next is the first unreached milestone after the stage, else the earliest skipped one; daysAtStage is the days since their most recent milestone. nextStep is the concrete next action with url (a direct link into HOP) and tools (platinum-mcp tools that help do it, e.g. get_daily_outreach_actions). With no contacts account only signup is known and nextStep is setting one up; an incomplete profile (photo/bio) comes first while there has been no outreach. complete true means every milestone is reached: celebrate, then move to growing (get_daily_outreach_actions, get_team_status). Dates come from HOP records; a milestone with date null was reached but HOP has no date for it. A customer who enrolled without the member ever changing the contact's status in HOP is not seen. Use it for "how am I doing?", progress check-ins and coaching; for just "what should I do next?" call get_next_activation_step. Read-only.

**Input:** none.

**Example call:**

```
{}
```

**Example result** (abbreviated):

```
{
  "date": "2026-10-21",
  "hasContactsAccount": true,
  "stage": "first_outbound",
  "stageLabel": "First outreach",
  "stageReachedOn": "2026-09-30 14:02:11",
  "daysAtStage": 21,
  "lastProgressOn": "2026-09-30 14:02:11",
  "daysSinceLastProgress": 21,
  "complete": false,
  "next": "first_response",
  "nextLabel": "First response",
  "skipped": [],
  "reachedCount": 4,
  "totalMilestones": 10,
  "nextStep": {
    "step": "first_response",
    "milestone": "first_response",
    "action": "Follow up personally with the contacts you sent information to, and send something new to those who have not opened anything.",
    "page": "Contacts",
    "url": "https://www.homeofficepro.net/v3/contacts?m=1",
    "tools": [
      "get_daily_outreach_actions",
      "get_quiet_contacts"
    ],
    "missing": []
  },
  "profileComplete": true,
  "milestones": [
    {
      "milestone": "signup",
      "label": "Signed up",
      "reached": true,
      "date": "2026-09-02 10:14:00",
      "evidence": {
        "date": "2026-09-02 10:14:00",
        "source": "member record",
        "detail": "Joined",
        "contactId": null
      }
    },
    {
      "milestone": "first_outbound",
      "label": "First outreach",
      "reached": true,
      "date": "2026-09-30 14:02:11",
      "evidence": {
        "date": "2026-09-30 14:02:11",
        "source": "history",
        "detail": "Send Information",
        "contactId": 87290012
      }
    },
    {
      "milestone": "first_response",
      "label": "First response",
      "reached": false,
      "date": null,
      "evidence": null
    },
    "… all ten, in order"
  ],
  "sourcesUnavailable": []
}
```

### `get_next_activation_step`: Get next activation step

The one thing the signed-in member should do next to get their business going, how long they have been stuck, and a one-click link to do it. CALL THIS WHEN THE MEMBER ASKS "what should I do next?", "where do I start?" or "what now?", and when you check in with a member who has gone quiet. Standalone: takes no input. Returns stage (the milestone they are at) with stageLabel, daysAtStage (days since their most recent milestone, from real HOP dates; null when HOP has no date), skipped (earlier milestones HOP never saw), next / nextLabel (the milestone this step reaches), nextStep {action (say this in your own words), page and url (a direct HOP link: give it so they can do it in one click), tools (platinum-mcp tools that help: call them to make the step concrete, e.g. get_daily_outreach_actions for who to contact, list_recorded_overviews for which overview to show), missing (for the profile step: what is left)}, progress (reachedCount of totalMilestones) and complete. Nudge, never nag: the longer daysAtStage, the smaller and more specific the step you suggest (one contact, one message). This tool only computes the nudge; you decide when to bring it up. nextStep null with complete true means every milestone is reached. For the full milestone list with dates and evidence, call get_activation_status. Read-only.

**Input:** none.

**Example call:**

```
{}
```

**Example result** (abbreviated):

```
{
  "stage": "first_lead",
  "stageLabel": "First lead",
  "daysAtStage": 12,
  "next": "first_outbound",
  "nextLabel": "First outreach",
  "nextStep": {
    "step": "first_outbound",
    "milestone": "first_outbound",
    "action": "Reach out to a contact: send them information through Send Information, so you see when they open it.",
    "page": "Send Information",
    "url": "https://www.homeofficepro.net/v3/contacts/send-information",
    "tools": [
      "get_daily_outreach_actions",
      "list_send_info_items"
    ],
    "missing": []
  },
  "progress": {
    "reachedCount": 3,
    "totalMilestones": 10
  },
  "complete": false,
  "skipped": [],
  "stageEvidence": {
    "date": "2026-10-09 16:40:02",
    "source": "contacts",
    "detail": "Jane Doe (origin: momswithaplan.net)",
    "contactId": 87301122
  }
}
```

### `list_my_websites`: List my websites

Lists the signed-in member's own marketing website and funnel links, the same ones as HOP's Marketing Websites page. Standalone: takes no input. Each has type (site or funnel), name, purpose (who it is for, when HOP has one), description (the team's own note on who that funnel speaks to, when it has one), domain, and url: the member's personal link, which credits leads to them. Give links exactly as returned, never rebuild or shorten them. isDefault marks the main site of each domain. needsUpgrade: true means the item needs a HOP subscription the member does not have; HOP sends them to its upgrade page instead, so say so rather than suggesting they share it. url is null when HOP cannot build the link (no website username, or a funnel without pages). Use it for "what is my website link?" or to give the member a link to share. To recommend which one to promote, you choose: ask the member 1-3 short questions (who they are, who they want to reach, the tone they want), then match their answers to purpose and description, following guidance (how the team chooses, when it has some) and citing it; say why, mention a close alternative, and give the url exactly as returned. Do not prefer a site for reasons the data does not give. Read-only. Tracked links for a single contact come from Send Information, not from here.

**Input:** none.

**Example call:**

```
{}
```

**Example result** (abbreviated):

```
{
  "username": "jane",
  "websites": [
    {
      "type": "site",
      "id": 9,
      "domainId": 1373,
      "domain": "momswithaplan.net",
      "name": "Moms with a Plan",
      "purpose": "Moms who want to work from home",
      "description": "Moms With a Plan: speaks as a mom to busy moms. The best-performing Enhance funnel.",
      "url": "https://momswithaplan.net/jane",
      "isDefault": true,
      "needsUpgrade": false
    },
    "… by domain, main site first"
  ],
  "total": 6,
  "guidance": "Recommend by the audience the member wants to reach, and pick the funnel whose voice matches that audience so it feels relatable. …"
}
```

### `get_pipeline_stage`: Get contact pipeline stage

Says which pipeline stage one of the signed-in member's contacts is in: the tab HOP's Contacts page shows them under. The stages are the member's team's own tabs (set by the team in PSG Admin, e.g. New Prospects, Callbacks, Needs Appointment), and a contact is under a tab when their contact status is one of that tab's statuses. stage is that tab's name (null when no tab holds their status: HOP then shows them only under All); alsoUnder lists any other tabs that hold the same status. evidence says why: status (the contact status the member set), statusSet (when and how it was last set; null if HOP never logged it, e.g. it came with an import), and recentHistory (the 3 latest history entries, newest first) with historyTotal. pipeline is the team's whole pipeline in tab order, each stage with the statuses under it: use it to say what the next stage is and which status would move the contact there. Quote stage names as returned; teams name their tabs differently. Needs a contactId from search_contacts. Read-only: it never changes a status. Next: get_contact_profile for the full history, or suggest the next step for that stage (e.g. set an appointment for Needs Appointment).

| Input | Type | Required | Description |
| --- | --- | --- | --- |
| `contactId` | integer | yes | The contactId from search_contacts. |

**Example call:**

```
{"contactId":1234567}
```

**Example result** (abbreviated):

```
{
  "contactId": 1234567,
  "stage": "Needs Appointment",
  "stageId": 3,
  "alsoUnder": [],
  "evidence": {
    "status": "Hot Prospect",
    "statusSet": {
      "date": "2026-10-01 14:02:00",
      "action": "Status Changed"
    },
    "recentHistory": [
      {
        "date": "2026-10-12 09:15:00",
        "action": "Send Information",
        "…": "same fields as get_contact_profile history"
      },
      "… up to 3, newest first"
    ],
    "historyTotal": 17
  },
  "pipeline": [
    {
      "stageId": 1,
      "name": "New Prospects",
      "statuses": [
        "New Lead"
      ]
    },
    {
      "stageId": 2,
      "name": "Callbacks",
      "statuses": [
        "Call Back"
      ]
    },
    {
      "stageId": 3,
      "name": "Needs Appointment",
      "statuses": [
        "Hot Prospect",
        "Warm Prospect"
      ]
    },
    "… every tab, in HOP order"
  ]
}
```

### `get_product_checklist`: Get contact product checklist

Shows the product checklists one of the signed-in member's contacts completed on the member's website (e.g. the Shop Wellness "what you already buy" checklist), newest first, as HOP shows them under See Checklist Details on the contact page. Each checklist has score (the score HOP showed the contact), completedAt, language (en or es), itemCount, totals overall, and the categories they picked from. By default each category gives its itemCount, totals and topItems (the 3 items with the most savings), which is enough for a message; a checklist can have 150+ items. Pass includeItems: true only when the member wants the full list: each category then has items instead of topItems. Every item has points, regularPrice, preferredPrice and savings; helpsWeightLoss / helpsImmunity appear only when true. This is the "switch stores, not your budget" data: they already spend about totals.regularPrice on these things elsewhere, would pay totals.preferredPrice as a preferred customer, and save totals.savings. Use the items they picked to personalize a message, and quote the numbers as returned. Some teams show only item names: then score, totals and the prices are null or left out. completed: false (empty checklists) means the contact never completed one; that is a normal answer, not an error. unknownItemIds are picked items HOP no longer has. Needs a contactId from search_contacts. Read-only. Next: suggest a follow-up message, or a product video from list_send_info_items.

| Input | Type | Required | Description |
| --- | --- | --- | --- |
| `contactId` | integer | yes | The contactId from search_contacts. |
| `includeItems` | boolean | no | true: list every item picked in each category instead of the top 3 (default false; long for big checklists). |

**Example call:**

```
{"contactId":1234567}
```

**Example result** (abbreviated):

```
{
  "contactId": 1234567,
  "completed": true,
  "checklists": [
    {
      "historyId": 99123,
      "completedAt": "2026-10-15 08:00",
      "language": "en",
      "checklistName": null,
      "score": 35,
      "totals": {
        "points": 35,
        "regularPrice": 142.5,
        "preferredPrice": 108.25,
        "savings": 34.25
      },
      "itemCount": 6,
      "itemsIncluded": false,
      "categories": [
        {
          "name": "Laundry",
          "itemCount": 2,
          "totals": {
            "points": 8,
            "regularPrice": 22,
            "preferredPrice": 16.49,
            "savings": 5.51
          },
          "topItems": [
            {
              "id": 12,
              "name": "Laundry detergent",
              "points": 5,
              "regularPrice": 12,
              "preferredPrice": 9.5,
              "savings": 2.5
            },
            "… up to 3, most savings first"
          ]
        },
        "… one entry per category"
      ],
      "unknownItemIds": []
    }
  ]
}
```

### `get_usage_guide`: Get usage guide

Returns the full usage guide for this server as Markdown: what each tool does, its inputs, examples, permissions, how to combine tools into workflows, and what each error means. Call it once if you are unsure which tool to use or how to chain them.

**Input:** none.

**Example call:**

```
{}
```

## Workflows: combining tools

### Get this week's posts for a brand

1. Call `get_latest_drop` with the brand the member named, e.g. `{"brand": "AOAM"}`.
2. `isUpcoming: true` means this is the next scheduled drop; `false` means no new drop is scheduled and this is the most recent one. Tell the member which.
3. Go through `pieces` in `position` order. Use each `caption` exactly as written, with its `assets` in the order given (a carousel lists its slides in order).
4. Use the member's `funnelUrl` wherever a post needs a link, such as the link in bio or a story link sticker.
5. Show the member what will be posted and get their OK before posting or scheduling anything anywhere.

### Browse or compare past weeks

1. Call `list_drops`, optionally with `brand`, to see the available weeks and piece counts.
2. Call `get_drop` with the `dropId` of the week you want for its captions and media.

### The member names a brand you don't recognise

1. Call `list_drops` with no input. `brands[]` lists every brand available to the member, with its display name and aliases.
2. Pick the matching brand and call `get_latest_drop` or `list_drops` with it.

### Find a contact the member mentions

1. Call `search_contacts` with what the member said, e.g. `{"query": "jane smith"}`. Each word must match the start of a first name, last name, phone or email; email domains and phone numbers in any format also work.
2. If several contacts match, show the names with their email or city and ask which one. If `matchedLoosely` is true, say these are near matches. If none match, try fewer words (just the first or last name).
3. Check `emailStatus` before suggesting an email: never email `opted_out` or `bounced` contacts.

### Catch up on a contact before following up

1. Find the contact with `search_contacts` and take its `contactId`.
2. Call `get_contact_profile` with it. Read `history` (newest first): the last call `outcome`, notes, and status changes tell you where things stand.
3. Check `upcomingAppointments` first; if one is booked, help the member prepare for it instead of suggesting a new follow-up.
4. Suggest a time from `bestTimeToCall` and the contact's `timezone`. Don't promise anything the history doesn't show.
5. Use `survey` (what the contact answered on HOP forms and questionnaires) to personalise the follow-up.

### List contacts that fit a description

1. Use the filters instead of fetching everything: e.g. new leads this week `{"addedSince": "2026-10-13"}`, people who can be emailed `{"emailable": true}`, or one stage `{"status": "Hot Prospect"}`. Filters combine with each other and with `query`.
2. Use `total` to say how many there are; page with `offset` only if the member wants more than the first page.
3. If `status` is rejected, the error lists the names this member uses. Pick the closest one, or ask the member.

### Suggest what to send a contact

1. Learn about the contact: `get_contact_profile` (status, history, `survey`, and `sendInfoSent`: what they already got), `get_pipeline_stage` and `get_contact_origin` (the site or ad they came in through).
2. Look through the library: `list_send_info_items` with a `query`, e.g. `{"query": "appointment"}`, or browse with `list_send_info_categories` then `list_send_info_items {"categoryId": …}`.
3. You choose: suggest one or two items that fit where the contact is and who they are, by title, and say why from what you read (`description` helps). For a video, offer its `previewUrl` so the member can watch it first. Don't suggest something in `sendInfoSent` unless the member asks.
4. Draft the message from the item's `exampleMessage` when it has one: it is HOP's approved wording. Without one, write a short personal message and say it is your suggestion.
5. These tools only read the library. Sending happens in HOP for now.

### Show a contact the business overview

1. Call `list_recorded_overviews` to see the overviews, their `description` and `playsOn` (where it is hosted, not who it is for).
2. Find the contact with `search_contacts`; `get_contact_origin` shows the site or ad they came in through and `get_contact_profile` their status and history.
3. Choose the overview that fits that contact and the conversation, and say why. If nothing points to one, ask the member who the contact is or offer the choices.
4. Pass on `playbook`: the best way is to set up a call or Zoom and watch the overview live together, rather than only sending the link. Offer `previewUrl` so the member can watch it first.
5. To send it, the member uses Send Information in HOP; draft the message from the overview's `exampleMessage`.

### Catch up on what happened

1. Call `get_notifications`, e.g. `{"since": "2026-10-14"}` for everything since yesterday, or `{"type": "presentation_viewed"}` for who watched a presentation, or `{"type": "calendar_viewed"}` for who looked at the calendar.
2. For a notification with a `contactId`, call `get_contact_profile` with it before suggesting a follow-up.

### Find out how a contact found the member

1. Find the contact with `search_contacts`, then call `get_contact_origin` with its `contactId`.
2. `promoCodes[].matches[].adCampaigns` names the ad campaign when the code is linked to one; `visits` shows the site and pages they saw first.
3. If `visits` and `promoCodes` are empty, HOP has no tracking for that contact (often added by hand or imported). Say so rather than guessing from `origin`.

### See whether a contact is reading the emails

1. Find the contact with `search_contacts`, then call `get_contact_email_engagement` with its `contactId`.
2. Lead with `score.total` and say what it is made of (`score.parts`); a 0 means nothing recorded, not that the contact is cold for sure.
3. `sequence` says where they are in the drip (next email and when); `opens.recent` and `emailClicks.recent` say which emails caught their interest.
4. Someone who opens or clicks but never replied is a good follow-up: reference what they looked at.

### Find contacts who have gone quiet

1. Call `get_quiet_contacts`, e.g. `{}` for two weeks, `{"daysWithoutMessage": 30, "status": "Hot Prospect"}` for warm leads left a month.
2. Start with the longest quiet. For each one you suggest, read `get_contact_profile` first: an upcoming appointment or a recent note changes the advice.
3. HOP only sees logged outreach. If the member says they texted someone, take their word for it and suggest they log a note.
4. Suggest one personal message per contact, with a Send Information item from `list_send_info_items` when one fits.

### When is the next Leadership Connection?

1. Call `get_upcoming_leadership_connection` (no input). Give `next.startLocal` (convert from Eastern if you know the member's time zone) and `next.link`.
2. Before a session (e.g. the day before or the morning of), remind the member with the time and link.
3. If they missed one, call `get_latest_replay` and share `latestReplay.url` with when it was recorded.
4. Leadership Connection is for members enrolled in Melaleuca, not prospects. If there is no schedule (`note`), send them to the Events calendar in HOP (`calendarPage`).

### Add someone I just met

1. Collect at least a first name; add last name, email, phone and Facebook id (`facebookId`, digits only) if they have them. A name-only contact is saved as bounced (no emails) until a real email is added. Ask where they met (`sourceNote`).
2. Pick the list with the member: being on a list starts its email sequence, as in HOP. If they only want the person saved, use a list without a sequence.
3. Show the member exactly what you will add and get their OK. Then call `add_contact` once.
4. `created: false` means they are already a contact: say so and use the returned `contactId`. Errors explain why HOP refused (e.g. they belong to another member): pass that on.
5. If `sequence` is set, tell the member when the first email goes out (`sequence.firstEmailAt`). Next: a personal message, or an item from `list_send_info_items`.

### What should I do next?

1. Call `get_next_activation_step` (no input). Say `nextStep.action` in your own words and give `nextStep.url` so they can do it in one click.
2. Make it concrete with the tools in `nextStep.tools` (e.g. `get_daily_outreach_actions` for who to contact, `list_recorded_overviews` for which overview to show).
3. The longer `daysAtStage`, the smaller the step: one contact, one message. Nudge, never nag.
4. For "how am I doing?", call `get_activation_status` and walk through the milestones reached (with dates) and what is next.

### Who should I reach out to today?

1. Call `get_daily_outreach_actions` (`{"limit": 5}` for a shorter list).
2. Give a short to-do list: for each action the contact name, `why` as written (it cites the signal and its date), then the `followUp` line.
3. If an item should go with it, choose one from `list_send_info_items` that fits what they just did, skipping what is in `sendInfoSent`. Before writing a message for someone, read `get_contact_profile` for recent notes or appointments.
4. Contacts with `emailStatus` opted_out or bounced get a call or text, never an email. Nothing is sent without the member's OK.

### Who on my team still needs help getting started?

1. Call `get_team_status` (`{"scope": "downline"}` for everyone below the member, not just personal enrollees).
2. Lead with the free resources: list who has `freeResources.sent` false or null and offer to share `freeResources.url`, with the member's Send Information item (`freeResources.sendInfoItem`) or their email tools. Draft one short, upbeat, helpful message (never salesy) and get the member's OK before anything is sent.
3. Then go through the rest by `status`: `not_set_up` (invite them to set up Enhance), `lapsed`, `never_logged_in`, `inactive` (a personal check-in). `contactId` opens the person in the member's contacts (`get_contact_profile`).
4. `sent: null` means HOP cannot tell (the link may have gone out by email); say so rather than claiming it was never sent.

### How is my lead rotator doing?

1. Call `list_lead_rotators` to find the rotator, then `get_rotator_distribution` with its `rotatorId`.
2. Summarize who got leads in the period (`sharePercent`) and go through `notes` (no members, everyone inactive, no ad links, an active member getting nothing).
3. For ads, compare `leads` and `conversionPercent` across links; the link to put in an ad is `url`.
4. Adding members or switching them on/off is done in HOP: Marketing > Lead Rotators.

### Is my Facebook pixel set up?

1. Call `get_ad_tracking_codes` (no input) and look at the site the member advertises.
2. Say which tags each site has (`tags`, e.g. Meta pixel id) and go through `problems`. A missing `conversion` code, or one whose Meta pixel fires no `Lead` event, means the ad platform cannot count signups.
3. `shownOnPages: false` means that site never runs tracking codes, whatever is saved: suggest advertising a site where it is true.
4. Changing codes is done in HOP: My Settings > Tracking Codes, pick the site, paste the codes, Save.

### Can prospects book a call with me?

1. Call `verify_scheduler_embed` (no input).
2. If every funnel is `ok`, say which calendar it is (`provider`) and offer `bookingUrl` so the member can try a booking.
3. For `missing`, `team_default` (pages show the team owner's calendar) or `unrecognized`, go through `problems`, then walk the member through pasting the embed code from Calendly or their Elevate calendar into My Settings > Custom Values, and check again.

### Are my leads reaching Elevate?

1. Call `get_elevate_webhook_status` (no input).
2. Lead with `health`. For `broken` or `lost_leads`, say so plainly and go through `problems`; for `lostLeads`, offer the contact emails so the member can add them to Elevate by hand.
3. For `not_configured` or a wrong link, the fix is in HOP: My Settings > Elevate Integration, pasting the inbound webhook URL from the Elevate workflow trigger.
4. If `health` is `ok` but leads are missing in Elevate, the problem is on the Elevate side: have the member check that the inbound-webhook workflow exists and is published.

### Help a new member finish their profile

1. Call `get_profile_completeness` (no input).
2. If `complete` is true, say so. Otherwise go through `missing` in order and pass on each `todo`.
3. For a denied bio, share `bio.denialComment` if there is one and help the member rewrite the bio. For anything `pending`, tell them it is waiting for an administrator; there is nothing to redo.

### Give the member their website link

1. Call `list_my_websites` (no input).
2. Pick by `purpose` and `name` for the audience, e.g. moms who want to work from home. The `isDefault` site is the safe choice when nothing fits better.
3. Give the `url` exactly as returned. If `needsUpgrade` is true, say the site needs a HOP subscription instead of handing out the link.

### Where is a contact in the pipeline?

1. Find the contact with `search_contacts`, then call `get_pipeline_stage {contactId}`.
2. `stage` is the tab HOP's Contacts page shows them under; `evidence` says why (their status, when it was set, the latest history). Quote the tab name as returned.
3. If `stage` is null, their status is not in any tab: say so, and use `pipeline` to name the status that would put them in one.
4. Use `pipeline` (the team's tabs in order) to say what the next stage is, then suggest the step that gets them there.

### Personalize a follow-up from a contact's product checklist

1. Find the contact with `search_contacts`, then call `get_product_checklist {contactId}`.
2. If `completed` is false, they never filled one in: suggest sending them the product checklist link from `list_my_websites` instead.
3. Otherwise use the newest checklist: name a few of the `topItems` they picked and quote `totals` as returned (they already spend `regularPrice`, would pay `preferredPrice`, save `savings`).
4. Only if the member wants every item, call again with `{"contactId": …, "includeItems": true}`.

### Recommend which website to promote

1. Call `list_my_websites`: each link has `purpose` and the team's `description`, and `guidance` says how the team chooses.
2. Ask 1-3 short questions about who the member is, who they want to reach and the tone they want.
3. Choose the site whose `purpose` / `description` fits, following `guidance`; say why, mention a close alternative, and give the `url` exactly as returned. If `guidance` encourages reaching people like themselves, pass that on.

### Check whether the member has been active in HOP

Call `get_last_login`. It needs no input and no other tool first.

## Guidance for agents

- Never ask the member for account, member or team ids. The connection already knows who they are.
- Brand names are flexible: the key, display name or an alias in any case all work (e.g. "AOAM", "America on a Mission").
- Captions are written to be posted as they are.
- Media URLs are public, direct links to the image or video file. Download or attach them as needed.
- Propose, then confirm: before posting, scheduling or sending anything on the member's behalf, show them what you will do and wait for their OK.

## Errors and what to do

| Message | Meaning | What to do |
| --- | --- | --- |
| HOP is busy right now (too many requests in the last minute). … | The member (or the server as a whole) went over the per-minute request allowance. | Wait a minute, then retry. When going through a long list, make fewer calls (e.g. use filters and paging) instead of one call per contact. |
| Social Media Drops aren't available for this member's team. | The member's team doesn't get drops. | Tell the member. Don't retry. |
| No drops found for that brand. Call list_drops to see the brands available to this member. | The brand wasn't recognised, or has no drops for this member. | Call `list_drops` and use a brand from `brands[]`. |
| That drop was not found or is not available yet. | The dropId is wrong, or that week isn't visible to the member yet. | Use a `dropId` from a fresh `list_drops` call. |
| This member's HOP account has no contacts account linked. | The member's HOP account isn't set up with contacts. | Tell the member. Don't retry. |
| This member's HOP subscription isn't active, so their contacts aren't available. | The member's HOP subscription has lapsed. | Tell the member to reactivate their subscription in HOP. Don't retry. |
| Unknown status "…". This member's statuses: … | That status name isn't one this member uses. | Retry with a name from the list, or ask the member. |
| That contact wasn't found. Use a contactId from search_contacts. | The contactId is wrong or isn't one of this member's contacts. | Search again with `search_contacts` and use a `contactId` from the results. |
| That category wasn't found. Use a categoryId from list_send_info_categories. | The categoryId is wrong or isn't one this member can see. | Call `list_send_info_categories` and use a `categoryId` from it. |
| Could not fetch … from HOP right now. | A temporary problem on the HOP side. | Try again in a few minutes. |
| HTTP 401: This app has been disconnected. Sign in again to reconnect. | The member disconnected the app or changed their HOP password. | The member needs to reconnect and sign in again. |
