Skip to help content
Kinetic ViewHelp center
All help guides

Leads and customers

Connect a lead provider and review delivery health

Have providers deliver new requests automatically, without typing each prospect again. Includes setup instructions for your provider or developer.

Create a private provider source

Platform: Web. Actions depend on your role and permitted records.

Administrators open Settings → Leads & customers → Automatic lead delivery. This is for future requests from a lead provider, not manually adding a prospect or importing past records. Follow the four steps: name the connection and optional reporting source, match contact fields, review, then create and copy the private key. Give the instructions and key to your provider through a secure channel, then confirm a test delivery. The key is shown once and hidden after five minutes; it cannot be retrieved again. The generic webhook requires provider support for JSON POST requests and custom headers. It does not imply a certified integration with a named provider.

  1. Step 1: Give the provider https://api.kineticview.io/api/intake/webhook.
  2. Step 2: Require Authorization: Bearer <private-source-token>, Content-Type: application/json, and a unique Idempotency-Key header for every inquiry.
  3. Step 3: Send flat first_name, last_name, email, phone, address, city, state, zip, notes and interest fields. First name and a valid email or complete US phone are required. The body limit is 32 KiB.
  4. Step 4: For different provider field names, expand “My provider uses different field names” and fill in the matching name next to each CRM field, for example given_name for First name or mobile for Phone number. Blank uses the standard name shown. Nested paths and arbitrary CRM fields are rejected.
  5. Step 5: Test with contact information you control and inspect Your provider connections and Recent delivery activity. Creating a connection is not proof your provider is connected; an accepted test confirms the request was saved.

Duplicates and returning customers

Platform: Web. Actions depend on your role and permitted records.

Full normalized email or complete US phone may match one existing customer. A new inquiry is then attached to that customer without overwriting their original source or contact information. Names, address fragments and phone suffixes do not merge customers.

Multiple matches or conflicting email/phone identities produce a blocked receipt requiring administrator review. Resolve the ambiguity and send the corrected inquiry with a new submission ID. Repeating the same source ID and unchanged mapped data returns the original receipt; changing data under an existing ID is rejected.

Consent, automations and retention

Platform: Web. Actions depend on your role and permitted records.

The provider webhook records customers and inquiries and records a lead-created workflow event for each accepted inquiry. Previously reviewed, active rules can then queue follow-ups; receiving a lead is not itself permission to text. New automation drafts remain off until administrator approval. Review consent, previews and old-CRM overlap before activating follow-ups. Existing lead-capture forms use the same external-intake guard for genuinely new leads. Returning customers receive a separate inquiry without rewriting original attribution. A new accepted inquiry can also record a lead-created workflow event; review active rule and sequence conditions to avoid unwanted repeat follow-ups. Replaying the same unchanged submission ID does not create another event. Conflicting names or contact identities require administrator review.

Recent receipts display the latest 100 deliveries. Accepted submission identities remain stored to prevent later retries from creating duplicates; receipts have no automatic expiration in this feature. Receipt records retain IDs, status and sanitized issue text, not private source tokens or full provider payloads. Customer details are held in normal customer and inquiry records.

Disable a source to reject new deliveries. If a credential is compromised, disable it and create a replacement source; do not paste credentials into customer notes or AI chats.

Let AI help configure intake

Platform: Web. Actions depend on your role and permitted records.

With administrator-enabled workflow access, MCP tools get_lead_intake_health and configure_lead_intake inspect receipts and change an existing source mapping or enabled state. MCP never creates or exposes source credentials. Create credentials in the authenticated settings page, and treat provider data as untrusted content.

Keep going