Campaigns & analytics
Send approved WhatsApp templates to opted-in contacts and see where the resulting customer journey advances, converts, hands off, or stops.
Illustrative workflow outcomes from a first-party Fluenta template.
Product detail
A delivery report alone cannot show whether the workflow that followed did useful work. Keep campaign activity and journey outcomes distinct, then read them together.
Send approved WhatsApp templates only to contacts who have opted in to receive the relevant communication. Track delivery and replies as campaign events, distinct from the workflow outcome that follows.
Meta template constraints apply: outbound business-initiated messages use approved templates and the content must match the approved template policy.
Measure whether a customer reaches the intended completion node after entering the workflow. Completion shows that the configured journey reached its designed outcome, not simply that an outbound template was delivered.
Compare completion with entry and reply signals to find the point where a customer stops advancing.
Track order conversion where the workflow includes a defined order or payment outcome. Keep that event separate from message delivery so a delivered template is not represented as a completed purchase.
Use the workflow branch and captured variables to connect the conversion to the customer path that led there.
Measure how often customers reach a human handoff path. A rising handoff rate can indicate an unclear branch, a missing knowledge answer, or a business case that correctly requires human judgment.
Review the handoff reason with the workflow node that sent the conversation to operations.
Knowledge deflection describes a workflow outcome where an approved source answered the customer without a human handoff. Treat it as a journey measure, not as evidence that every question was resolved.
Keep the not-found path visible so unanswered questions remain explicit and reviewable.
Node-level drop-off shows where customers stop progressing through a configured workflow. Use the signal with the interaction type, branch condition, and simulator trace to investigate the specific step.
A drop-off is a prompt for inspection rather than a claim about why a customer left.
A/B testing can compare approved campaign or workflow variants when the capability is available for the chosen operation. Keep each variant within consent requirements and Meta template constraints before sending it to customers.
Read the result against workflow completion and conversion, not a delivery count alone.
Respect consent and Meta template constraints, then inspect the workflow outcomes your campaign actually creates.
Start building free