Jadav AI Lead Briefs
| 开发者 | jadavsanjay |
|---|---|
| 更新时间 | 2026年10月1日 12:30 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
- Fluent Forms and Contact Form 7 capture for explicitly selected form IDs.
- Summary, High/Medium/Low/Needs review priority, and a short reason.
- Supporting quotes checked against the captured text. Without a matching quote, priority becomes Needs review. A matching quote does not guarantee a correct priority.
- Missing information and up to three suggested follow-up questions.
- Human priority override, keeping the original AI brief for comparison.
- Field allowlist and best-effort redaction before local storage.
- Configurable English, Hindi, Gujarati, or other output language.
- Manual analysis, daily attempt cap, retention cleanup, and permanent deletion. This is a separate companion plugin, not a form builder. It does not send replies, reject submissions, alter form notifications, or make automatic sales decisions. AI suggestions may be inaccurate; a person should review them. No external request runs during form submission.
安装:
- Upload the jadav-ai-lead-briefs folder to wp-content/plugins, or install the ZIP in Plugins > Add New > Upload Plugin.
- Activate the plugin. For multisite, activate separately on each site; network activation is not supported.
- Open AI Lead Briefs > Settings. Enter Fluent Forms and/or Contact Form 7 numeric form IDs.
- Match allowed field names to the actual input names in your form builder, then enable local capture. Blank form ID lists disable that integration.
- Configure a compatible AI provider in WordPress Settings > Connectors. Enter business context and output language in this plugin, then enable AI sharing.
- Submit a selected form, preview its captured text in Lead inbox, then click Analyze with AI.
- Review the brief and save your own priority. No reply is sent automatically.
常见问题:
What is different about this workflow?
It combines payload preview, matching source quotes, missing-detail questions, and a separate human priority. It focuses on reviewable enquiry briefs rather than automatically scoring and routing every submission. These are design choices, not a claim of exclusivity across the plugin directory.
Which form fields are supported?
Up to 15 explicitly named scalar fields, with at most 2,000 characters each. Arrays, nested fields, and uploads are skipped. Fields whose names suggest names, email addresses, phones, addresses, passwords, files, tokens, or secrets are excluded even when allowlisted. Field names must match exactly after lowercase normalization. Configure normal lowercase input names in your form builder.
Is the captured text anonymous?
No. Common email addresses, URLs, and phone-like numbers are redacted before storage. Names or other identifying information in free text may remain. Some long budget numbers may also be redacted. Review the preview before analysis and delete records that should not be shared. Keep sensitive fields out of the allowlist and update your site's privacy notice as appropriate.
Where is data stored?
Captured text, source form/entry references, AI results, priority, and reviewer user ID/time are stored as private WordPress records. Access is restricted to users with manage_options. Original form plugin entries are unaffected. Provider credentials are managed by WordPress and the selected connector, not this plugin.
What happens if AI fails or no provider is configured?
The lead remains in the inbox and can be reviewed manually. Connection, quota, invalid response and incomplete response errors do not assign an AI priority. There is no automatic retry or keyword score presented as AI output.
How does retention work?
The default is 30 days from capture. WordPress cron removes up to 100 expired records per hourly run, so low-traffic sites or a backlog can delay deletion. Use reliable WordPress cron scheduling for time-sensitive cleanup. Deactivation preserves records and stops cleanup. Uninstalling deletes this plugin's records and settings across sites, including legacy plugin-owned API keys. Core connector settings are not deleted; legacy constants in wp-config.php must be removed manually.
更新日志:
- Migrate generation to the WordPress AI Client; remove direct provider requests and plugin-owned credential/model configuration.
- Require WordPress 7.0+, reset sharing consent on upgrade, and preserve existing leads and briefs.
- Initial release with selected-form capture, structured AI briefs, quote checks, human review, request limits, and retention controls.