# Connect the channels. Keep the customer context.

> A lead source, a messaging inbox and an autonomous workflow are different things. Use this directory to understand what can be configured and what is still part of the product direction.

## Supported intake is not instant activation

Thumbtack, Google Local Services Ads, Meta Lead Ads, Angi and Yelp have intake paths in the current application. Activating them depends on credentials, permissions, provider access and configuration. A logo is not proof that your account is connected or that every provider feature is available.

## Calls and SMS

The current product includes Twilio-based calling and messaging workflows. Phone setup, messaging eligibility and usage charges apply. Review replies and routing with a test request before using automation with customers.

## Social messages and email

Instagram direct messages, Facebook Messenger and email are not self-serve channels today. The product can receive them for the operator's own business, and customer workspaces are on the roadmap. Instagram and Facebook lead forms are supported through Meta Lead Ads. Each channel page states its exact status; do not buy a subscription on the assumption that these inboxes are included.

## What happens after a request arrives

The current workflow brings a request into a lead record so the team can continue the conversation and manage work. The longer-term Neuro model connects that context to tasks, scheduling, follow-up and business outcomes, with approvals and exceptions.

## Questions to ask before connecting

Is this a lead form or a two-way messaging integration? Can the provider grant access to your account? Which messages are imported? Who reviews AI replies? What usage costs apply? Test each answer against an actual supported connection before relying on it.

Source: https://neurlead.com/integrations/
