Tomato or Tomahto? How Next Caller uses kimono to add pronunciation to caller ID

Next Caller provides Advanced Caller ID™ to businesses. Across industries, inefficient exchanges between sales/support reps and customers cost $14B annually. With the Next Caller API, unknown inbound phone numbers get matched with relevant background data for the caller, giving reps near-instant access to all relevant data on a customer.

Screen Shot 2015-03-06 at 9.26.30 AM

Although this adds tremendous value to any customer-facing business, Next Caller did not stop there. They looked to the edges, for truly distinctive customer support and they learned that “the details” matter. One step here is correctly pronouncing the caller’s name. Like any startup, engineering time is at a premium, and feature prioritization looks more like triage. Pronunciation data would have to remain on the shelf for another few quarters or longer until the team had bandwidth to build out a solution.

With kimono, one of Next Caller’s engineers set up a REST API for a massive pronunciation dataset within hours and set up a working prototype within a weekend. Using kimono, Next Caller was able to plan and execute this feature within a single development sprint.


“Kimono saved us days of programming and let us deliver a feature to users 2 quarters faster than we would have been able to otherwise” – Gianni Martire, CEO, Next Caller

One thought on “Tomato or Tomahto? How Next Caller uses kimono to add pronunciation to caller ID

Comments are closed.