dougiebuckets

7 ms·

31.
by dougiebuckets 14y ago
This is awesome! I love seeing comments like this. You obviously know the space which is great! I think you'll find that we're approaching telephony from a different perspective. We're a bootstrapped company of developers building a product
32.
by dougiebuckets 14y ago
Thanks Michael! With regards to your questions... 1. The flat-rate is $27/mo per channel. TelAPI also offers channel bursting . This ultimately means developers and businesses have on demand access to additional channels for TelAPI numbers
33.
by dougiebuckets 14y ago
Absolutely. Some of the more notable include: "The ability to set your outbound Caller ID to any number" - This is an attribute in our <Dial> element which allows developers to build systems that initiate calls from the phone number
34.
by dougiebuckets 14y ago
Hi ewang, thanks for pointing this out. Each telephony API handles pricing a bit differently. For instance, a production US phone number with Tropo is $3/mo whereas with TelAPI it's only $1/mo. A production toll free number with Tropo is $5
35.
by dougiebuckets 14y ago
Nate is definitely a sharp dude. We're lucky he's a part of the team.
36.
by dougiebuckets 14y ago
Great comment, appreciate the feedback. We'll keep that in mind and perhaps tweak that statement a bit. We do acknowledge Twilio and respect what they've done so far. Though, we're confident TelAPI's increased set of features are well-suite
37.
by dougiebuckets 14y ago
Hi mingpan, sorry about that. It looks as though a HN moderator changed the headline before I had a chance. Hopefully it's less ambiguous now!
38.
by dougiebuckets 14y ago
Hi everyone, dev evangelist at TelAPI here. If you have questions or thoughts you'd like to share, feel free to let me know - thanks!
39.
Introducing TelAPI(telapi.com)
44 points by dougiebuckets 14y ago|33 comments
40.
by dougiebuckets 14y ago
Full disclosure: I'm a dev evangelist at TelAPI
41.
by dougiebuckets 14y ago
Thanks balbaugh - that's an interesting thought. Definitely something I'll keep in mind. I put this together really quickly today w/ TelAPI and Zapier and was hoping to get some feedback just like that. Thanks!
42.
Happy Hour Share - Crowdsourcing happy hour specials in NYC via SMS and Twitter(happyhourshare.com)
1 points by dougiebuckets 14y ago|0 comments
43.
by dougiebuckets 14y ago
great feedback, really appreciate it! i'm going to increase the delay between messages being sent (hopefully upon doing so, you'll receive them in the right order). thanks again ;)
44.
by dougiebuckets 14y ago
yup. that's the case. it was our first time playing around w/ it. really nice api! i'd encourage you all to check it out ;)
45.
by dougiebuckets 14y ago
thanks everyone, i totally agree. i wish we could use a db for the app that limited the length of descriptions. right now we're using brewerydb, and i agree, some of the descriptions are excessive as you mention
46.
by dougiebuckets 14y ago
it doesn't look like drakes heffe is in the db unfortunately. concerning pacifico, it's in the db but it's not populated with any data. http://www.brewerydb.com/beer/xfQQiO thanks for sharing this!
47.
by dougiebuckets 14y ago
very interesting--appreciate the info. we're aggregating all of this feedback and will update asap. when you're not receiving responses, most of the time it's b/c the db doesn't have the beer (and we're doing a really poor job of handling t
48.
by dougiebuckets 14y ago
sorry, we ran out of requests to the brewerydb api. just upgraded -- should be all set now! give it another whirl ;)
49.
by dougiebuckets 14y ago
hi everyone - myself and another dev built this at a Twilio hackathon over the weekend. would love to get some feedback/suggestions.
50.
Want to learn about that beer in your hand? Send an SMS to learn more.(beertext.us)
39 points by dougiebuckets 14y ago|21 comments