مشاركة مميزة
Show HN: FounderPhone – make customer support personal with SMS https://ift.tt/38EDEMJ
- Get link
- X
- Other Apps
Show HN: FounderPhone – make customer support personal with SMS Hi HN! We're Parthi and Kunal from FounderPhone (https://ift.tt/39LIHew). FounderPhone is a shared customer support inbox for SMS and calls in Slack. We've built and shipped 7 products recently and if there's one thing we've learned, it's that your personal relationship with your customer is your secret weapon as a startup. Having customers email support@company.com or message a bot via Intercom doesn't feel personal. People are skeptical they will ever get a response. We've had a lot of success giving out our phone number to customers we really care about and telling them to text us whenever something comes up. Apparently, lots of great founders like Patrick from Stripe did this while growing their startups. The problem is that personal phone numbers weren't designed for support at scale. So we hacked together a solution for ourselves where we made Slack a shared inbox. When a customer texts or calls me, our team can also see the messages and incoming calls. We can discuss how best to handle the issue in Slack and then anyone can respond via text. For calls, anyone available can redirect calls to their own number. From the customer's perspective, they're just texting a single number. They're not frustrated with messy tickets or being routed to 3 different people. They will always read your responses because it's in their SMS inbox instead of being lost amongst their 20,000 unread emails. This is just the start! We're looking into building a whole suite of software to make customer support feel both personal and immediate. We're making an integration with Segment and Sentry to alert you when a customer has an issue so you can reach out to them about it before they complain to you. Text our FounderPhone (510) 756-2522 with your name or email founders@founderphone.com if you have any questions. Thanks for checking us out! February 18, 2020 at 07:02PM
- Get link
- X
- Other Apps
Popular posts from this blog
The Cipher's Whisper
Liked on YouTube: الربح من الانترنت 50 دولار يومياً من مشاهدة اليوتيوب والتيك توك
الربح من الانترنت 50 دولار يومياً من مشاهدة اليوتيوب والتيك توك الربح من الانترنت من مشاهدة فيديوهات اليوتيوب والتيك توك ومشاهدة الاعلانات تعد هذة الطريقة من اسهل طرق الربح من الانترنت للمبتدئين . الموقع الذي بالشرح : https://bit.ly/3cN4GmI ▬ ▬ ▬ ▬ ▬ ▬ ▬ ▬ ▬ ▬ ▬ ▬ ▬ ▬ ▬ تابعنا علي : قناتنا الثانيه علي اليوتيوب : http://bit.ly/2prA33b جروبنا علي الفيس بوك : http://bit.ly/2JgyPhQ صفحتنا علي الفيس بوك | https://goo.gl/YmFW1X ▬ ▬ ▬ ▬ ▬ ▬ ▬ ▬ ▬ ▬ ▬ ▬ ▬ ▬ ▬ بعض الدروس من الممكن الأستفاده منها : الربح من CPA للمبتدئين 540 دولار شهريا [موقع يقبل الجميع] مع اثبات الدفع https://youtu.be/piaSrbB7Fm0 الربح من CPA للمبتدئين 540 دولار شهريا [اختيار افضل عرض CPA] https://youtu.be/OVwQrCSo7uI الربح من CPA للمبتدئين 540 دولار شهريا [إنشاء Landing Page مجانا] https://youtu.be/yXHyqDZxyHQ افضل طريقة لترويج عروض CPA للمبتدئين والمحترفين https://youtu.be/67cOvXv9wtU ترويج عروض CPA بطريقة مجانيه استراتيجية ذهبية [اربح 540 دولار شهريا] https://youtu.be/X0v57ots070 ▬ ▬ ▬ ▬ ▬ ▬ ▬ ▬ ▬ ▬ ▬ ▬ ▬ ▬ ▬ Who i am : M...
Launch HN: Datree (YC W20) – Best practices and security policies on each commit https://ift.tt/3cJCp13
Launch HN: Datree (YC W20) – Best practices and security policies on each commit We are Shimon and Eyar, co-founders of Datree ( https://www.datree.io ). We've built software to help engineering teams automate the adoption of development best practices, coding standards, and security policies. When I (Shimon) was the manager of a 400-developer company's infrastructure engineering team, we had an issue where a developer committed AWS secret keys into a public GitHub repo. We were very, very lucky that the bad actors who quickly got ahold of the keys "only" spun up compute instances to mine bitcoin. Mistakes happen and they happen to the best of us. No developer wants to make mistakes, especially ones impacting production. Those mistakes can be not only costly to the business, but emotionally painful for the developer. After finding out about the issue, I had to search for any other leaked secret in our repositories to make sure we were no longer exposed. The next thing...
Comments
Post a Comment