Meta Lead Ads Bringing Poor-Quality Enquiries? Start Here

A cheap enquiry isn't a win if the person was never a fit for your business. But an unanswered phone call isn't proof of a bad lead either.

That's where I'd start. Before changing audiences, rebuilding the campaign or giving up on Facebook altogether, find out what "poor quality" actually means in your account. You could be dealing with unsuitable prospects, invalid contact details, weak expectations or enquiries that haven't been properly assessed. Those are different problems. They don't deserve the same fix.

My recommendation is to judge the campaign on cost per qualified enquiry, alongside what those enquiries eventually become. Keep cost per lead in the report. Just don't let it make the decision on its own.

This guide is for businesses already receiving enquiries through Meta instant forms on Facebook or Instagram. If people aren't enquiring at all, start with the broader guide to Meta Ads that aren't converting.

Find out what is wrong with the enquiries

"The leads are rubbish" might be an honest reaction, but it isn't a useful diagnosis.

Take a recent group of enquiries that has had enough time to progress through your normal sales process. Look at what actually happened to each one. Don't compare last month's completed sales with yesterday's unanswered calls.

Record two things separately: whether the person fits your service, and what happened when your team tried to contact them. A prospect can be suitable and unreachable. Someone can answer immediately and still be entirely wrong for the offer.

For fit, use clear outcomes such as qualified, unsuitable, or not yet assessed. Record why someone is unsuitable: wrong service, outside your operating area, or a requirement you genuinely cannot meet. "Didn't buy immediately" isn't automatically a qualification failure.

For contact, distinguish not attempted, attempted but unreached, reached, and confirmed invalid contact information. Keep duplicates separate. Flag suspected spam for investigation rather than treating it as confirmed because somebody didn't answer.

That gives you something you can act on. If most enquiries are unsuitable for a specific reason, review the offer and qualification. If most haven't been assessed, fix the handover before declaring the audience wrong. If contact details are genuinely invalid, investigate the form and available verification controls.

You don't need an elaborate dashboard to begin. You need consistent records. A spreadsheet with honest answers is more useful than a beautiful report full of guesses.

Decide what "qualified" means before judging the campaign

A qualified enquiry should meet agreed business criteria, not whichever definition makes this week's report look better.

For a hypothetical installation business, that could mean the customer wants a service the business actually provides, is in its operating area and has a suitable project. For an appointment-based service, it might mean a relevant need and a realistic next step towards booking.

Use the criteria that matter to your business. Don't copy another company's definition, or quietly change yours halfway through a test. Keep unknown cases visible. An enquiry you haven't assessed is not proven unsuitable.

Check whether the offer explains what happens next

Read the client-supplied ad and the form together, as someone who has never heard of your business.

Can they tell what they are requesting? Is it a quotation, a consultation, an information pack or a booking? Who is the service for? What happens after they submit?

If the ad offers free information and the form leads straight to a sales call, don't act surprised when the prospect isn't ready for that conversation. The campaign may be collecting exactly the interest you asked for. The expectation is the part that needs work.

For example, a hypothetical service business could make the request clearer by stating the specific service, its operating area and that the enquiry is a request for a quotation. Where an accurate starting price or minimum project requirement matters to fit, consider making it visible. Don't manufacture a price just to put a filter on the form.

I would rather help the right person understand the offer than make it sound vaguely attractive to everyone. Some people choosing not to enquire is perfectly acceptable when they genuinely aren't a fit.

The client is responsible for creating all final ad copy, images and videos. Nexus can advise on the testing direction and manage the campaigns using client-supplied assets. Nexus does not produce final ad creatives or respond to ad comments and messages.

Make the form useful, not simply longer

Meta instant forms let people submit information without leaving Facebook or Instagram. Contact fields may be prefilled using information already provided to Meta, and people can edit those details. That makes the process convenient. It doesn't establish whether the person is suitable for your service.

The aim isn't to make submitting an enquiry unpleasant. It's to make the request clear and collect what you genuinely need to assess it.

Start with questions that change the next step. "Which service are you interested in?" and "When are you looking to get started?" can be useful. A question that nobody uses after submission is usually just extra work for the prospect.

If you need to prevent clearly unsuitable submissions, check whether conditional logic is appropriate in your Ads Manager form setup. Meta documents routing that can close the form for particular answers without passing that person's information to the advertiser. That's different from collecting an answer and assuming it automatically filters someone out.

Keep the rules fair and relevant. Don't reject somebody simply because they are researching rather than ready to buy today, unless the specific offer genuinely requires an immediate buying decision. Some enquiries belong in a longer sales process.

Meta restricts the questions you can ask. It also prohibits custom questions that duplicate its prefill fields, so don't try to get around autofill by asking for the same email or phone number again as a custom question. Check the current policy before changing the form, especially around sensitive information.

Higher intent is a test, not a qualification certificate

Meta's Higher intent form type adds follow-up context and a review screen before submission. That is worth testing when you want people to confirm what they are requesting.

It does not verify that somebody can afford your service, intends to buy or will answer your call. It also changes delivery: Meta's current guidance limits Higher intent to Facebook Feed and Instagram feed on mobile, rather than desktop. Account for that when interpreting a comparison.

Test it against meaningful outcomes, not just whether the raw lead price went up. If volume falls but the cost per qualified enquiry improves, that may be a worthwhile trade. If it doesn't, an extra review screen hasn't fixed the problem.

Where available in your setup, phone verification addresses a different issue. Meta documents verification using a code sent through WhatsApp or SMS to help filter fake leads and obtain a current mobile number. It has eligibility, device and phone-number restrictions, including no landlines. A verified number still doesn't prove buying intent or guarantee a later response.

Use the control that addresses your diagnosis. Don't switch on every available obstacle and call it a strategy.

Check the handover without blaming the sales team

Submit a test enquiry and follow it through your actual process.

Does it arrive where it should? Are the answers attached? Does somebody know it needs attention? Does your team know which offer the person responded to? Is there a clear expectation about the contact method and timing?

Meta supports CRM integrations that retrieve new enquiries automatically, alongside manual downloads. The important question is whether your chosen process delivers the enquiry and its context reliably.

Don't leave a form submission sitting unseen, then label it low intent days later. Equally, don't assume faster contact will rescue an unsuitable offer or a genuinely invalid number.

Have the client team record first-contact timing and outcomes. Use that record to find handover problems and improve the process. Avoid quoting a universal response deadline as if every business, prospect and sales cycle behaves identically. Follow up in line with what the person requested and the permissions you have.

Customer follow-up remains the client's responsibility. Campaign reporting can help identify a gap; it doesn't mean Nexus takes over the client's calls, comments or messages.

Make sure Meta is receiving the outcome you care about

A lead arriving in your CRM and a qualified outcome reaching Meta are two different things.

The first is lead delivery. The second is feedback that can support optimisation towards a more meaningful result. Connecting one doesn't prove the other is working.

Meta's current guidance distinguishes a performance goal that seeks people likely to share their contact details from "Maximize number of qualified leads", which seeks people more likely to convert after sharing them. For the CRM route, check the current Conversions API requirements and supported account options before changing the goal. This is not a setting I'd tell an owner to switch on blindly.

Conversions API for CRM can send downstream lead outcomes back to Meta. A working website Pixel or website Conversions API connection isn't proof that this CRM feedback route is configured correctly.

Define a meaningful outcome first. Then check that your CRM records it consistently, the chosen integration sends it correctly, and Meta recognises the events and the connection. The event you choose should represent real progress, not simply a status your team uses inconsistently.

If one staff member marks every conversation as qualified and another reserves that status for a confirmed opportunity, fix the definition before feeding the data back. Sending inconsistent labels faster does not make them better.

This involves customer data, so use the supported integration and appropriate permissions and disclosures. Don't copy customer contact details or qualification answers into GA4 events as a shortcut. Advertising-platform matching and website analytics are different data flows.

A better signal gives the campaign something more relevant to optimise towards. It is not a guarantee of better performance, and it doesn't remove the need to check the offer, assessment and sales process.

Why a $30 enquiry can be better than a $15 enquiry

Here is a hypothetical example in Australian dollars. It is not a Nexus client result, industry benchmark or prediction.

Campaign A spends $1,500 and produces 100 unique enquiries. Ten meet the agreed qualification criteria, and two become sales within the comparison window. Its cost per enquiry is $15, its cost per qualified enquiry is $150, and its media spend per sale is $750.

Campaign B also spends $1,500. It produces 50 unique enquiries, with 15 qualified and three becoming sales within the same window. Its cost per enquiry is $30, its cost per qualified enquiry is $100, and its media spend per sale is $500.

Judge that comparison only by cost per lead and you'd favour A. Look further down the process and B has the stronger result on those measures. The supposedly expensive enquiries cost less per qualified opportunity and less per sale.

The calculations are simple:

• Cost per enquiry = media spend divided by unique enquiries.
• Cost per qualified enquiry = media spend divided by qualified enquiries.
• Media spend per sale = media spend divided by sales attributed on your agreed basis.

Those aren't full business-profit calculations. They exclude management fees, sales costs, delivery costs, refunds and margin. The example doesn't prove that a particular form change caused the difference either.

In a real account, compare equivalent periods, offers and qualification rules. Give each group enough time for your normal sales cycle. Reconcile duplicates and use the same attribution basis. If outcomes are still pending or the numbers are small, say so rather than pretending the winner is settled.

Where your campaign has no qualified enquiries, don't turn the calculation into a misleading $0 result. Record that no qualified outcome has been observed yet and investigate why.

What I would do next

I'd leave the campaign structure alone long enough to diagnose the problem, unless there is an obvious delivery, spending or tracking error that needs immediate action.

First, agree what a qualified enquiry means. Review the recent enquiries against that definition and keep contact status separate. Then check whether the supplied offer, form and follow-up expectations explain what the person is asking for.

Choose the first test from that evidence. It might be clearer client-supplied messaging, a relevant qualification question, Higher intent, an available verification control, a handover repair or a properly configured qualified-outcome signal. Document the change and the outcome you're judging. Where practical, change one major variable at a time.

If an instant form can't explain the offer or collect the information needed for a sensible next step, a website enquiry flow may be worth testing. It isn't automatically better. Judge it on comparable qualified outcomes, and don't replace a quick form with a slow page and hope the extra inconvenience counts as intent.

The point is to stop asking, "How do we get the cheapest leads?" and start asking, "Which enquiries are helping the business, and what needs to change to get more of those?"

If you want help reviewing the campaign and the outcome data together, talk to Nexus about an ads consultancy session. Bring the actual enquiry outcomes, not just the Ads Manager screenshot. That's what makes the conversation useful.

Platform guidance checked on 7 November 2026 (Brisbane time). Form features, restrictions and available performance goals can change; verify the options in your own account before implementing them.