Locint: the compliance layer
pay-per-call has been
waiting for.
Locint helps pay-per-call teams qualify inbound leads over SMS and keep versioned consent receipts. Text-message consent is recorded separately from phone-call consent for review by your team.
How Locint works
Four steps from inbound form to a buyer's ringing phone.
Lead lands
Google Lead Form / Facebook Lead Ads webhook posts the payload. We validate, dedupe, and assign a vertical.
AI texts the lead
Within 8 seconds, the SMS agent opens with a TCPA-compliant intro and starts qualifying.
Consent + intent capture
Every reply is logged. The agent stops if the lead opts out and tags the audit row.
Live patch + whisper
Only qualified leads are bridged to the buyer with a 6-second whisper brief.
The full stack
Compliance infrastructure, not another lead form.
Webhook ingestion
Drop-in endpoints for Google Lead Forms and Facebook Lead Ads. Signed payloads, schema validation, and instant dispatch.
AI SMS qualification
Vertical-aware LLM dialogues. The agent confirms intent, captures the budget, and surfaces the buyer match.
TCPA audit trail
Every consent capture is timestamped, hashed, and stored with the verbatim text. Export-ready for legal review.
Verified live patching
Only qualified, consented leads are bridged via Twilio with a whisper prompt that briefs the buyer in 6 seconds.
Pre-tuned vertical templates
Audit trail
When legal asks for receipts, you have receipts.
Keep the verbatim SMS disclosure, consumer reply, disclosure version, timestamp, and cryptographic hash together. Authorized integrations retrieve consent receipts for review. SMS confirmation does not grant phone-call consent.
- Text-message consent capture with verbatim copy stored
- Stop / opt-out keywords end the conversation instantly
- Per-buyer disclosure templates with replay-safe identifiers
- Immutable history — leads can never be silently re-engaged
{"lead_id": "lead_7s4b9k", "type": "sms_consent", "captured_at": "2026-06-11T14:02:18.471Z", "channel": "sms", "disclosure_version": "cs-v2", "consent_text": "This is CallSignal. Reply YES to confirm we can text you about your roofing request. Msg frequency varies, msg & data rates may apply. Reply STOP to opt out, HELP for help.", "user_reply": "YES", "hash": "sha256:9f17…c4e1"}Pricing
Pay for the leads that actually pick up the phone.
14-day free trial with your first 50 qualified calls on us. A small monthly base plus a per-call fee that drops as you grow. No charges for unqualified or unconsented leads — ever.
Publisher
For independent affiliates
- Up to 500 qualified calls/mo
- $1.50 per qualified call
- TCPA audit export
- Standard SMS templates
Questions about Locint
- What is Locint?
- Locint provides SMS qualification and consent records for pay-per-call workflows. Its CallSignal integration creates qualification sessions, records text-message confirmations, and sends status updates to connected systems.
- Does replying YES authorize phone calls?
- No. The SMS confirmation authorizes text messages only. Phone-call consent must be captured separately on the website. Consent records support review; using Locint does not by itself guarantee legal compliance.
- What does a consent receipt contain?
- A receipt records the disclosure text and version, the consumer’s reply, a timestamp, and a SHA-256 hash. Authorized integrations can retrieve the receipt for review without making consumer records public.
- Can AI agents connect to Locint?
- Yes. Locint’s MCP endpoint exposes tools to create, retrieve, and cancel qualification sessions and retrieve consent receipts. Requests require an API key. Read the MCP integration details.
- What is required before sending US business texts?
- The sending number needs the appropriate carrier registration and campaign approval. Connecting Twilio alone does not ensure delivery. Message frequency varies; message and data rates may apply. Recipients can reply STOP to opt out or HELP for help.
