Driven by a customer's lead-scoring rubric (A/B/C keyword tiers, bonuses,
deductions, compliance-risk words, lead fields):
- the judge returns score/signals/risk/risk_reason/reason; levels come
from configurable high_score (60) and ask_score (30), so medium and
high intent are asked once; 0.1/0.2-style strong_intent answers still
map to a score
- compliance risk (configurable risk_prompt) marks the lead "risk": no
contact request, no sales email, listed for review
- once contact details arrive, configurable lead_fields are extracted
from the whole conversation and shown at the top of the email (subject
now carries level and score) and on the page
- Page: score/level column, risk total and filter, lead fields and
per-judgment signals in the detail view
- bump to 0.3.0
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: multica-agent <github@multica.ai>
Record every purchase-intent judgment per conversation (result, reason,
the user's message, an AI reply excerpt) plus the contact request,
captured contact, email attempts and errors as a per-user timeline
(latest 100 events). Users who were judged but not asked now get an
"idle" row; asking still happens at most once.
Add a read-only Page (留资判断记录 / Lead judgments): totals, a filterable
and searchable conversation list, and a detail panel with the timeline
and the 30 most recent messages. i18n en_US / zh_Hans. Bump to 0.2.0.
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: multica-agent <github@multica.ai>
New misc plugin langbot-team/LeadCapture 0.1.0 (购买意向留资):
- after each AI reply (NormalMessageResponded) a configured LLM judges
strong purchase intent against a configurable prompt over the recent
conversation (monitoring.messages, read-only)
- on strong intent, a fixed contact-request text is appended to that
reply, once per bot+user
- user messages are then checked for contact details (patterns for CN
mobile/landline, email, WeChat; LLM extraction as fallback)
- on capture, the full conversation is emailed via Resend (configurable
API key, sender, recipients) with a .txt transcript attachment; failed
sends are retried on later replies, up to 3 attempts; an optional
thank-you is appended to the next reply
- every failure is logged and never breaks the conversation
Misc plugin CI now uses any plugin's own requirements-dev.txt.
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: multica-agent <github@multica.ai>