I'm working on a marketplace website that connects homeowners with tradespeople. The idea is to allow homeowners to contact tradespeople directly or post tasks which are sent to suitable tradespeople. We want to mask the phone numbers when homeowners call tradespeople, using numbers purchased from Twilio. However, my client insists on charging homeowners for these calls, but currently, homeowners can use the site for free and it seems counterintuitive to make them pay for calling. Also, I'm trying to figure out how to track the call duration since it involves extra complexity. My client has floated ideas like a token system for calls, but that would require major redesigns just before launch. I'm also puzzled as to why we can't just let tradespeople share their real numbers. Could anyone share their thoughts on how to handle this situation?
4 Answers
The whole situation seems contradictory to me. Your client wants homeowners to pay for calls, but they're supposed to use the platform for free? That's a mismatch. If you want homeowners to pay in some way, you really need a subscription model for them as well. Without that, you're just creating friction. Honestly, allowing direct number exchanges feels like the simplest way out of this. You avoid complicating your platform right before launch!
Why complicate things with extra charges when you can just absorb the costs for now? It’s common for platforms to take on call costs until they prove their value. Once you establish your marketplace, you might find ways for tradespeople to cover those costs indirectly—like integrating call minutes into subscription prices. If homeowners are not paying initially, fret less about that cost. Focus on making sure your platform operates smoothly first, then adjust as needed once you have users and feedback.
It sounds like a tough spot! The reason you might not want to let tradespeople give out their real numbers is to protect your revenue model. If you connect homeowners and service providers, masking details allows for commissions on those connections. But yeah, once they communicate, there's nothing stopping them from exchanging real info anyway. As for charging homeowners, if they know they’re getting a valuable service, they might be willing to pay—just not directly for the calls. Maybe charge a flat fee for access that includes some call time, and track the usage. It simplifies things and keeps homeowners happy without scaring off tradespeople.
You’re definitely dealing with some scope creep here. Number masking is part of your platform's functionality; consider it included in the subscription price. Instead of charging for calls, focus on providing call tracking as a value add for tradespeople—after all, they will charge homeowners somehow! Just make sure your subscription covers those operational costs. You really don’t want to confuse users at this stage—keeping it simple and effective is key. If necessary, raise the subscription fee rather than complicate things further with token systems or direct charges for homeowners.
Related Questions
How to Build a Custom GPT Journalist That Posts Directly to WordPress
Cloudflare Origin SSL Certificate Setup Guide
How To Effectively Monetize A Site With Ads