u/Professional_Sign230

I’d go with a hybrid approach: use RAG to find relevant content, MongoDB to handle specific data queries, and tool calling when the chatbot needs to take action. The key is to keep answers grounded in your actual data and test them regularly to make sure they’re accurate and useful.

If you’re building your first AI agent, I wouldn’t overcomplicate the model choice. Start with a strong, affordable model and focus more on the agent architecture, tools, memory, and prompts.

You can prototype with a cheaper model first, then move to a more capable model only where you actually need it. That usually gives you a much better cost-to-performance balance than paying for the most expensive model from day one.

And honestly, you don’t need Fable to build something impressive. Start small, get the workflow working, measure where it struggles, and upgrade selectively.

Yes, same in india

I write usually for myself, on topics that interest me. Sometimes, when something is trending, I also share my personal opinion. The act of writing itself is valuable to me. And whenever one of my blogs reaches multiple readers, it feels rewarding—it gives me a sense of purpose and value for the effort I put in.

I agree 4o was the best, it had helped me doing great great research, advices i can never forget...i wish we could bring it back

If you’re looking for something user-friendly, I’d check out Monday. It’s built for non-technical teams, so you can set up automations like “when a status changes → send a Slack message” without coding. It’s reliable for the basics, and they’ve been adding some AI features too.

If you want something a bit more flexible (but with a steeper learning curve), Zapier or Make could also be options — though those feel more “techie".