Skip to main content

Documentation Index

Fetch the complete documentation index at: https://knowledge.flowella.io/llms.txt

Use this file to discover all available pages before exploring further.

If you’re running paid traffic to WhatsApp and the prospect needs to understand your product before a meaningful conversation can happen, the standard pattern is:
  1. Click-to-WhatsApp (CTWA) ad drives the click
  2. Pre-filled WhatsApp message opens the conversation
  3. WhatsApp template + Flow delivers the demo or asks qualifying questions
This works for simple offers. For more complex products — where the prospect needs to see the tool to understand it — inserting a HowdyGo interactive demo between the ad click and the WhatsApp conversation closes the gap. The lead arrives in WhatsApp having already self-served the high-level walk-through, and your team can have a much more useful conversation. This page covers the pattern Flowella uses on flowella.io and how to set it up for your own product.

​
The pattern

1

CTWA ad runs on Facebook or Instagram

Ad creative shows the product visually and offers “See it in action”. The destination is a landing page on your domain, not directly to WhatsApp — because you want the HowdyGo demo in between.
2

Landing page hosts the HowdyGo demo

The page embeds a HowdyGo interactive demo above the fold. The demo walks the prospect through the product without any signup, account, or sales call.
3

HowdyGo events fire when the prospect engages

HowdyGo’s analytics record how far the prospect got through the demo, which screens they spent time on, and where they dropped off. These events feed your CRM and your ads platform.
4

Click-to-WhatsApp button appears mid-demo and at the end

The page has a “Chat on WhatsApp” CTA that uses a wa.me link with a pre-filled code identifying the demo step they reached. See click-to-chat for the link format.
5

Flowella receives the inbound message with context

The pre-filled code lands in Flowella, which uses it to route the conversation:
  • If they dropped at the demo’s “templates” step, the auto-reply talks about templates
  • If they reached the end of the demo, the auto-reply offers to book a setup call
  • If they barely started the demo, the auto-reply answers “what is this?” type questions
6

HubSpot contact gets full context

Both the HowdyGo demo events and the WhatsApp entry_source land on the HubSpot contact record, giving sales reps a clear story of what the prospect saw before reaching out.

​
Why insert HowdyGo between the ad and the WhatsApp chat?

Three concrete benefits over sending prospects straight into a WhatsApp conversation:
A prospect who’s spent 3 minutes clicking through your demo has self-selected. They’ve seen enough to know it’s relevant, and they message with specific questions instead of “what does this do?”.Sales and SDR teams report that demo-engaged WhatsApp conversations convert 3–5x better than cold CTWA chats.
The HowdyGo demo filters out prospects who weren’t going to convert anyway. They click the ad, see the demo, decide it isn’t for them, and never start a WhatsApp conversation — saving your reps’ time.Net effect: WhatsApp conversation volume drops but qualified conversation volume stays roughly flat, lowering cost per qualified conversation.
Facebook’s Conversions API can receive the HowdyGo “demo completed” event as a conversion, allowing the ad to optimise on prospects who watched the demo, not just on those who clicked. This produces better ad targeting over time. See CTWA Ads for the Conversions API setup.

​
Setting it up

​
1. Build the HowdyGo demo

In HowdyGo, record the click-through that walks a new prospect through your product’s core value. Aim for 2–5 minutes if you watched it linearly. Most prospects will dip in and out rather than watch linearly, but the demo needs a coherent narrative for those who do. Key screens to highlight:
  • The problem before, briefly. One screen, not three.
  • The product in action, 3–5 screens, with the key clicks and outputs.
  • The outcome after, with a tangible result the prospect can imagine for their business.
Don’t over-narrate. Let the product UI carry the demo and use HowdyGo’s annotations sparingly.

​
2. Embed it on a landing page

Use HowdyGo’s embed code on a landing page on your domain. The landing page should:
  • Lead with the demo, not with marketing copy. The prospect just clicked an ad expecting to see the product.
  • Add a short value statement above the demo (one line, the same headline as the ad).
  • Place the click-to-WhatsApp CTA below the demo and as a sticky bottom bar on mobile.
  • Match the ad’s visual style so the prospect feels they’ve landed in the right place.

​
3. Wire up the WhatsApp CTAs with demo-stage codes

Use different wa.me links at different points in the demo so the prospect’s entry context lands cleanly in Flowella:
  • Above the demo: wa.me/<num>?text=Hi%2C%20I%20saw%20%5BFLOWELLA_DEMO_START%5D
  • Half-way: wa.me/<num>?text=I%27ve%20been%20looking%20at%20%5BFLOWELLA_DEMO_MID%5D
  • End of demo: wa.me/<num>?text=I%27ve%20watched%20%5BFLOWELLA_DEMO_COMPLETE%5D
Flowella parses the bracketed code and writes it to the contact’s whatsapp_entry_source property in HubSpot. See UTM tracking.

​
4. Route the WhatsApp conversation in Flowella

In Flowella, set up keyword-triggered workflows on the parsed code:
Trigger codeAuto-reply / Flow
[FLOWELLA_DEMO_START]Brief introduction and “What part are you most curious about?”
[FLOWELLA_DEMO_MID]”Looks like you got partway through — happy to walk through the parts you missed, or jump straight to your questions.”
[FLOWELLA_DEMO_COMPLETE]”You’ve seen the whole thing! Want me to book you a setup call?” with a Flow form for date selection
See Workflow Actions for the workflow trigger types.

​
5. Send HowdyGo events to HubSpot and Facebook

HowdyGo can fire webhooks on demo events. Configure two destinations:
  • HubSpot custom event API — record “Demo step viewed”, “Demo completed” on the contact (matched by email, or by the ctwa_clid parameter passed through from the ad).
  • Facebook Conversions API — send the demo events as conversions so the ad campaign learns to find more demo-engaged users.
See CTWA Ads for the Conversions API integration; the same pipeline carries HowdyGo events.

​
Measuring it

Build HubSpot reports that join the demo and WhatsApp data:
  • WhatsApp conversations by demo completion stage — do conversations that arrive from “demo complete” close at a higher rate than “demo start”?
  • Demo-to-WhatsApp conversion rate — what percentage of demo viewers tap through to WhatsApp?
  • Demo retention curve — where do prospects drop off? Use this to improve the demo itself.
See Reporting and dashboards.

​
When this pattern is overkill

Not every product needs an interactive demo before the WhatsApp conversation. Skip it and run CTWA directly to WhatsApp if:
  • Your offer is simple — a single product, a single price, a single “buy now” path. The prospect doesn’t need to understand the tool.
  • You’re running a discount-driven campaign — the offer is in the ad creative; an extra demo step adds friction without adding qualification.
  • Your audience is already aware of you — retargeting visitors who already know the product doesn’t need re-education.
For first-touch acquisition into a complex product, though, this is one of the most effective patterns we’ve seen.