How to connect your website tools into one flow
Don’t wire tools. Follow one visitor to the result.
Everything loads from one script tag, so there is nothing to integrate. What makes the modules work as one is a handful of choices: which list a popup writes into, which list a sequence listens to, which button opens which calendar. Each flow below follows a single visitor through those choices, stop by stop, with what a month of it costs and where it breaks.
Three flows.
Three shapes.
A flow is one job, such as following up a lead or answering a question, built from several modules in an order chosen on purpose. Its shape says how the stations connect: a line, where each one feeds the next; a loop, where the last feeds the first, so it keeps improving; or a fork, where one decision sends visitors down different routes.
The lead line
Automated lead follow-up
Someone leaves their email. Then what?
A popup that writes into a list, a sequence that runs on that list, and a goal that counts what it earned.
- 01Popups
- 02Leads
- 03Sequences
- 04User Journey
The answer loop
AI chatbot with human handoff
A visitor asks something the bot cannot answer. Then what?
A bot that answers from your own words, hands the rest to you as a ticket and an email, and learns from every reply you give.
- 01AI Chatbot
- 02Support Tickets
- 03Live Chat
- 04Callbacks
The booking fork
Qualify leads before they book a call
Not every visitor should get the same calendar.
A scored quiz sorts visitors into hot, warm and cold. Hot ones book a time, the rest are followed up on their own.
- 01Quizzes
- 02Bookings
- 03Callbacks
- 04Sequences
Every flow reads
the same way.
A guide answers one question from start to finish. A flow follows one visitor through several modules, so it is the page to read before you decide what to switch on. Once you have read one, you can read them all.
Looking for a single answer instead? Browse the guides →
-
01
The map
A board that plays the flow once.
At the top of every flow, a dark board lights each station in the order a visitor meets it. Pause it or replay it; the chapters underneath say the same thing in words.
-
02
The stops
One chapter per module.
Each stop says what the module does for the visitor and what you set, and links to the module page when you want every option.
-
03
The handoffs
The one setting between two modules.
Between two stops, a ticket lists what travels and names the setting that makes it travel. It is the easiest thing to miss, so every one is written out.
-
04
The model
Change a rule, watch it move.
Each flow has a small working model with the product’s own rules and sample data: replay one lead’s first week, ask a toy assistant something it cannot answer, or score three answers and leave a gap on purpose.
-
05
The cost
A meter, with your numbers.
A meter multiplies the rate card by your own traffic, so you see the month’s credits before you build anything.
-
06
The traps
Where it breaks, and the fix.
Each flow ends with the ways it quietly fails: the symptom you will see, the likely cause and the setting that fixes it.
One real handoff · from the lead line
Four rules hold
in every flow.
Learn these once and each flow becomes a variation on them. They are also the first four things to check when a setup does not do what you expected.
One script tag, nothing to integrate.
Popups, quizzes, bookings, live chat, the chatbot, sequences and the rest all load from the one script tag on your site. They already share your lead lists and your sending domain, so a flow never asks you to connect anything. It asks you to choose.
A list is the hinge.
A door writes a person into a list only when you point it at one. Quiz outcomes, bookings, callbacks, popups and live chat each have a list picker. Sequences and broadcasts read from lists, never from popups, so the list you choose is the connection. A door with no list leaves no lead.
Every popup and block has an address.
In a popup’s or block’s Triggers settings, Open it from a link shows its address. Use it as the link on any button on a page that carries your script tag and it opens that popup, or opens the bubble at that block. It is how a quiz result opens a booking calendar.
Only usage has a rate.
Every module is included. What is metered is what happens: page loads, new leads, emails sent, tracked journeys, live chats and tickets. Each flow page turns those rates into a month’s total from your own numbers. Every account gets 250 free credits a month, packs start at $9 and purchased credits never expire.
Flows, in plain answers.
A flow is one job, such as following up a lead or answering a question, that takes several Builderify modules wired in order. Each flow page shows the stations in the order a visitor meets them, the one setting that connects each pair, what a month of it costs and what goes wrong.
No. Every module loads from the one script tag already on your site, and they share your lead lists and your sending domain. What a flow teaches is the few choices that make them help each other, such as which list a popup writes into and which list a sequence listens to.
A guide answers one question from start to finish, such as replacing a retired widget. A flow follows one visitor through several modules and shows how each handoff works, so it is the page to read before you decide what to switch on.
They are the three ways modules connect. In a line each station feeds the next. In a loop the last station feeds the first, so the flow improves itself. In a fork one decision sends visitors down different routes.
Every flow uses the same balance of Usage Credits as the rest of Builderify. Every account gets 250 free credits a month, packs start at $9 and purchased credits never expire. Each flow page has a meter that multiplies the rates on the pricing page by your own numbers.
Stop losing the visitors
you already paid for.
More leads from the traffic you already have, and follow-up that sends itself. Free to start. No card, no monthly fee.