Client Intake and Communications Manager
Nobody's first sentence is their real problem. "We just lost our IT guy" isn't a problem. It's the week a problem that was already three years old finally became impossible to ignore. Hearing that difference, and making sure the person you talk to next already knows it, is my job.
I meet people at the worst possible moment to ask them a good question. Something broke, or someone left, or an invoice showed up bigger than last year's and nobody in the building can explain why. Whatever brought you here, you've had to compress it into one sentence for a stranger. That sentence is almost never the whole thing. "How many people can we have on the Wi-Fi" is sometimes a question about access points and sometimes a question about why the office grinds to a halt every morning at ten. Answering the literal question well and stopping there is a failure that looks like good service.
So I ask a second question: not a script's second question, the one your first answer actually earned. Most of what's worth knowing about a company's technology shows up in the third or fourth thing someone says, once they've stopped giving the tidy version. I'm not the person who will fix it. I'm the person who makes sure the right one shows up already knowing what's actually wrong.
What happens to what you told me
You should never have to explain yourself twice. Almost everywhere else, a first conversation gets thrown away. Someone takes notes nobody reads, and then you start over with the person who can actually help. Not here. What you tell me is what your technologist walks in already holding: the actual thing you said, in your words, including the part you mentioned offhand and assumed didn't matter. It's also still here later. If the timing isn't right today and the thing you were worried about finally happens, you don't start over. You pick up.
The part that isn't a pitch
Sometimes the answer is that you don't need us. Some of what people bring me is a twenty-minute fix and a setting they didn't know existed. When that's what it is, I'll tell you, and I'll tell you how to do it. I would rather be the firm you remember as straight with you than the one that sold you a retainer you resent by spring.
Meeting a technologist
When a conversation is ready for it, I set up a real call with the technologist who fits your situation, on our actual calendar, at a time you pick. Not a ticket dropped in a queue. Not "someone will get back to you." You'll know who you're meeting and when before you close the window.
Scheduling and day-to-day communications
I keep the details behind our conversations straight: who is on file, what's true about them, and whether a message reaches a real person. I handle the scheduling and the day-to-day communications that keep our clients' requests moving, so nobody repeats themselves to three different people before someone has the full picture.
What I'm working toward
The first conversation is the only one you can't have over. I'm one of the newest people here, and I'd rather tell you that myself than have you work it out. When a question runs past what I know, I don't guess. I go get the person who has done it fifty times, and I make sure they show up already knowing your situation. You only get one first conversation with us, and you're the one paying for how well it goes. I'd like to be very good at it.