3 ms·
I'm building a product now that focuses on "services that travel to the customer" (house cleaning), but for some services it might not be as big an issue as for
by cpher 16y ago
I'm building a product now that focuses on "services that travel to the customer" (house cleaning), but for some services it might not be as big an issue as for others. For example, a house cleaning service might actually expect them to not be home regularly. Kind of depends on whether interaction with the client is required.
In our client conversations so far, missed appointments (not home) hasn't been brought up, so it will be interesting to see if that continues to hold true.
Patrick, thanks for sharing your process!
- sourc3 16y agoThis is actually very interesting. Because you can just turn this around make sure that the person at home leaves their house at that time because someone is coming :) Out of curiosity are you also working on an appointment specific service?
- cpher 16y agoYes, appointments are part of it, but also simple timekeeping for hourly employees, managing schedules, etc. So, a cleaning might be scheduled for 3 hours, but it may take 5 hours--this needs to be accounted for. We may also integrate scheduling based on spatial analysis of available employees. We're still early in the process (much earlier than Patrick is w/ AR), but we've also explored the idea of integrating Twilio. It's nice to see how it's being used. Edit: it's not a general purpose appointment manager and reminders are not central to my product. More of a basecamp-like app for cleaning services, of which appointments are a part. What are you working on?
- patio11 16y agoI cannot stress enough how much value customers will perceive from a few days of work with Twilio. You can have remote crews punch in and punch out on their cell phones. This reduces paperwork and saves labor costs.