Dev (@otherdev) header
Dev (@otherdev) profile picture

CIO for ReplyCX and TechAlpha Group. Family, Cooking and being fit are my other passions.

Orlando, FL
Joined December 2009
Photo by Dev (@otherdev)Photo by Dev (@otherdev)Photo by Dev (@otherdev)Photo by Dev (@otherdev)Photo by Dev (@otherdev)Photo by Dev (@otherdev)Photo by Dev (@otherdev)Photo by Dev (@otherdev)Photo by Dev (@otherdev)Photo by Dev (@otherdev)
When was the last time one of your customers had to explain themselves twice in the same week. I'd like to hear what you found.
1
3
What if the question isn't which channel to add next. What if it's whether any agent on your team can see the last three things a customer said, regardless of where they said it.
1
3
Most mid-market teams I work with are data rich and context poor. They've invested in collection. They haven't invested in activation. The customer feels invisible while being fully logged.
1
5
Knowing and connecting are two different operations. Knowing is storage. Connecting is making the right piece of that storage show up in the moment an agent needs it.
1
2
I used to call this a channel problem. It isn't. Adding another channel to a stack that doesn't share context just gives the customer a new place to repeat themselves.
1
3
The data exists. Purchase history. Past tickets. Monday's SMS sitting in a database somewhere. None of it shows up when the Friday agent picks up the phone.
1
4
A customer texts me Monday. Emails Wednesday. Calls Friday. Three agents. Three blank screens. She re-explains herself every time.
1
9
You know everything about your customer. They can't tell.
1
14
who in your company owns what your AI agent says today? drop the role, not the name. i want to see how many of us actually have an answer.
2
if you can't fill those three names in right now, the risk is already on the balance sheet. you just haven't been billed yet.
1
2
before you scale, three things need a name on them. who reviews the agent's outputs. who approves changes to its instructions. who answers when a customer is harmed by what it said.
1
what if we treated AI agents the way we treat any other employee talking to customers? training. boundaries. a manager. a record of what was said. none of that is exotic. it's just basic operational discipline.
1
2
the AI shipped fast. the governance never shipped at all. that gap is quiet right now. it stops being quiet the day a screenshot goes public.
1
1
the pattern is always the same. no audit trail. no escalation logic. no defined owner when the agent says something wrong.
1
1
most teams i talk to can't answer that. not because they're careless. because nobody built the structure before they flipped the switch.
1
3
you deployed it. it's handling conversations at scale. if it gives a customer wrong information tomorrow — who in your company is accountable?
1
9
your AI agent is live. nobody owns what it says.
2
1
18
before the next call goes to procurement, ask them. then sit with the silence. what did the answers tell you about the next 18 months?
1
none of these appear on a feature matrix. that's the point. they test whether the vendor has thought about your operation or only their own roadmap.
1
question three. who owns the first 90 days after signature? if the answer is your team, you bought software. if the answer is a real person on their side, you bought a partner. these are different purchases.
1
2