What to set up first
Most teams get value fastest by proving one complete path: one lead source, one instant alert channel, one owner or routing rule, and one destination such as a CRM or spreadsheet.
Do not connect every vendor on day one. Start with the source that already produces real leads, prove the response path, then add more sources after the first test is clean.
- Pick your first source: Google Ads lead form, Meta Lead Ads, a website form, or an existing Zapier/Make automation.
- Pick your fastest alert channel: email, Slack, Teams, Telegram, SMS, WhatsApp, voice fallback, or browser push.
- Pick your system of record: HubSpot, Salesforce, Pipedrive, GoHighLevel, Zoho, Google Sheets, Excel Online, Zapier, or Make.
- Send one controlled test lead and confirm it appears in `/app`, not only in the source platform.
- Confirm the team member who owns the lead can claim it and see the SLA timing.
Use case 1: Google Ads lead form to instant follow-up
Use this when paid search or Performance Max is already collecting leads inside Google Ads. Google supports lead form assets that can send leads to a CRM through a webhook path, which makes it a strong first integration for speed-to-lead workflows.
InstaChime receives the lead, normalizes contact fields, starts the SLA clock, alerts the team, and can forward the lead to your CRM or spreadsheet.
- Open your Google Ads lead form asset.
- Add the InstaChime capture endpoint as the webhook URL.
- Use your InstaChime shared secret as the webhook key.
- Send Google test data and confirm a 200 response.
- Open `/app` and confirm the lead appears with contact fields and source context.
Use case 2: Meta Lead Ads to CRM and alerts
Use this when Facebook or Instagram instant forms are generating leads. Meta lead retrieval usually uses a Page/app webhook or an approved bridge that receives a lead ID, retrieves the full fields, and posts the normalized lead to InstaChime.
This flow is useful when you want sales to call or message quickly instead of waiting for manual CSV downloads.
- Confirm your Meta Page, ad account, and instant form are owned by the correct Business account.
- Connect a Meta app or approved bridge with lead retrieval access.
- Map name, email, phone, form ID, campaign, ad ID, and leadgen ID.
- Post the normalized payload to InstaChime with the shared-secret header.
- Confirm the lead, alert, and CRM delivery history all show success.
Use case 3: Website form to lead dashboard
Use this when the highest-intent leads come from your own landing page, contact form, calculator, quote form, or booking page.
Send the form through your server, CMS plugin, or automation bridge so your shared secret stays private. The browser should not contain the secret.
- Create a server-side form handler or use a trusted form platform webhook.
- Send JSON to the InstaChime capture endpoint with name, email, phone, message, UTM fields, and consent fields.
- Keep the shared secret on the server or bridge only.
- Return a normal thank-you message to the visitor after InstaChime accepts the lead.
- Send one duplicate test and confirm the dashboard does not create messy duplicate work.
Use case 4: Send every lead to a spreadsheet
Use this when operations, agencies, or owners still need a simple lead log outside the CRM. Google Sheets and Excel Online are common because they are easy to review, filter, and share.
A spreadsheet should not replace fast follow-up, but it is useful for reconciliation, client reporting, and backup visibility.
- Create a sheet or workbook table with stable column names.
- Add columns for lead ID, created time, source, campaign, name, email, phone, status, score, and owner.
- Connect through Zapier, Make, Google Sheets API, Microsoft Graph, or your own webhook bridge.
- Send a sample lead and confirm the row appears once with the expected values.
- Keep the lead ID column so later exports can be matched back to InstaChime.
Use case 5: Route to the CRM your team already uses
Use this when HubSpot, Salesforce, Pipedrive, GoHighLevel, or Zoho is the system where sales works after the first response.
Keep InstaChime focused on instant capture, claim, SLA, routing, and retry visibility. Send the CRM a clean lead.created payload after the lead is accepted.
- Choose insert or upsert behavior before launch.
- Map mandatory CRM fields before turning on live traffic.
- Store OAuth tokens or private app credentials only in the destination bridge or backend, never in public docs.
- Send one successful lead and one controlled validation-error test.
- Confirm the CRM record ID or error response appears in `/integrations`.
Finish with proof before live traffic
Before you rely on the workflow, prove the full path from source submission to dashboard, alert, destination, and retry visibility.
- Save the source test ID or screenshot.
- Save the InstaChime lead ID.
- Confirm at least one alert was delivered to the right recipient.
- Confirm the CRM record, sheet row, Zap run, Make run, or webhook delivery returned success.
- Open the detailed launch checklist and complete it for every production source.