Hi @George Shields George, I saw your post. That is a great spec, and I like that the core logic is decision trees, not free-form chatbot output. I can build the MVP exactly in your priority order: 1. SMS end-to-end on Twilio 2. Load your JSON trees, match to the right tree, and run step-by-step routing 3. Session state per tech (current node + history) so it stays consistent across texts 4. Tight “service manager” tone layer 5. Then add voice (STT/TTS) once SMS is solid A couple quick questions: - Are your 25 diagnostic trees already in JSON, or do they need to be converted? - How do you want sessions identified for SMS (phone number only is fine)? - Any preference for state store (Redis is simplest, Postgres also works)? If you want to talk, you can book here: https://cal.com/mvpdevs/30min If you want, I can also give you a “price anchor” message for him (since this is likely a paid MVP).