Use case

Lead capture to booking

The gap between an enquiry and a confirmed booking is where most leads die. This journey closes it by asking for what you need one question at a time, then putting the slot in the diary while the person is still in the conversation.

Trigger · new contact or keyword Approval-first
How it runs

Step by step, with the channel named.

01
An enquiry opens a conversationFrom an ad, a comment, a DM or a saved number. The source is attached.WhatsApp
02
A form asks one question at a timeEach answer validated and written to the contact as structured data.WhatsApp
03
An owner is assignedExplicit ownership, with takeover recorded if it changes hands.WhatsApp
04
The slot is confirmedAn approved template with the details filled from the record.WhatsApp
05
A reminder follows on scheduleConsent re-checked at send time, not at signup.WhatsApp
What runs it

The parts of uxjo doing the work.

CaptureIn-chat forms

Typed and validated answers instead of free text somebody has to read.

ConversationAssignment and takeover

One thread, one owner, and a record of who took it over.

JourneysConfirmation and reminder

Dated steps that re-check consent before each send.

GovernanceEvery send audited

Who approved it, when it went out, what it cost.

How it is built

The journey, as it exists in Studio.

A trigger, the conditions that hold it back, and the branches that decide what happens next.

Journey StudioPublished
New contact or keywordTrigger · any channel
Consent and suppression checkedCondition
Send the qualification formWhatsApp · form step
Assign an ownerInternal · no message
Confirm the slot, then remindTemplate · dated step

The branch on the right sends nothing. A journey step can be an internal action, which is how ownership gets decided before anyone is messaged.

Built once, runs on every enquiry.The same journey fires whether the enquiry arrived on WhatsApp, an Instagram DM or Messenger.
What changes

The same job, before and after.

Without uxjo

  • The brief lives in a chat scroll somebody has to read back
  • Two people answer the same enquiry, or nobody does
  • The slot is agreed in words and forgotten by Friday
  • No record of who promised what

With uxjo

  • Validated answers written to the contact as structured data
  • One owner per thread, with takeover recorded
  • A dated confirmation and reminder, consent re-checked at send
  • Every send in the audit chain with its approver
Every channel

What each channel contributes.

WhatsAppWhere the form runs

One question at a time, each answer validated and stored.

InstagramWhere the enquiry often starts

DMs and comments arrive in the same queue as WhatsApp.

FacebookLead ads and Messenger

A form fill becomes a contact with its answers attached.

EmailFor the ones who go quiet

A later step through your own provider.

Questions

What people ask before they start.

What makes this better than asking in chat?

A form writes structured, validated data onto the contact record. Free text has to be read and retyped by a person, which is where details get lost.

Can the form branch?

Yes. A journey can branch on an answer, so a different qualification path runs for a different budget or service.

Does it work on channels other than WhatsApp?

The form runs where the conversation is. Instagram DMs and Messenger arrive in the same inbox, and email can carry a step in a longer sequence.

What stops a lead being answered twice?

Ownership is explicit per conversation, and takeover is a recorded action rather than a silent one.

Industries

Who runs this most.

Not on this page?

Your journey is the one we have not listed yet.

Every business has a flow that is only theirs. Describe it in a message and we will map it with you, name the triggers, and tell you honestly what runs today and what does not. No form, no wait.

Talk to usStart free