Inventoried common customer intentions and content sources
Configured and reviewed within the relevant platform context, with QA and evidence boundaries documented.
Better Gas case studiesWork · Better Gas · Automation
WhatsApp Chatbot — General Enquiries Automation
I translated common customer intentions into a structured WATI workflow for cylinder exchange, general enquiries, delivery information and team handoff.
ClientBetter Gas Energy Services Limited
SectorLPG retail, cylinder exchange & distribution
GeographyNigeria · Abuja/FCT & surrounding distribution areas
RoleStrategy, implementation, management & analysis where supported
Evidence window2026 WATI workflow editor snapshot
Engagement datesNot independently established
Workflow screenshots prove the automation design; customer volume, resolution rate and revenue impact require separate operational reporting.
The chatbot workflow organized recurring LPG enquiries into menu branches, guided questions, conditions and team-assignment paths while preserving human escalation.
Delivery architecture
How the work was structured.
A case-specific operating model rather than a generic service checklist.
01Intent
02Menu / question
03Condition
04Team escalation
Implementation translated into operational value.
Modelled menus, buttons, conditions and validation
Configured and reviewed within the relevant platform context, with QA and evidence boundaries documented.
Configured escalation and team-assignment paths
Configured and reviewed within the relevant platform context, with QA and evidence boundaries documented.
Tested branches with sample conversations
Configured and reviewed within the relevant platform context, with QA and evidence boundaries documented.
Documented activation and monitoring criteria
Configured and reviewed within the relevant platform context, with QA and evidence boundaries documented.
Separated workflow design evidence from outcome claims
Configured and reviewed within the relevant platform context, with QA and evidence boundaries documented.
What the available reporting actually proves.
Workflow visible
Source: WATI workflow editor
Period: 2026 capture
The screenshot establishes the workflow design, not volume served.Node types visible
Source: WATI workflow editor
Period: 2026 capture
Node presence does not establish completion or resolution rate.Assign Team step visible
Source: WATI workflow editor
Period: 2026 capture
Routing logic requires operational reporting to evaluate effectiveness.Decision logic, implementation and QA.
- 01
Inventory customer intents
Review the platform state, implement the relevant configuration, test the customer/measurement path and document the operational handoff.
- 02
Model menus and branches
Review the platform state, implement the relevant configuration, test the customer/measurement path and document the operational handoff.
- 03
Set escalation and fallbacks
Review the platform state, implement the relevant configuration, test the customer/measurement path and document the operational handoff.
- 04
Test sample conversations
Review the platform state, implement the relevant configuration, test the customer/measurement path and document the operational handoff.
- 05
Define activation and monitoring criteria
Review the platform state, implement the relevant configuration, test the customer/measurement path and document the operational handoff.
Commercial significance without overstating causality.
Observed / configuredMarket demand / audience
Observed / configuredDiscovery or click
Configured / measurableBetter Gas web / messaging experience
Configured / measurableMeasurable enquiry
Configured / measurableHuman / automated follow-up
Only where independently evidencedOrder or visit where independently evidenced
The evidence on this page distinguishes observed platform state, configured journeys, forecasts and future measurement requirements. Where purchase attribution is absent, no ROAS or ROI claim is made.
Original evidence is tracked separately from presentation mockups.
Privacy review required
Wati - WhatsApp Automation(workflow).png
What this proves: this source is part of the documented evidence set for the case study.
What remains unverified: any metric, identity or operational claim not explicitly described in the evidence panel above.
Raw admin screenshots are not rendered publicly until sensitive data is redacted and approved.Recommended next measurement and operating improvements.
Measure branch completion and escalation rates
Review unanswered-intent logs monthly
Connect chatbot outcomes to CRM lifecycle stages
Next project
Need a similar result-oriented setup?
Discuss the business problem, the platform environment and the evidence you need to measure next.