META LEADS + WHATSAPP

Connect your Meta enquiries
to the next conversation.

Bring supported Facebook and Instagram lead enquiries into an organised workflow, then help your team follow up on WhatsApp with the right context.

Start with WhatsOS See how it works

Lead capture Conversation context Team follow-up

PRODUCT PREVIEW

Illustrative lead-to-follow-up workflow

1 Meta form submission

Meta lead form

Sample campaign: Home services enquiry

Name: Ananya
Service: Terrace waterproofing
Location: Kochi
Preferred callback: Tomorrow after 11 AM

Fictional form answers · no real phone number

2 Organised lead

Lead in WhatsOS

Source: Meta Instant Form
Requirement: Terrace waterproofing
Location: Kochi
Owner: Priya · example staff assignment
Status: New

Source data is illustrative; ownership is a staff update.

3 Follow-up prepared

Example template preview

Hi Ananya, thank you for your waterproofing enquiry. Would you like to continue discussing your requirement here?

Preview · Not sent

Sending depends on the configured messaging permissions, template and account setup.

Meta form capture requires the enabled Meta Lead Capture feature, a configured ingestion connection and available usage.

KNOW WHERE THE ENQUIRY STARTS

Two entry points. Different starting points for follow-up.

Meta Instant Forms

Customers share details in a form on Facebook or Instagram. Your configured integration captures the submission for staff to review.

Form submission

Lead record

WhatsApp outreach needs the appropriate messaging setup and permission.

Click-to-WhatsApp ads

Customers open WhatsApp from your ad and send a message. Your team or configured AI can continue the conversation.

Customer sends a message

WhatsApp conversation

A click alone is not a message. Ad referral attribution is not verified in this implementation.

What each entry point provides
Starting point	Meta Instant Form	Click-to-WhatsApp
Where the customer responds	In a Facebook or Instagram form	In WhatsApp
What starts the workflow	A supported form submission reaches the integration	The customer sends a WhatsApp message
What information is available	Submitted answers and supplied source metadata	Message and contact context; ad attribution is not guaranteed
How follow-up begins	Review permission and the supported template/send setup	Reply to the customer’s message under the applicable messaging rules

LESS COPYING. MORE CONTEXT.

Give every enquiry a clearer next step.

Reduce manual copying

Bring supported lead fields into the configured workspace.

Keep the original context

See the customer’s requirement and available source information.

Organise follow-up

Use supported ownership, status and notes to help staff plan the next step.

THE FORM-TO-TEAM JOURNEY

From submission to team follow-up.

Customer submits an enquiry

A supported Meta form receives the customer’s details.

Integration captures the lead

Your configured connection supplies the available supported fields.

Lead reaches the workspace

Staff review the requirement and supplied source information.

Your team follows up

Check permission and messaging setup before preparing outreach.

Messaging requirements metPrepare the supported follow-up

Setup or permission missingStaff review / complete setup

Integration details

WhatsOS accepts supported lead fields for an active configured form, records the lead event and checks account usage. The current follow-up option records a queued action, not a completed send. Confirm your authorised ingestion and send workflows with the team; the public examples do not submit data.

USE WHAT THE CUSTOMER ALREADY TOLD YOU

Keep the details your customer already shared.

Map submitted information to the supported lead fields, and keep additional answers in their original context.

Separate customer answers from source metadata and staff updates. Missing information stays “Not provided”—including permission when it has not been established.

Available source metadataConfigured form and Page · supplied campaign, ad set and ad details

This is an example mapping, not a custom mapping editor. Source completeness depends on what the integration supplies.

Example field mappingMeta form → WhatsOS context

Full nameContact name

PhoneContact number

Service requiredRequirement

CityLocation

Preferred callbackOriginal answer / payload

Callback preference is extra form context, not a dedicated saved lead field. No real phone number appears in this demo.

MAKE THE FIRST MESSAGE RELEVANT

Start the next conversation with context.

Respond to the enquiry the customer actually submitted, with a relevant message and one clear next-step question.

ORIGINAL ENQUIRY · SAMPLE DATA

Ananya

Home services enquiry

Terrace waterproofing
Kochi
Tomorrow after 11 AM

The callback time is a preference, not a booking. Messaging permission is a separate check.

Example template preview

Hi Ananya, thank you for your waterproofing enquiry. Would you like to continue discussing your requirement here?

Preview · Not sent

Example: requirements checked

An authorised teammate can prepare the supported follow-up after checking permission, the approved template and the connected number.

Form submission and WhatsApp messaging are separate steps. Check recipient permission and use an approved template when required. Available follow-up options depend on your account setup. WhatsApp messaging policy

A CLEARER TEAM REVIEW

Give your team one place to review the enquiry.

An illustrative WhatsOS lead review, using supported lead fields and example team notes. Select a customer to see the context.

WhatsOS lead workspaceSAMPLE DATA · SELECT A RECORD

Requirement	Source	Owner	Status	Next action
Terrace waterproofing	Meta Instant Form	Priya	New	Review and prepare follow-up
Two-bedroom apartment	Meta Instant Form	Arjun	Contacted	Clarify property preferences
Interior consultation	WhatsApp chat	Unassigned	New	Assign a teammate

SELECTED EXAMPLE

Ananya · Terrace waterproofing

New

Customer-provided details

Name: Ananya
Location: Kochi
Requirement: Terrace waterproofing
Callback preference: Tomorrow after 11 AM
Budget: Not provided

Sample source details

Source: Meta Instant Form
Form: Service enquiry form
Campaign: Home services enquiry

Campaign and form details are example context, not guaranteed attribution on every record.

Conversation & team context

No WhatsApp conversation started by this form submission.

Example staff note

Review the submitted service and location. Confirm permission and the correct template before outreach.

SUGGESTED NEXT ACTIONReview and prepare follow-up

This combined preview illustrates the review process; it is not a claim that the current dashboard displays every original form answer together. Suggested actions are example notes, not scheduled tasks.

Explore lead capture Explore the shared inbox See the AI chatbot

How does LeadSaza fit in?

WhatsOS keeps lead and event records. Its LeadSaza connection supports configured conversation/lead transfers, but automatic sync of every Meta submission has not been verified. Account mapping, credentials and enabled sync are required. Check the relevant workflow and sync logs; neither shared login nor separate product access is implied.

SET UP THE CONNECTION, THEN TEST IT

Connect your lead sources in a clear sequence.

Confirm Meta asset access

Work with the team to confirm access to the Page, forms and supported lead ingestion connection.

Register the supported forms

Configure the form ID and optional Page ID. A self-service form picker is not currently available.

Review fields and follow-up

Check the supplied fields, enabled feature, permissions and any approved template/send workflow.

Test the complete journey

Use an authorised test enquiry to verify capture and the permitted follow-up separately.

Before you begin

Appropriate access to your Meta assets
Enabled Meta Lead Capture feature and available usage
A configured, active form ingestion connection
Eligible WhatsApp setup, recipient permission and approved templates where required

REAL QUESTIONS. USEFUL NEXT STEPS.

Built around real enquiry workflows.

Home services

Capture service and location details, then arrange the next discussion.

Real estate

Collect property preferences and connect the enquiry with an advisor.

Education

Capture course interest and help an admissions team follow up.

Business services

Understand the requirement and organise a sales conversation.

KEEP CAPTURE AND MESSAGING DISTINCT

See what needs attention.

Review capture records, account setup and messaging results in the relevant workspace views.

WhatsOS records lead events and supports WhatsApp message statuses when events arrive. Review unassigned leads and usage separately; capturing a lead does not establish delivery or a sale.

Review current plans

The current Meta dashboard is not a complete monitoring console. The panel shows example checkpoints, not a live unified status screen.

Example review checkpointsSAMPLE DATA

Lead recordCaptured in this example

OwnerPriya · staff assignment

WhatsApp follow-upPreview only · not sent

Messaging permissionStaff to check

Captured ≠ sent. Sent ≠ delivered.
Delivery and read events do not mean converted.

THE DETAILS THAT MATTER

Your integration questions, answered.

Clear answers to help you set up the connection and choose the right next step.

Talk to sales

How are Meta Instant Forms different from Click-to-WhatsApp ads?

An Instant Form collects answers on Facebook or Instagram. The configured integration receives those details as a lead. A Click-to-WhatsApp ad opens WhatsApp; the customer must send a message for the conversation to begin. The two entry points do not provide identical fields or attribution.

Does submitting a form start a WhatsApp conversation?

No. A form submission and a WhatsApp conversation are separate steps. A phone number in a form is not, on its own, permission to send WhatsApp outreach. Review recipient permission and your messaging setup before following up.

Can WhatsOS send a follow-up automatically?

The current Meta form integration can record a queued follow-up when its option is enabled and a phone number is supplied. That queue entry is not a send or delivery confirmation. Automatic sending from that queue has not been verified. Use a supported, configured send workflow and the required permission and template checks.

Which lead fields can be captured?

The capture service accepts name, phone, email, city and requirement, plus supplied campaign, ad set and ad identifiers or names. The integration must provide these supported fields. Extra form answers can remain in the submitted payload; a callback preference is not a dedicated mapped lead field in the verified implementation.

Can I connect multiple Pages or forms?

The configuration supports multiple form records, each with its own form ID and optional Page ID. Access depends on the relevant Meta assets, enabled Meta Lead Capture feature and usage limits. A self-service Page/form discovery wizard is not currently shown in the WhatsOS Meta leads screen; confirm connection support with the team.

Can my team reply manually?

Yes. Once there is a WhatsApp conversation, authorised staff can reply through the shared inbox, assign ownership, add internal notes and pause AI where applicable. For form-only leads, a supported outreach workflow and the messaging requirements still need to be checked.

Where are the leads stored?

The capture service creates or updates a lead record in WhatsOS and saves a Meta lead event with supplied source details. Extra original form data can remain in that event payload. WhatsOS also supports LeadSaza identity and ownership mappings, but those mappings alone do not establish that the lead has synced to another product.

Does this integration connect with LeadSaza?

WhatsOS has a configured LeadSaza integration for supported conversation and lead transfers. It requires account mapping, credentials and enabled sync. Automatic transfer of every Meta form submission was not verified, so check the relevant workflow and sync logs. Shared login and separate product access are not implied.

Can I see the source campaign?

Meta lead events store campaign, ad set and ad details when the integration supplies them; the lead record can hold campaign context. Missing values remain unknown. Automatic Click-to-WhatsApp ad referral attribution was not verified in this implementation, so the page does not promise it for every WhatsApp chat.

What happens if a connection stops working?

An inactive or unconnected form is rejected by the capture service. Account and usage checks can also block capture. Have your team inspect the connection and available event records. Review a real send result separately from capture; automatic recovery, guaranteed retries and a unified delivery dashboard are not promised.

Are WhatsApp messaging charges included?

WhatsOS plan and enabled-feature limits are separate from Meta messaging charges. Charges depend on the message and current Meta pricing. Review the current WhatsOS pricing and official WhatsApp Business Platform pricing; this page does not promise that all messages, campaigns or integrations are included.

Current requirements: WhatsApp messaging policy · Meta platform pricing

KEEP THE CONTEXT. MAKE THE NEXT STEP COUNT.

Give your next Meta enquiry
a clear path forward.

Capture the details, keep the context, and help your team start the right conversation.

Start with WhatsOS Talk to sales