We build and improve chatbot journeys, integrations, and reporting on Turn.io and RapidPro/TextIt, helping your team turn programme requirements into a working messaging experience.
Turn.ioRapidPro / TextItBuilding chatbots since 2019
Example journeyIllustration
01
Registration
Welcome. Reply YES to join the programme and receive weekly updates.
02
Question
Which district do you live in? Reply with the number from the list.
03
Response
4
04
Integration
Contact record updated in programme system
Illustration of a typical journey structure. Not a real customer journey or result.
Services
Scoped engagements, then ongoing support
Each engagement starts from a written scope with agreed deliverables and acceptance criteria, so you know what will be handed over before work begins.
Review and improvement plan
Review an existing chatbot, identify friction and technical gaps, and define a prioritised improvement plan.
Problem addressed
A chatbot has grown over time. It is unclear where participants drop off, which flows are fragile, or what to fix first.
Deliverables that can be agreed
Written review of journeys, configuration, and integrations
List of friction points and technical gaps
Prioritised improvement plan, with each item ready to scope
Journey build or improvement
Build or refine registration, surveys, content journeys, and other agreed workflows.
Problem addressed
Programme requirements exist in documents and spreadsheets but not yet as a working, tested journey.
Deliverables that can be agreed
Agreed journey specification
Built and tested journeys in your workspace
Test checklist matched to the acceptance criteria
Integrations and reporting
Connect chatbot workflows to relevant business systems and develop useful reporting.
Problem addressed
Chatbot data sits in the messaging platform, separate from the systems and reports your team relies on.
Deliverables that can be agreed
Agreed data mapping between the chatbot and named systems
Working integrations for the systems in scope
Reports or data exports defined at scoping
Migration and handover
Help move agreed journeys and integrations between platforms, with testing, documentation, and team handover.
Problem addressed
Moving between platforms risks broken flows and lost data, and can leave the team unsure how the new setup works.
Deliverables that can be agreed
Inventory of journeys and integrations to move
Rebuilt and tested journeys on the target platform
Documentation and a handover session with your team
Ongoing support
After handover, an ongoing support contract keeps your chatbot developing alongside the programme.
Problem addressed
Programmes change after launch. Content needs updating, new needs arise, and staff change, but a one-off build leaves no one responsible for keeping up.
What it can cover
Content support: updates to messages and journeys
Additional functionality as the programme develops
Training for your team
Delivery approach
How a scoped engagement runs
The same stages apply whether the work is a review, a new journey, an integration, or a migration.
Step 01
Understand
Understand the programme and existing system.
Step 02
Agree
Agree scope, deliverables, and acceptance criteria.
Step 03
Build and test
Build and test the agreed workflows.
Step 04
Hand over
Document and hand over.
Then
Ongoing support
Content support, additional functionality, and training under a support contract.
Separate costs. Platform subscriptions, messaging charges, and hosting are scoped separately where applicable.
Your platform. Work is delivered in your existing Turn.io or RapidPro/TextIt workspace. You keep ownership of the journeys and documentation we hand over.
Platforms and capabilities
We build on the platform you already use
Our experience covers Turn.io journeys and RapidPro/TextIt workflows, including messaging journeys, integrations, and reporting.
Platform
Turn.io
Journeys
Turn.io journeys for WhatsApp programmes: registration, surveys, and content delivery.
Integrations
Connecting journeys to external systems using the integration options available in your workspace.
Reporting
Reporting on journey and contact data agreed during scoping, including dashboards and support with analysing the data.
Platform
RapidPro / TextIt
Workflows
RapidPro and TextIt flows across the channels configured in your workspace, such as WhatsApp and SMS.
Integrations
Webhooks and API connections between flows and your programme systems.
Reporting
Reporting built from flow results and contact data, including dashboards and support with analysing the data.
Responsible use of AI in journeys
Where a programme adds AI services to a journey, we scope them with clear boundaries: participants are told when they are interacting with an automated system, and we help you choose suitable AI providers and models, build guardrails around what the AI can say, and monitor and evaluate its responses over time.
Capabilities differ between platforms, versions, and plans. We confirm what is possible on your workspace during scoping. Turn.io, RapidPro and TextIt are the property of their respective owners. BotFlow Dev is not affiliated with or endorsed by them.
BotFlow Host
Need managed RapidPro infrastructure too?
BotFlow Dev handles the journeys and integrations. BotFlow Host operates dedicated RapidPro infrastructure, including monitoring, backups, upgrades, and recovery.
Development can be delivered on your existing platform. You do not need BotFlow Host to work with BotFlow Dev.
