Why Every Call to Transcon Starts with an Engineer
You have a conveyor down, a line change coming, or a belt that isn’t lasting the way it should. So you call the manufacturer. Someone takes your information, tells you an engineer will get back to you, and you wait.
Then the engineer calls back and asks you to explain the whole thing again.
That gap - between the person who answers and the person who can actually help - is the part we built around.
Who picks up
At Transcon, the person handling your account is an engineer. Not a sales rep with an engineer on speed dial. Someone who has spent years at a drafting table, on a plant floor, or both, and who stays with the job from the first phone call through the build.
Across our customer-facing team, that’s roughly 10 to 25 years of design and shop-floor experience per person. It’s who you get on the first call, not the third.
What that actually changes
It sounds like a small structural detail. On a live problem, it isn’t:
- The diagnosis starts on the first call. When you describe a wear pattern, a jam, or a belt that keeps stretching, the person listening has seen it before and can tell you what usually causes it. You’re not relaying symptoms to someone who will relay them to someone else.
- Drawings get read, not forwarded. Send a print and it goes to someone who can look at it and tell you what won’t clear, what won’t hold up, and what to change.
- Custom quotes don’t wait on an escalation. The person scoping your application is the person who can price it.
- Nothing gets lost in the handoff. The detail you mentioned in passing on the first call is still known by the same person six weeks later.
Why we’re built this way
It comes down to what we make.
A catalog conveyor can be sold from a price book because it’s one of a fixed set of configurations. Pick the model, pick the length, read the number. That works, and for a catalog problem it’s genuinely the right answer.
That isn’t what we build. When the geometry, payload, environment, or footprint don’t match anything standard, the quote is an engineering exercise. There’s no price book to read from, because the thing doesn’t exist until someone designs it.
So there are two options: put people on the front line who can do that work, or add a translation layer between the customer and the people who can. We picked the first one. Every hop between you and the engineer is a chance for something to get lost, and on a custom application the details are the whole job.
What to expect on the first call
Questions. Probably more than you’re used to.
Not a qualifying script - we’re trying to understand what the conveyor is actually doing. Usually that means what’s running on it, how much and how fast, how hot, what’s failing and how it fails, and what’s around it in the plant.
If you have a serial number, a drawing, or a photo, that speeds things up. You don’t need any of it to start. Joey can also handle the quick technical questions any time of day if you just need a fast answer rather than a conversation.
The honest version
This is not the fastest way to get a price.
A vendor with a catalog and a quote desk will turn a number around faster than we will. If your problem fits a catalog, that’s probably the right call, and we’ll tell you so rather than talk you into something you don’t need.
Where this approach earns its keep is the application that doesn’t fit. The custom build. The rebuild of a machine that’s been running for thirty years. The line where the last three belts all failed the same way and nobody has asked why. Those are engineering problems, and they get an engineer from the first minute.
Start the conversation
If you’ve got an application you’re trying to figure out, get in touch and you’ll be talking to someone who can actually work the problem. If it’s a part or a belt you need, the parts request form is the fastest path - send a serial number or a photo and we’ll take it from there.
Either way, no one is going to take a message and pass you along.
