Hello
I am building a chatbot with Ideta that runs across multiple channels (e.g., website, Facebook Messenger, and WhatsApp) & I have run into a challenge managing user context dynamically across platforms. 
Each channel has slightly different user interaction patterns, so a one-size-fits-all context structure doesn’t always work. I’m using webhooks and the Ideta API to sync external data, but context sometimes gets lost / behaves inconsistently when switching channels or restoring previous sessions. 
What’s the best practice for keeping context coherent across these channels while preserving personalized responses and session continuity? Should I maintain a centralized external state store (e.g., Firebase or Redis) & sync context through API calls, or is there a more native Ideta-centric method that I might be overlooking? 
Checked Ideta Developer Docs – API & WebhooksTalend Certification guide related to this and found it quite informative.
Would love to hear how other developers are managing multi-channel bot memory, especially when dealing with variable intents, fallbacks, and language models. Any guidance or shared patterns would really help me scale this bot cleanly without bloating the backend logic.
Thank you !! 