Custom software development company for web, mobile & AI

Twilio + OpenAI inbox automation

RelayHub started from a blunt observation: phone and chat should not live in separate tools. Sales and support kept losing the thread when a caller switched to SMS or a chat widget. The brief was one shared inbox. Twilio traffic and digital messages land together. AI clears the routine work so people only jump in when judgment matters. Teams also needed to steer the assistant without shipping a new build every time the script changed. Admin-controlled prompts per contact group were in the brief from day one. File digests mattered too. Long PDFs and call notes piled up unread. The product needed a path from upload to a short summary the whole group could scan before the next shift. Nobody on the project believed every reply should be fully automated. Refund fights, tone-sensitive replies, and messy exceptions still need a human. RelayHub uses OpenAI to draft, summarize, and clear the easy queue so senior staff spend time on work that actually needs them.

AI fleet advisor + live load board

RouteMind exists so shippers and carriers can see loads, capacity, and routes in one place. Dispatch should cost less time and fewer wasted miles. The product pairs a live load board with an AI Fleet Advisor. Planners match freight to available trucks and compare paths with real map data instead of gut feel. Empty miles and stale boards were the business pain. When capacity is a guess, trucks deadhead and fuel burns for no revenue. Status, distance, and advisor guidance had to show up in the tools dispatchers already live in. Another spreadsheet export at the end of the shift was not going to cut it. Dispatchers needed advice that respected current capacity, not a generic logistics chatbot. The Fleet Advisor had to read live loads and vehicle state, then suggest moves a planner could accept or reject in the same UI. RouteMind was never meant to replace judgment. It was meant to cut the time spent assembling the picture before judgment starts.

Rentals, deposits, and return logistics

Loom & Luxe makes designer dresses reachable for short events. Shoppers browse an editorial catalog, book a rental window, pay a fraction of retail, and get pickup handled when the window closes. Owners and brands need inventory, active rentals, and earnings in one lender dashboard instead of side chats and spreadsheets. The business needed rental commerce that feels like shopping, not a form dump. Deposits, delivery addresses, and returns had to be productized. If those steps stay manual, the marketplace cannot grow past a handful of garments and a very patient ops person. Trust sits at the center. Renters need deposits and holds that feel fair. Lenders need payouts and inventory status they can verify. Both sides had to feel comfortable putting real garments and real event dates into the system, not treating it like a weekend experiment. The storefront had to feel like fashion retail while the backend behaved like a logistics system. Pretty pages without return automation fail. Automation without an editorial catalog fails too. That tension is the real product.