Claude + HawkSoft:
what works today, and what doesn’t.

The gate: HawkSoft’s partner program

HawkSoft publishes its Partner API documentation openly, which is more than most systems do. Calling it is another matter: credentials go to technology vendors that serve independent agencies, after a security risk assessment and a signed letter of agreement. Direct AMS competitors are excluded.

HawkSoft’s API terms set an annual API fee of $3,000, paid in advance, which HawkSoft can waive. Each agency then switches on the data scopes a partner may use in its HawkSoft license portal.

• Client read access is always on; creating notes, tasks and attachments, accounting, new clients and the user list are separate scopes the agency grants.
• A single agency asking for its own key may be pointed to an existing partner instead.
• Products must say they use the HawkSoft API and may not be endorsed by HawkSoft.

What HawkSoft gives you, and what it doesn’t

HawkSoft has not announced an AI product of its own. Its AI story runs through marketplace partners: voice receptionists, AI CSRs and document tools that hold their own partner credentials and write tasks and notes into HawkSoft.

The Partner API itself:

• Read: agencies, offices, users, a single client, clients in batches of up to 200, and clients changed since a date.
• Search by exact policy number only, and that endpoint is still marked in development. There is no name search.
• Write: log notes (with an optional task), attachments up to 5 MB, receipts, and new “shell” clients for prospects.
• No webhooks: partners poll the changed-clients feed, usually every 1 to 24 hours.
• No Zapier or Make app.

How you would actually connect Claude to HawkSoft

With partner credentials, the bridge is an MCP server that tells Claude which HawkSoft actions exist and calls the Partner API when asked. Because the API cannot search by name, the bridge keeps its own copy of the client list.

1. 01
   Get partner credentials

   Through HawkSoft’s partner program: security review, letter of agreement, the API fee unless waived. Then the agency grants the scopes.
2. 02
   Mirror the client list

   Sync the changed-clients feed into a small database on a schedule, so Claude can find “the Martinez account” by name.
3. 03
   Build the MCP server

   Read tools over the mirror and the live client endpoint; write tools for notes, tasks and attachments. HawkSoft provides a sandbox install during onboarding.
4. 04
   Work out policy status yourself

   A client record reflects the last save in HawkSoft, and HawkSoft’s best-practices guide gives the rules for deciding which policies are active.
5. 05
   Expect delayed writes

   A write for an agency that is offline can come back as accepted and be applied the next time the agency connects.

The limits that actually matter

• No policy or coverage edits through the API. Endorsements still happen in HawkSoft by hand.
• No name search, so a useful bridge needs its own synced copy of the book.
• No webhooks, so nothing in HawkSoft can wake Claude up.
• The partner route costs money and time, and the agency must opt in to each scope.

Claude itself has one more limit on every AMS: it acts when someone asks, or on a scheduled task’s clock. It does not notice a new lead, a changed policy or a cancellation notice on its own. Anything that should happen because something changed in HawkSoft needs a listener running outside Claude.

If you want HawkSoft work that runs on its own

We are an engineering team that builds automation on top of the AMS an agency already runs. For HawkSoft that means one of two things: we build and host the bridge above so your team can ask Claude about the book, or we skip the chat window and build the workflow itself, triggered by HawkSoft events and checked by rules where a wrong number matters.

• A Claude connector on your HawkSoft book through the Partner API, with a nightly mirror so Claude can search by name.
• Call and email summaries filed as HawkSoft log notes with the right follow-up task, without a CSR typing them.
• Carrier portal and certificate work from the HawkSoft record, for the jobs the API does not cover.

The first build is live in 14 days for $2,499, charged only if your team is using it, then $2,499 a month flat. You keep the code. More on what we automate on top of HawkSoft.

Trucking agency? Our Market Tracker connector already works in Claude today: it answers carrier questions (filings, X-dates, safety, ISS) from the federal record, so the AMS bridge only has to carry your own book.

Claude + HawkSoft, answered.