Hacker News new | ask | show | jobs
by rjaco31 4086 days ago
I think there's something I'm missing about it. Usually, the most annoying part about 'important calls' is that they won't exactly be right on time & you'll have to wait starring at your phone for a couple of minutes. I don't see how this solve that problem.
1 comments
dotmike 4086 days ago
rhaco31, you are right. Callr, in its current form, solves the first big pain point which is remembering when your calls are and dialing them in. If it's a conference call with long PIN, it becomes really handy as well.

For the scenario you mentioned, the hope is the other party will start using Callr as well so that s/he will be on time. We built a 'Share the Love' feature so that our users can show them the light :-)

Does this adequately answers your question?

link
rjaco31 4086 days ago
Oh, I guess I didn't dig enough in how it does actually work. So I have two new questions :

- Do you need to format your calendar events in a certain way for Callr to understand them & extract number/PIN? Looking at my actual confcall entries, not two have the same format and most of them have tons of different numbers depending of the country (the one I'm looking at atm has 10 different phone numbers in the calendar entry for instance)

- How do you address the privacy problem of having to upload your whole business calendar to your server? Imho that would be forbidden in most places.

link
dotmike 4085 days ago
Not a problem; here are the answers

1. No, you do not need to format your calendar in any special way. We've developed a machine learning algorithm that automatically figures out the correct phone number and PIN number (if available). It works in 99.98% of the cases. In those rare cases that it misses, Callr will ask the user for a feedback and adjusts the algorithm based on that input.

2. There are a couple of important points; Callr only looks at a few days worth of events at a time and we did that by design. This will ensure that Callr does not have more information than it actually needs. Once the data is pulled, Callr is built like a fortress; we encrypt it with AES-256 to make sure it's fully locked. We wrote about clearly on our privacy page: http://www.getcallr.com/privacy-policy/

link