Omnichannel No-Code AI Assistant
Budget: $150 – $350 USD
I have already sketched out the entire stack—Voiceflow for the conversational logic, Twilio for phone connectivity, Google Sheets as the lightweight database, Make.com to pass data between services, and Axiom.ai to drive browser tasks inside carrier portals and our own web forms. Now I need someone who can wire the pieces together so the experience feels seamless on desktop, mobile chat, and a live phone call.
Core user journey
• A caller or web-chat user identifies themselves.
• The assistant pulls their account details from Google Sheets.
• If the user is new, it collects the needed fields, writes them back, and continues.
• When asked, it jumps into Axiom-powered automation to retrieve a real-time quote from a carrier portal or our internal form.
• It can text the results (or any follow-up info) via Twilio before ending the session.
Key functions that must work from day one
– Retrieve customer information (mainly account details)
– Collect and input new or updated customer data
– Send confirmation or quote details by text
– Handle the full flow by voice or web chat with identical logic
I will have the accounts everything else is blank canvas. Your task is to connect the dots, test end-to-end, and document the setup so I can maintain it. If it goes well, I’d like an ongoing relationship for feature tweaks and additional automations, so an affordable, modular build is essential.
Please outline how you would structure the Make.com scenarios, any constraints you foresee with Axiom.ai in carrier portals, and the timeline you’d need for a first production-ready version.
Core user journey
• A caller or web-chat user identifies themselves.
• The assistant pulls their account details from Google Sheets.
• If the user is new, it collects the needed fields, writes them back, and continues.
• When asked, it jumps into Axiom-powered automation to retrieve a real-time quote from a carrier portal or our internal form.
• It can text the results (or any follow-up info) via Twilio before ending the session.
Key functions that must work from day one
– Retrieve customer information (mainly account details)
– Collect and input new or updated customer data
– Send confirmation or quote details by text
– Handle the full flow by voice or web chat with identical logic
I will have the accounts everything else is blank canvas. Your task is to connect the dots, test end-to-end, and document the setup so I can maintain it. If it goes well, I’d like an ongoing relationship for feature tweaks and additional automations, so an affordable, modular build is essential.
Please outline how you would structure the Make.com scenarios, any constraints you foresee with Axiom.ai in carrier portals, and the timeline you’d need for a first production-ready version.