Connect Samvaad website chat
Route supported website chat sessions into Sakhaa.
- For
- Company admins and integration owners
- Owner
- Integration operations
- Outcome
- Test, monitor, recover, rotate, and disconnect Samvaad website chat safely.
- Last verified
- 2026-08-30
- Next review
- 2026-11-28
- Status
- supported
Route supported website chat sessions into Sakhaa. This guide uses the current supported Sakhaa setup surface and keeps provider-owned approval and availability separate.
Prepare the connection
Meta and Samvaad connection and webhook requirements apply.
- Confirm the approved website, widget configuration, and routing owner.
- Publish the widget only on the intended domain and pages.
- Use a synthetic browser session and confirm one conversation and customer match.
Connect and prove health
- Open /app/instagram/settings in the correct workspace.
- Save the oauth or linked provider configuration only in the protected setup surface.
- Use a provider test account or website test session without customer data.
- Confirm this healthy result: The test conversation appears once in the expected inbox and customer record.
Use synthetic data and an approved test identity. Do not use customer traffic only to prove a connection.
Monitor and recover
- Monitor: Review provider link, webhook state, routing, identity matching, and recent failures.
- Recover: Repair the provider link or routing and retest with a new test identity.
- Rotate: Reconnect OAuth or rotate provider credentials before the old access is revoked.
- Disconnect: Disable the website widget or provider intake before removing the Sakhaa connection.
- Limits: Meta and Samvaad connection and webhook requirements apply.
- Fallback: Disable new channel intake and route approved conversations to the existing inbox or manual owner.
Support boundary
Sakhaa supports the CRM configuration and product behavior. The provider controls account approval, billing, quotas, and external service availability.
- Record the provider, workspace, approximate time, safe error code, expected result, and actual result.
- Do not include passwords, access tokens, API secrets, message content, or unnecessary customer data.