Answer from approved knowledge
Knowledge nodes answer from the content your team has approved rather than an unbounded reply.
For customer support
Resolve routine questions automatically. Hand over the hard ones with context.
Answer from approved business information, follow an explicit fallback when the answer is uncertain, and open a human ticket with the transcript and captured details intact.
The problem
Routine support should not erase human judgment
Customers want a fast first response. Your team needs approved answers, a clear fallback, and enough context to resolve the exception without asking the same questions again.
Outcomes
What the workflow improves
- Faster first response for routine questions.
- Consistent answers from approved business information.
- Less repeated data collection before an agent joins.
- Complete handoff context and a visible escalation rate.
Capabilities
The tools behind the work
Make fallback explicit
Use the not-found branch for clarification or human escalation when the source material is not enough.
Hand over the context
A ticket can carry the conversation transcript, customer details, and the reason the workflow escalated.
Inspect where automation stops
Use workflow and conversation activity to see answers, uncertainty, and handoffs.
How a flow looks
Controlled automation with a clear handoff
Give routine questions a consistent answer, then make uncertainty visible and hand the next step to your team.
Question
A customer asks
The WhatsApp conversation starts with the customer’s free-form support question.
Knowledge
Approved content is checked
A knowledge node routes an answered or not-found result deliberately.
Handoff
A person takes the hard case
The workflow sends the context your support team needs instead of a bare escalation.
Review
The team finds the gaps
Review the questions and paths that produced unanswered or escalated conversations.
Example workflow
Approved-answer support handoff
- 01Customer asks a free-form question.
- 02Knowledge node searches approved content.
- 03Answered path responds and offers the next action.
- 04Not-found path asks one clarification.
- 05Continued uncertainty creates a ticket.
- 06Agent receives transcript, customer details, and reason.
- 07Workflow resumes after resolution.
Demonstration workflow using a first-party Fluenta template.
Product truth
What is controlled
- Answer source
- Knowledge answers are grounded in the business content you have added.
- Fallback
- The not-found path is an explicit flow branch, so you can ask for clarification or route to a person.
- Handoff
- A human ticket carries the conversation context and captured details for the next person.
- Team role
- This workflow handles routine and well-defined paths; people keep judgment-heavy or uncertain cases.
Metrics
Numbers visible to the operator
- Knowledge questions
- Answered rate
- Not-found rate
- Handoff rate
- Time to human reply
- Resolution outcome
- Repeated unanswered topics
Questions
Before you build
Does this replace the support team?
No. It handles controlled, routine paths and preserves context when a person needs to take over.
What happens when the knowledge base does not answer?
The workflow follows its not-found branch, which can ask one clarification and then create a human ticket.
Can we choose what the workflow answers?
Yes. The knowledge source and the explicit branches are part of the workflow your team configures.
Build a support workflow your team can inspect
Start with approved information, define the fallback, and test the handoff before you publish.