Security and privacy
Security and privacy basics for LeadSnap AI.
The website handles business setup requests and demo submissions. Live SMS and phone features depend on provider credentials and verified webhook routes.
Public forms use nonces, honeypot spam protection, server-side sanitisation and escaped output.
Provider API keys are stored server-side in WordPress options and are not printed on public pages. Admin fields are masked where practical.
Telnyx and Twilio integrations include signature verification placeholders/routes that should be enabled before live traffic.
The site should collect only the lead and setup details needed to respond, qualify and deliver the requested service.
Privacy, terms, cookie and acceptable-use pages are UK-style placeholders and should be reviewed before paid launch.
The service must not be positioned as an emergency response system or substitute for professional/emergency services.
Product guidance
Continue through setup, operation and safeguards.
Follow the intended route from an unanswered call to a callback summary.
Setup routeCheck number-divert support, caller ID behaviour and provider requirements.
Frequently asked questionsReview existing-number, provider, pricing and service-limit answers.
Integration routesSee the phone, SMS, CRM, payment and calendar dependencies.
Text-back for UK tradesSee the customer-facing missed-call text-back workflow by trade.
Next step
Use the system with a careful setup path.
Configure provider credentials, email delivery and legal pages before live customer traffic.