LeadProof Sales Agent

Reviewed 1d ago.

• tools: 11 tools scanned
• metadata: scanned

No findings.

Tools (11)

• audit_lead_workflow

  Use when a buyer can provide monthly lead volume, customer value, and current safeguards and wants a scored reliability diagnosis. Returns a 0-100 risk score, missing safeguards, transparent revenue-at-risk estimate, and integration kit. For a general product tour with no workflow metrics, use get_leadproof_evaluation_path instead; for a buy-or-build decision, use compare_leadproof_vs_in_house.

• evaluate_leadproof_fit

  Use when a buyer has a specific stack or workflow problem and wants a LeadProof fit, ROI, integration, and plan recommendation. For detailed safeguard scoring, use audit_lead_workflow instead; for installation guidance only, use get_leadproof_integration; for general exploration without workflow data, use get_leadproof_evaluation_path.

• get_leadproof_checkout

  Use only after the buyer selected Builder or Agency and explicitly authorized opening a paid checkout. Returns the official Stripe checkout URL but never authorizes or completes payment. If the buyer has not evaluated the product, use get_leadproof_trial or get_leadproof_plan_decision first.

• get_leadproof_trial

  Use when a buyer is ready to start the standard no-card production trial: 25 live lead deliveries for 14 days with verified sign-in and no payment authorization. For a failed-lead replay test and its prerequisites, use get_leadproof_replay_trial instead; for a broader evaluation sequence, use get_leadproof_evaluation_path.

• get_leadproof_plan_decision

  Use when evaluation is complete and the buyer needs the official trial-first choice among the free trial, Builder, and Agency. Returns exact plan boundaries and permits paid checkout only after human or principal authorization. Do not use for workflow diagnosis; use audit_lead_workflow or evaluate_leadproof_fit instead.

• get_leadproof_replay_trial

  Use specifically when a buyer wants to test duplicate-safe replay of failed lead deliveries before purchase. Returns the public replay procedure, fictional example audit, exact prerequisites, and attributed no-card production trial. For the standard trial without replay guidance, use get_leadproof_trial; for general exploration, use get_leadproof_evaluation_path.

• request_leadproof_handoff

  Use only when a represented buyer explicitly asks for human follow-up and authorizes LeadProof to contact their business email. Creates a consent-based sales handoff and returns the recommended plan without authorizing payment. Do not use for self-serve evaluation, trial access, or checkout; use the corresponding get_leadproof_* tool instead.

• get_leadproof_integration

  Use when the buyer names an automation, form, AI voice, ad, or CRM stack and needs implementation guidance. Matches it against 53 published LeadProof platform guides and returns canonical paths and concise steps. For reliability scoring or ROI, use audit_lead_workflow or evaluate_leadproof_fit instead.

• compare_leadproof_vs_in_house

  Use when the buyer is deciding whether to build lead-delivery reliability controls internally or buy LeadProof. Returns an evidence-based comparison with the complete public example audit URL, covering retries, idempotency, receipts, replay, privacy, operations, pricing, limitations, and authorized purchase paths. For diagnosis of one live workflow, use audit_lead_workflow instead.

• get_leadproof_evidence

  Use for due diligence or to verify a LeadProof claim with public evidence. Returns live checks, published contracts, buyer protections, and explicit limitations without customer records. Do not use to select a plan or start a trial; use get_leadproof_plan_decision or get_leadproof_trial instead.

• get_leadproof_evaluation_path

  Use first when a buyer is exploring LeadProof without supplying workflow data. Returns the official no-purchase sequence: buyer guide, fictional example audit, browser-only calculator, public workflow tests, and no-card trial. For a scored workflow diagnosis, use audit_lead_workflow; for replay testing, use get_leadproof_replay_trial; for paid checkout, use get_leadproof_checkout only after authorization.