A lot of AI conversations open the same way. Someone has seen a chat box on another company's site, and they want one too.
We ask a plainer question. What is a person on your team doing by hand, over and over, that a customer never sees?
The answers are rarely glamorous. A coordinator copies names and dates out of a PDF into a form. A front desk answers the same three questions between check-ins. An insurance team reads a policy summary and types the same fields into a comparison sheet. None of that belongs on a product demo. All of it is where the afternoon goes.
When the assistant sits next to that task, people use it. Drop the document in. The fields fill. A person checks the lines that look wrong and moves on. Nobody writes a testimonial the first time it works. They just finish earlier and go back to the work that needed a human.
The chatbot can still live on the site. It can answer office hours and the refund policy. It tends to get a handful of visits, and that is a fine outcome for a side door. It was never the job.
What we learned after the demo wore off
Models change every few months. The habits that make a feature stick have stayed stubbornly ordinary.
- Put it on the screen where the work already happens. A separate AI page gets forgotten by Friday.
- Show the source. If a number came from page two of a PDF, let the person see page two. Trust shows up when they can correct it.
- Leave the last click to a human when the stakes are a booking, a claim, or a care note. Speed helps. A silent wrong answer does not.
- Count the hour it gave back, not the number of prompts. If the team stops opening it after two weeks, it did not help.
We have watched teams turn a tool off without a meeting. They simply go back to the old way, because the old way was only a little slower and a lot more predictable. That is useful feedback. It means the feature was solving a slide, not a Tuesday.
Start from the repeated task
The useful question is small. Which repeated task, if it took half the time, would make this week feel different?
Answer that, and the shape of the feature is usually obvious. A draft beside the form. A search that understands the words your staff actually type. A summary of the thread, sitting above the reply box, with the messy bits still visible.
At North Tech we would rather build that quiet piece well than ship a chat window nobody returns to.