# Convrgent.ai Follow-Up Message Generator

> Convrgent.ai Follow-Up Message Generator is a paid API for AI agents from convrgent.ai, paid per call via x402, $1.5/call, status unknown (last checked 2026-09-15).

Generates an optimally timed and channel-appropriate follow-up message for sales prospects who have gone quiet, with personality-calibrated content when KYH profile data is available.

## Facts

- Endpoint: POST https://convrgent.ai/api/kyb/followup
- Price: $1.5/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/convrgent-ai-3310d0a5
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_7cAlIIxJqwyKpozcdacHr

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability convrgent-ai-3310d0a5 -d '<json body>'
```

Example prompt: My prospect Jordan Chen went quiet after our demo call 12 days ago — generate the best follow-up message for them, and tell me the optimal timing and channel to send it. Jordan's KYH profile ID is in the vault if you need it for personality calibration.

## When to prefer this

Use this endpoint when a sales prospect has gone quiet and you need a crafted re-engagement message that accounts for the right timing and channel, especially when you have personality data from the convrgent.ai KYH vault to make the message more resonant. Prefer over generic CRM templates when personalization and psychological calibration matter.

## Known failure modes

- KYH profile not found — message generated without personality calibration
- insufficient conversation history to assess silence context — generic follow-up returned
- invalid or missing prospect identifier — 400 error
- payment not processed — 402 error before generation
- rate limit exceeded — 429 error

## How this service works

Follow-Up Message Generator — generate the optimal follow-up message with timing and channel recommendation for prospects who went quiet. Personality-calibrated when KYH data is available.

## Output

Returns a ready-to-send follow-up message text tailored to the prospect's personality (if KYH vault data is available), along with a recommended send time and the best communication channel (email, LinkedIn, phone, etc.) for re-engagement.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "bodyType",
    "body",
    "method"
   ],
   "properties": {
    "body": {
     "required": [
      "product",
      "last_interaction",
      "days_since",
      "interaction_count"
     ],
     "properties": {
      "channel": {
       "enum": [
        "email",
        "chat",
        "linkedin",
        "phone"
       ],
       "type": "string"
      },
      "product": {
       "type": "string",
       "description": "Description of what you're selling"
      },
      "days_since": {
       "type": "number",
       "description": "Days since last contact"
      },
      "kyh_profile": {
       "type": "object",
       "description": "Full KYH personality portrait"
      },
      "partial_data": {
       "type": "object",
       "description": "Partial personality data"
      },
      "last_interaction": {
       "type": "string",
       "description": "What was discussed last"
      },
      "previous_outcome": {
       "type": "string",
       "description": "What happened last time"
      },
      "buyer_description": {
       "type": "string",
       "description": "Text description of the buyer"
      },
      "interaction_count": {
       "type": "number",
       "description": "How many prior interactions"
      }
     }
    },
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "POST"
     ],
     "type": "string"
    },
    "bodyType": {
     "enum": [
      "json",
      "form-data",
      "text"
     ],
     "type": "string"
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "mode": "inferred",
  "timing": {
   "best_day": "Tuesday",
   "best_time": "10:00 AM",
   "reasoning": "Mid-morning minimizes decision fatigue for analytical types",
   "send_in_days": 1
  },
  "message": "Hi — I came across a case study that reminded me of the workflow challenge you mentioned. No pressure, just thought it might be useful as you're evaluating options.",
  "subject_line": "Quick thought on your automation workflow",
  "tone_strategy": "Value-add, no direct ask — matches this buyer's need for processing time",
  "channel_recommendation": "email — analytical buyers prefer written communication they can review at their pace"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/convrgent-ai-3310d0a5/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from convrgent.ai](https://www.zero.xyz/host/convrgent.ai/llms.txt)