Description
Summary About us We're building a software platform (a lead-routing / autodialer tool) for US home service businesses. The company behind it is a Ukrainian sole proprietor (FOP); note that the legal entity name does not match the project name. What we need We want to integrate Twilio to power a call-bridging autodialer: a lead comes into our platform, we call the business, they pick up, we call the customer, and we connect the two. When we call the end customer, we want the call to display a phone number associated with the client business as caller ID. We're still deciding on the best way to set this up and would like your input (see below). We previously created a Twilio account and applied for approval but were rejected – the issues appeared to be related to how we filled out the forms, and we haven't resolved them yet. Key requirements Guide us to full Twilio approval for this use case. We need to purchase US phone numbers (not Ukraine) – this is essential. We'd like your advice on the right mix of local vs. toll-free numbers. Our current plan is to set up subaccounts for each client company under our parent account (we'd like it structured similar to how LeadWinner does it, which works smoothly for them). The client business's phone number, verified with Twilio, would then be used as caller ID when we call the customer. However, we noticed a competitor does it differently: the business enters their phone number and verifies it via SMS/call (Twilio's process). Our guess is that they don't register customers as subaccounts, but instead use their own pool of numbers that they provide to customers. We'd like your recommendation on which approach is most compliant and practical for our case – subaccounts, the competitor's approach, or something else. Our clients are legitimate home service businesses – no bulk calling, no spam. This is a compliant, "white hat" use case. Who we're looking for Someone with hands-on experience getting Twilio accounts approved, ideally for non-US companies and for voice/autodialer use cases — not just basic Twilio API coding. You can either consult (hourly) on the right approach, or help us implement it end to end. To apply Please briefly describe a similar Twilio approval or autodialer project you've handled, especially any involving US numbers for a non-US business. Let us know whether you'd prefer a consulting or hands-on role, and your rate.