dtolb · October 11, 2016 14:52
diff --git a/noreen b/noreen
 ## Regarding API ease of use, could you elaborate on where you are vs. Twilio or other competitors?

 ### Where Bandwidth is easier:
 * More advanced use cases where the customer wants to control each and every aspect of their calls. Bandwidth's REST API implementation trades off immediate ease-of-use and rewards the more advanced user by exposing each event to the user.
 * Example: Creating a round-robin call flow where an incoming call can try to connect multiple phones (one at a time) then record the call whenever the call is bridged. Then when the call is over, ask the incoming caller to take a brief survey.
 * Bandwidth excels at number portability compared to competitors. At this point, porting requires a Dashboard and App platform account, but even still is way ahead of the competition.
 * Example: OTT app wants to allow users to port numbers to/from their service. Via Bandwidth, this can all be done via the API with few customer-support tickets.
 * Bandwidth is more likely to partner with enterprise customers to fill any missing functionality gap for their specific use case.


 ### Where Bandwidth struggles:
 * Simple use cases where the customer doesn't need to completely control each and every aspect of the call flow.
 * Example: Creating a simple call-forward that can timeout and goto a voicemail system.
 * IVR Creation. Twilio has a tool 'task router' that abstracts even more away from the call flow and focuses more on tasks. Nexmo recently released a tool 'nexmo-cli' that builds small apps directly from the command line
 * Various SDK usage: Twilio benefits from being extremely well known and having lots of eyes and programmers helping develop their SDKs. Bandwidth has a few SDKs that have been reworked to be more user friendly, but not nearly as many as Twilio.
 * Getting started guides. Twilio has really focused on each level of documentation: Reference, Guides, Tutorials. Bandwidth has a renewed focus on creating developer focused content that address our customer needs.

 ### Overall
 If you strip all the associated content away and focus directly on the API. Bandwidth and Twilio and Competitor are all about the same in terms of use. However, other competitors have more content explaining how to use their API to accomplish specific tasks. This content directly reduces perceived ease of use as examples are right in the developers face.
	## Regarding API ease of use, could you elaborate on where you are vs. Twilio or other competitors?

	### Where Bandwidth is easier:
	* More advanced use cases where the customer wants to control each and every aspect of their calls. Bandwidth's REST API implementation trades off immediate ease-of-use and rewards the more advanced user by exposing each event to the user.
	* Example: Creating a round-robin call flow where an incoming call can try to connect multiple phones (one at a time) then record the call whenever the call is bridged. Then when the call is over, ask the incoming caller to take a brief survey.
	* Bandwidth excels at number portability compared to competitors. At this point, porting requires a Dashboard and App platform account, but even still is way ahead of the competition.
	* Example: OTT app wants to allow users to port numbers to/from their service. Via Bandwidth, this can all be done via the API with few customer-support tickets.
	* Bandwidth is more likely to partner with enterprise customers to fill any missing functionality gap for their specific use case.


	### Where Bandwidth struggles:
	* Simple use cases where the customer doesn't need to completely control each and every aspect of the call flow.
	* Example: Creating a simple call-forward that can timeout and goto a voicemail system.
	* IVR Creation. Twilio has a tool 'task router' that abstracts even more away from the call flow and focuses more on tasks. Nexmo recently released a tool 'nexmo-cli' that builds small apps directly from the command line
	* Various SDK usage: Twilio benefits from being extremely well known and having lots of eyes and programmers helping develop their SDKs. Bandwidth has a few SDKs that have been reworked to be more user friendly, but not nearly as many as Twilio.
	* Getting started guides. Twilio has really focused on each level of documentation: Reference, Guides, Tutorials. Bandwidth has a renewed focus on creating developer focused content that address our customer needs.

	### Overall
	If you strip all the associated content away and focus directly on the API. Bandwidth and Twilio and Competitor are all about the same in terms of use. However, other competitors have more content explaining how to use their API to accomplish specific tasks. This content directly reduces perceived ease of use as examples are right in the developers face.
No results found