BRANCH

Operator playbook

Interested people need a next step they can trust.

A person can want a class, league, club, or event and still not act because they do not know which option fits, whether they belong, or what happens next. Branch resolves that uncertainty and carries the context toward attendance and return.

Private preview. No migration. No members contacted.

The useful answer

What to do when this problem appears.

Operators with real demand, multiple offerings, and a meaningful gap between website interest, first action, attendance, and repeat participation.

Start here: Treat “I want this, but I am unsure” as actionable intent. It is different from both a ready buyer and a person who said no.

How Branch handles it

A practical operating sequence.

01

Separate interest from readiness

Treat “I want this, but I am not sure what to do” as a real state between curiosity and a no—not as a dead lead.

02

Route one personal next step

Use the person’s goal, fit, timing, and questions to narrow a complicated supply side into one approved booking, RSVP, registration, or visit.

03

Carry context beyond the first action

Keep the thread moving from decision to arrival to the next visit instead of restarting with a generic reminder at every stage.

Practical playbook

Use this on your next operating cycle.

01

Recognize the middle state

Treat “I want this, but I am unsure” as actionable intent. It is different from both a ready buyer and a person who said no.

02

Classify the blocker

Use bounded categories such as fit, belonging, logistics, timing, price, placement, or missing next step.

03

Resolve one decision

Answer the blocker and recommend one approved action. Do not overload the person with every possible offering.

04

Keep the context

Carry the answer into booking, arrival, attendance, and return follow-up so the person does not have to explain themselves again.

WORKED EXAMPLE

A complete site still leaves a decision open

A visitor can read every class page and still ask which class is right for a beginner who comes alone. The missing product is routing through the options, not another page of options.

MEASUREMENT

Measure intent resolution

Track qualified conversations by blocker, recommended action, action completion, and verified attendance. Review unknown classifications separately.

What to measure

Measure movement, not message volume.

The distinction

Information ≠ decisionA complete website can still leave a prospective participant unsure what to choose.

The analogy

A menu needs a waiterPeople often need routing through the options, not another page containing options.

The measure

Intent → attendanceJudge the layer by follow-through and verified participation, not by message volume alone.

Where teams go wrong

Avoid the shortcuts that hide the real problem.

Calling silence disinterest

Some people are waiting for one fact that the current site or follow-up did not provide.

Letting the model invent certainty

Unknown policy or availability should trigger an escalation or explicit limitation.

Questions operators ask

Clear answers before the next action.

What is unresolved intent?

Unresolved intent is the state where someone is interested in an experience but has not completed the decision because fit, belonging, logistics, timing, or the next step is still unclear.

How is Branch different from a website chatbot?

A chatbot can answer a question in one session. Branch is designed as the follow-through layer that understands the person’s goal, routes the next action, and carries context toward attendance and return.

Does Branch replace a booking or membership system?

No. Existing systems record offerings and transactions. Branch works around them to help people choose, commit, show up, and continue.

Private Branch preview

Show us where people get stuck.

Test a preview built around your real offerings, policies, questions, and conversion path.

Preview this workflow