James Ramey’s business begins with an experience almost nobody would choose to repeat. A product is supposed to make life easier. Something goes wrong. Its owner searches for an answer, reads instructions, tries a fix, and eventually asks for help. The question has already consumed part of the day. Then the person on the other end needs the whole story again. The machine may be new. The irritation is old enough to have its own comfortable chair.
Ramey, known professionally as JC, has spent years working on the machinery behind those encounters. He has led DeviceBits, built another business with Refactory, and arrived at a new chapter following Refactory’s acquisition by Capacity. The companies and their vocabulary have changed. The thread worth following is the customer trying to get somewhere.
His interest has a consumer’s starting point. During the early mobile-app years, he noticed the difficulty people had understanding and fixing the products they owned. He included himself in that group, describing himself as an “ultimate consumer.” That is a useful vantage point for an enterprise software founder. It puts the inconvenience in the foreground, before the architecture gets a chance to demand all the attention.
The customer after the sale
DeviceBits was founded in 2015 in Columbus, Ohio. By early 2017, Ramey was making a fairly pointed observation about the way companies spent their effort. Sales and marketing had received attention as customers moved across digital channels. Helping those customers afterward deserved attention too. Winning someone’s business creates a relationship that still has to survive ordinary use.
“Customers are looking for support where they’re spending time,” he said. The places included phones, social networks, websites, and email. A company could choose its preferred support channel. Its customers were already choosing theirs.
DeviceBits’ Academy organized support material, including guides, videos, and FAQs. Support Predict worked with information about interactions to surface relevant help. These names belong to the period, but the practical ambition remains easy to recognize: get a person to an answer that fits the situation.
There is a certain comic imbalance in the conventional customer relationship. Before a purchase, every obstacle invites attention. Afterward, an instruction manual can become a scavenger hunt. Ramey’s emphasis on retention asks companies to keep paying attention after the transaction. A customer who needs help is still a customer, even when the conversation is less flattering than a sales call.
“A user journey is rarely a single step or answer.”
James Ramey, on customer support
The answer is only the beginning
That observation about journeys is the hinge of his work. Finding a sentence that appears to answer a question does not necessarily complete the task. The customer may need to follow an instruction, understand what changed, or reach somebody who can deal with an exception. Each of those steps creates another opportunity to lose the thread.
In his early writing on customer care, Ramey advocated using support materials for both customers and agents. The same body of useful information could help somebody working independently and somebody answering a call. He also wrote about adaptive FAQs and interactive guides as ways to make ordinary problems easier to resolve.
The human handoff mattered. In a December 2017 article about chatbot training, he argued that an agent should be able to step in when the bot could not help, without forcing the customer back to the beginning. A business may call that a workflow. The person waiting for help is more likely to call it remembering.
His account of DeviceBits’ development also contains an instructive twist. Academy was intended to help consumers serve themselves, but employees in call centers were using it too. The company responded with a product for them. Watching who actually used the material helped reveal another job the software could do. The audience had, in effect, supplied part of the brief.
A customer is a better test than a demo
In August 2017, DeviceBits joined the UpRamp Fiterator cohort alongside King & Union, Bansen Labs, and Teltoo. CableLabs had built UpRamp to connect startups with cable operators. Its Fiterator program targeted businesses that already had a product and wanted to establish a fit within the cable, broadband, and wireless market.
The program’s design made the distinction unusually concrete. It ran for three months, and its intended outcomes included commercial deals and reference customers. A polished demonstration could open a conversation. A customer prepared to use the software supplied a different test.
DeviceBits entered UpRamp with three other companies. The program connected working products with industry buyers.
Ramey’s work had identifiable users beyond an accelerator roster. Nex-Tech Wireless introduced DeviceBits’ Academy support materials for its customers. Azumi Mobile announced a partnership using DeviceBits’ Academy and Support Predict products for its customer support community. These were practical settings for the idea: people with mobile devices, questions, and limited enthusiasm for a complicated route to help.
Telecom gives this work a particularly unforgiving stage. The service is part of everyday life, while a support request is usually an interruption to it. A guide must earn the time it takes to read. An agent needs information useful to the person on the line. The product’s real audience has little reason to admire the diagram of the system that delivered the answer.
Leaving room for the person
In 2017, Ramey also made an argument about the people answering those calls. He believed automation of general inquiries could leave room for agents to handle more demanding work. His writing presented AI and live assistance as parts of the same support operation, with agents able to draw on materials that helped customers directly.
He went further, suggesting that the demand for technical expertise could create jobs. That was an argument about a possible outcome, rather than a guarantee. Its place in his story is the emphasis it reveals: better automation should be considered alongside the work that people still need to do.
Ramey explored that distinction in writing about artificial intelligence and the use of technology to augment human intelligence. His interest included software that could act independently and software that supplied people with information to make better decisions. Both belonged in the customer service discussion. Reading that argument alongside his support products gives the career a more specific shape: he was considering who should act, who should have the information, and how the two could work together.
These are useful questions to ask before adding another interface. A company can give its customers more places to speak while leaving its employees with more places to search. The design has to account for both experiences.
This helps explain why the handoff keeps appearing. The person is an intended part of the service. Getting to that person should carry useful information forward. If a customer has completed several steps, making those steps visible gives the agent somewhere sensible to begin.
There is also a question of who learns from the exchange. On a November 2017 podcast appearance, Ramey discussed machine learning, chatbot training, and how bots and people could help each other. The issue extends beyond presenting an answer. Every interaction is an opportunity to discover whether the answer helped.
The mat and the meeting room
Ramey’s public record has a life outside software. He coached youth wrestling at Ronin Training Center from 2011 to 2019 and later served as treasurer of a Central Ohio youth wrestling league. The work included beginners and intermediate wrestlers, a setting where knowing a technique and teaching it are separate responsibilities.
It would be convenient to turn that into a neat explanation of his business career. His own advice about teams is more direct: “Know your swim lane really, really well.” In discussing entrepreneurship, he emphasized the value of different skills and temperaments. Expertise gave a person something useful to contribute, even when personalities did not line up politely.
The remark leaves room for a team with a little friction in it. Agreement is pleasant. Knowing what each person brings is useful. For a founder working on the places where systems and people meet, that is an appropriate concern.
Another company, the same unfinished conversation
In September 2020, DeviceBits announced that it had unified its brand with ResultsCX. Ramey was identified as President of Tech Enabled Services. The SupportPredict offering brought together agent assistance, self-service, and bots, including a transition designed to let an agent continue where a chatbot left off.
Refactory carried the connected-journey concern into another business. Ramey worked with Brian Thibault and Dustin Spies, and his account dates the OCX platform’s inception to 2022. On April 28, 2026, the sale of DevRefactory to Capacity was announced. The platform connected customer interactions across voice, chat, web, and social channels, with services supporting implementation and ongoing improvement.
At the announcement, Ramey described Capacity as a way to extend Refactory’s capabilities to a wider audience. A larger platform offered a new setting for the work. The central problem remained recognizably small: carry the information, keep the conversation moving, help the customer reach the next step.
Seen across these chapters, his career has a kind of persistence that company announcements can obscure. The businesses arrive with new names and wider ambitions. The customer arrives with something that needs doing. Ramey keeps meeting the story at that point, where the demonstration is over and the practical questions begin.
A service that remembers can feel surprisingly considerate. It acknowledges the time somebody has already spent. It lets the next person help. For all the elaborate machinery involved, the experience has a plain, human measure: the customer can continue.