Customer Support Chat Development
Budget: $2 – $8 USD
I’m building a dedicated customer-support chat for Balesin and need a developer who can deliver a smooth, professional experience on both our public website and our companion mobile apps (iOS and Android). The core must include real-time live chat, an always-available chat-history log, and secure file-sharing so guests can easily send screenshots, PDFs, or photos while speaking with an agent.
A single code-base that can serve Web and Mobile (React, Flutter, or a comparable framework) is ideal, but I’m open to separate native builds if that proves more reliable. Back-end choice is up to you—Node, Laravel, Firebase, or another scalable solution—as long as messages sync instantly and are stored safely for future reference.
Acceptance criteria
• Website widget and in-app chat screen both connect to the same back-end and exchange messages with <1-second latency.
• Conversations remain visible when a user refreshes the page, reopens the app, or switches devices.
• Users and agents can attach files up to 20 MB; downloads must be virus-scanned server-side.
• Basic agent console (web) shows active chats, history search, and file download links.
• Complete source code, environment docs, and a short video demo submitted for hand-off.
A single code-base that can serve Web and Mobile (React, Flutter, or a comparable framework) is ideal, but I’m open to separate native builds if that proves more reliable. Back-end choice is up to you—Node, Laravel, Firebase, or another scalable solution—as long as messages sync instantly and are stored safely for future reference.
Acceptance criteria
• Website widget and in-app chat screen both connect to the same back-end and exchange messages with <1-second latency.
• Conversations remain visible when a user refreshes the page, reopens the app, or switches devices.
• Users and agents can attach files up to 20 MB; downloads must be virus-scanned server-side.
• Basic agent console (web) shows active chats, history search, and file download links.
• Complete source code, environment docs, and a short video demo submitted for hand-off.