Skip to content

Why Timi doesn't send every WhatsApp ad chat to Meta (qualified leads vs thin Hi)

Bare Hi openers from Click-to-WhatsApp ads don't become Meta conversion events. Learn what qualified rate means and how to fix creative that attracts browsers.

7 August 2026 · 7 min read · Timi Labs

Imagine a Nairobi beauty-products shop spending KES 12,000 on a Reel and receiving 198 WhatsApp chats. Many stop at “Hi”; others ask for a specific bundle and delivery to Umoja. These hypothetical figures are not customer results. Conversation volume alone does not distinguish those buying signals.

Timi separates thin greetings from substantive ad-chat engagement. Bare openers are held back from conversion reporting; qualified interest and seller-confirmed sales help you review the funnel. Qualification is not payment, and sending events does not automatically change your campaign objective or guarantee better buyers.

This guide explains lead quality. Read CTWA attribution for the source path, Purchase confirmation for recorded sales, and the ROAS guide for spend comparisons.

The problem with optimising on raw chat volume

A small Click-to-WhatsApp campaign can still generate chats that do not progress. No daily spend amount guarantees conversations or sales. Conversations feel like success until you reconcile the till. Many chats never ask for a product, price, or delivery pin. They opened WhatsApp because the creative was pretty or the CTA was vague.

Counting every chat as a qualified conversion hides the difference between a greeting and product interest. Review those stages separately before deciding whether the offer, replies or follow-up need work.

Better signal: did the buyer engage beyond a bare greeting? Timi separates thin openers from qualified ad chats on your Ads dashboard and holds back low-intent openers from Meta conversion reporting until real interest shows.

What you see in Timi: thin openers vs qualified leads

Open Ads in your seller navigation after Meta is connected. You will see:

  • Ad chats — total Click-to-WhatsApp conversations in the period
  • Qualified rate — share that moved past thin openers
  • Thin Hi count — openers that stayed at greeting-level (shown alongside qualified leads in the KPI row)
  • Cost per qualified — spend divided by engaged ad leads, not raw chat count

In Feed, paid chats from CTWA show ad attribution labels. A thread can sit in Feed as an ad chat while Timi waits for substantive interest before sending qualified-lead events to Meta.

A thin opener may progress later after you or Timi answer a question. It simply is not enough evidence of a qualified conversion yet. AI replies are optional; response handling and outcome reporting are separate choices.

What Timi sends to Meta (and what it holds back)

For Click-to-WhatsApp ad chats with conversion tracking on, Timi reports milestones as buyers progress — see connect Meta Ads for the default event ladder (Lead submitted, Qualified lead, Checkout started, Purchase).

Bare "Hi" openers are not sent to Meta as qualified conversions. Timi waits until the buyer shows real engagement — a product ask, price question, delivery pin, or similar — before qualified-lead events flow. That keeps Ads Manager focused on interest, not curiosity.

When a buyer pays, Purchase fires only if you complete the payment loop — see when Timi sends Purchase.

Organic bio and Status traffic is separate: those chats convert in Feed but do not carry campaign referral for ad optimisation.

What you can do: creative and shop context

You control more of qualified rate than any dashboard setting:

Ask a specific question in the ad. "Message us for Size 8 stock and CBD delivery fee" beats "Chat with us on WhatsApp." Specific CTAs pre-qualify before the first reply.

Match creative to shop context. If the Reel shows KES 3,500 incl. delivery, Timi's first reply must quote KES 3,500 — not a stale KES 4,000 from last month's catalog. Mismatch creates ghosting after message two.

Hand off on payment signals. When a buyer asks for till or sends a pin, take over — see how to spot serious buyers. Timi handles catalog noise; you close payers.

One offer per ad set. Mixed catalog ads attract browsers comparing ten SKUs. Split collections so qualified rate reflects intent for one product line.

Signal health in Settings

Open Settings → Ad conversion tracking. The Signal health panel shows events Timi sent to Meta in the last seven days — qualified leads, checkouts, purchases.

If events were skipped, the panel explains in plain language: organic chats and bare Hi openers are not sent. That is expected behaviour — not a fault code you need to decode.

Use Send test event after connect; use Signal health weekly alongside Ads Manager review.

Meta conversations vs Timi qualified rate

Counts

Meta Ads Manager (native)
Conversations / messaging starts
Timi Ads dashboard
Ad chats + qualified rate + thin Hi

Optimisation fit

Meta Ads Manager (native)
Broad engagement
Timi Ads dashboard
Engaged buyers toward Purchase

Bare Hi impact

Meta Ads Manager (native)
Inflates volume
Timi Ads dashboard
Tracked separately, not sent as qualified CAPI

Best for

Meta Ads Manager (native)
Top-of-funnel tests
Timi Ads dashboard
Weekly pause/scale on paying outcomes

Metric scenarios above.

Use Meta for placement and spend delivery. Use Timi for whether those chats were worth the KES.

Qualification is one stage, not a sales guarantee

A buyer can ask for a price and still decide not to buy. A chat can qualify today and pay later. Compare similar offers and date ranges; do not rank a custom furniture enquiry against a small ready-stock accessory using the percentage alone.

Work through a practical sample: open a few ad-attributed chats, note the product question, inspect the response, and check whether a handoff or recorded sale followed. If interest is strong but sales are missing, investigate price, stock, delivery and payment recording before blaming acquisition.

New Timi accounts are for product businesses currently running Meta CTWA ads and selling mainly through WhatsApp. See the ads overview and pricing, then use Connect WhatsApp below. No website or minimum conversation volume is required.

Common mistakes

  • Assuming reporting changes your campaign objective — check the performance goals Meta makes available for your account and configuration
  • Blaming CAPI when creative is vague — 70% thin Hi is often an ad copy problem
  • Expecting every Feed ad chat to appear in Events Manager immediately — bare openers are held until engagement
  • Comparing qualified rate across different offers — a KES 800 impulse item qualifies differently than custom furniture
  • Ignoring thin Hi trend after a creative change — spike means the new Reel attracts browsers

Read the WhatsApp ads pillar guide for first-reply playbook and campaign structure.

FAQ

Does Timi reply to thin Hi openers? If you have enabled AI for that chat scope, it can reply. You can also handle replies yourself. Conversion reporting waits for eligible engagement.

Can I force every chat to Meta manually? No — and you should not upload spreadsheets to override. Fix creative and qualification instead.

What counts as qualified? Product, price, delivery, or payment interest beyond a lone greeting — Timi applies consistent rules so your team sees the same labels in Feed and Ads.

Will qualified rate improve automatically? No guarantee. Review the offer, creative and chat experience; reporting events alone does not change a campaign objective or ensure better delivery.

Does Instagram Reels behave differently from Feed? Destination matters (CTWA), not placement. Weak creative on Reels still produces thin openers.

Is there a universal qualified-rate cutoff? No. Review your own offer, margin and sales cycle, and check that payment recording and attribution are complete before making a budget decision.

Why Timi doesn't send every WhatsApp ad chat to Meta (qualified leads vs thin Hi) | Timi