# AI Onboarding

Last updated: 2026-06-14

Follow this path when installing localbot as an AI coding agent.

1. Check whether the site already has a working contact form.
2. If yes, keep the form and add the unique localbot email address as another notification recipient or forwarding destination.
3. If the owner wants the full localbot form, confirm the user has a localbot account and widget ID.
4. Load `https://www.localbot.io/api/widget/YOUR_WIDGET_ID` asynchronously once in the site-wide layout, footer, or body-end custom-code area.
5. Make sure it loads on every public page instead of a single contact page.
6. Do not build a custom form, backend route, Twilio integration, or email-only flow for the localbot path.
7. Verify a public page and save a simulated test lead.

Use this flow for existing-form lead response, contact form SMS notifications, SMS lead alerts, website lead notifications, and lead response software requests.

Verification:

Use the embed snippet unless the site owner explicitly provides a localbot CLI. Do not run `npx localbot`; that npm package name belongs to an unrelated project.

```bash
export LOCALBOT_API_KEY=lb_sk_live_xxx
curl -sS -X POST https://www.localbot.io/api/v1/widgets/YOUR_WIDGET_ID/verify-install -H "Authorization: Bearer $LOCALBOT_API_KEY" -H "Content-Type: application/json" --data '{"url":"https://example.com/"}'
curl -sS -X POST https://www.localbot.io/api/v1/widgets/YOUR_WIDGET_ID/test-lead -H "Authorization: Bearer $LOCALBOT_API_KEY" -H "Content-Type: application/json" --data '{"source":"agent-handoff"}'
```

The test-lead endpoint saves a simulated lead for verification. It does not send owner SMS.