INBOUND LEAD INBOX

No lead stays pending.

LeadPending brings every website request into one queue and turns a short instruction into an editable draft. The private beta is live for invited operators; email delivery follows verified provider setup.

Invited? Open workspace Read the API docs

Invite-only access
Draft manually or with AI
Telegram alerts available

Oldest pending

Maya Chen · Website redesign for three clinics

Draft only

INBOUND · 18 MIN WAITING

Can you help us launch before October? We need one system for three clinic websites.

YOUR INSTRUCTION

Say we can help. Ask for budget and who owns content approval.

REVIEWED DRAFT

Hi Maya — yes, this is the kind of multi-site launch we handle. What budget range are you working with, and who will approve the clinic content?

One route from form request to reviewed draft

The private-beta line is deliberately short. Intake, drafting, and Telegram alerts are live now; email delivery and inbound threading will join it after provider verification.

FORM REQUEST
Receive
Your server sends the form payload with a site API key. The lead appears as pending only after it is safely stored.
OPERATOR GUIDANCE
Review
Add a plain-language instruction, generate a draft, and edit the subject or body. Manual drafting always remains available.
LINKED TELEGRAM
Stay notified
Link your private Telegram chat to the exact LeadPending account and receive an alert when a new lead needs attention.

A communications desk, not a sales machine

Human control: AI prepares editable text only when you ask. Manual drafting always remains available.
Account-linked Telegram: A private bot chat is linked through a short-lived, single-use account connection.
Safe retries: Idempotency protects live lead intake now and will protect email sending when delivery is enabled.
Tenant isolation: Every site, lead, message, quota, and suppression stays scoped to its organization.

FUTURE FREE · 5 SITES · 20 REPLIES

The Free plan specification remains

The planned Free plan includes 5 active sites and 20 provider-accepted replies per calendar month UTC. During private beta, access is by invitation and email sending is not yet enabled.

Open invited workspace

POST /api/v1/leads

Replace a form integration, not your frontend

Keep local validation and bot protection. From your server route, send one authenticated POST request with a stable idempotency key.

curl https://api.leadpending.com/api/v1/leads \
  -H "Authorization: Bearer lp_live_••••" \
  -H "Idempotency-Key: form_018f..." \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Maya Chen",
    "email": "[email protected]",
    "subject": "Three clinic websites",
    "message": "Can you help us launch before October?"
  }'

Open complete API reference →

Before you connect a site

Is LeadPending a CRM or cold-email tool?

No. It is a focused inbox for people who already submitted a request through one of your websites.

Can AI send an email automatically?

No. AI creates an editable draft only when an operator asks. Email sending is off during the private beta and will still require an explicit human action after provider setup.

Is the 20-reply Free allowance active now?

Not yet. It remains the public Free plan specification; private-beta email delivery is disabled until the provider setup is complete.

Can I call the API directly from browser JavaScript?

No. A site key is a server secret. Call LeadPending from your server route after your own validation and Turnstile checks.

Already invited? Your lead desk is ready.

Open the workspace to connect a site, test intake, prepare a draft, and link Telegram. Public self-signup and email delivery are not open yet.

Invited? Open workspace →