AI Lead Decision Layer

Kanshi is a bouncer for your CRM

Kanshi sits between website forms and business systems, acting as a real-time traffic controller for leads before they enter your CRM, inbox, database, or redirect flow.

Between forms and business systems

Kanshi intercepts form submissions before processing. The AI decision engine evaluates the submission and returns allow, reject, or flag before downstream systems act.

  • Website forms
  • CRM systems
  • Email notifications
  • Database storage

Why low-quality leads cost money

Fake and low-intent submissions trigger sales calls, CRM records, support work, reports, and automation even when they never had business value.

  • Wasted follow-up
  • Polluted CRM
  • Bad pipeline data
  • Operational noise

Real-time lead gatekeeping

Kanshi makes a decision while the submission is still at the gate, so only approved leads proceed into your workflow.

  • Allow valid leads
  • Reject fake leads
  • Flag uncertain submissions
Traditional vs Kanshi

Security tools and lead decisioning solve different problems

Kanshi is a layer after CAPTCHA, WAF, IP blocking, and rate limiting. It decides whether the submission should enter the business pipeline.

Traditional solution
What it checks
What Kanshi adds
CAPTCHA and Turnstile
Verify interaction signals before submission.
Decides whether the submitted lead should enter business systems.
Regex and keyword filters
Catch exact patterns but miss rewritten or AI-generated abuse.
Understands meaning, intent, and lead quality.
Blacklists and IP blocking
Block known sources while new senders keep appearing.
Evaluates each form submission before CRM, email, or database entry.
Manual moderation
Works, but becomes slow and expensive as lead volume grows.
Allows valid leads, rejects fake leads, and keeps uncertain submissions reviewable.
Rule engines and WAFs
Protect infrastructure and known rules.
Adds semantic, business-aware lead decisioning after form submission.
Decision Engine

Allow, reject, or flag with explainable confidence

Every submission can return a decision, confidence score, category, and reason.

Incoming submission

"I need a quote today. Please call me about your service package."

Confidence
92%
Risk
Low
Category
Valid lead

Allow

Lead intent fits the business and can enter the workflow.

Reject

Submission is fake, low quality, irrelevant, or not worth routing.

Flag

Submission may be real but should be reviewed before entry.

Developer API

Gatekeep leads from any form workflow

Use Kanshi in contact forms, quote requests, bookings, support requests, registrations, and custom lead pipelines.

Forum post

I need help restoring my account access after changing my email.

Product review

The replacement part arrived on time and fit the older model correctly.

Support ticket

Our billing page shows two failed invoices after updating the card.

Marketplace listing

Lightly used commercial mixer with serial number and pickup details.

POST /api/validate
{
  "type": "contact_form",
  "site_context": "Local service business accepting quote requests",
  "content": "I need a quote today. Please call me about your service package."
}

{
  "decision": "allow",
  "confidence": 0.91,
  "category": "valid_lead",
  "reason": "The message matches the business, page intent, and expected buyer request."
}
How It Works

From form submission to business decision

Kanshi turns raw form submissions into lead decisions your workflow can act on.

1

User submits a form

2

Kanshi understands business context

3

AI analyzes lead intent

4

Decision engine scores confidence

5

Allow, reject, or send to review

6

Only valid leads proceed