I’m building a full-featured interpreting platform that lets our clients choose how they connect with language professionals—video, phone, or on-site—simply by speaking a request or using more traditional inputs. Scope • Three interpreting modes: virtual remote interpreting, over-the-phone interpreting, and onsite interpreter scheduling, all managed from the same interface. • Three interaction styles: voice commands for hands-free operation, plus keyboard/mouse and touchscreen for desktop and mobile users. • Role-based access: distinct dashboards for clients, interpreters, administrators, and an additional scheduler/project-manager role with permission controls. Core requirements 1. Integrate best-fit APIs for video conferencing, VoIP, and real-time captions; the stack is flexible as long as it is reliable and well-documented. 2. Create a clean, multilingual UX that guides users from service request to session completion, including automated notifications and status updates. 3. Build secure authentication and session logging so administrators can monitor interpreter availability, call quality, and billing metrics. 4. Provide an admin console where I can tweak language pairs, pricing tiers, and interpreter rosters without code changes. 5. Deliver clear technical documentation and hand-off support so our internal team can maintain and extend the system. We'd like this to be based on as much AI and Automation as possible. If you’ve architected similar voice-enabled communication solutions or interpreting platforms, I’d love to see your approach, preferred tech stack, and live examples. RULES: 1. Please do not try to contact us outside of Freelancer platform. We are accepting clarification questions until Tuesday November 4th at 4 pm EST. 2. Everyone responding to this post should be a verified company or freelancer with government issued ID. 3. Please provide detailed quote. We've uploaded the overview specs document for your reference. NOTE: This document's details are NOT written in stone and can change later based on our findings and evolving feature needs of the portal. 4. Your bid should be as practical/real as possible based on the specs document. Do not create a placeholder bid to create a low-ball offer.