FOR UCO COLLECTION
AI phone answering for used cooking oil collection.
A kitchen manager notices the drum is full at nine at night, after service. That is when he calls. Your drivers are done, your office closed at five, and the call goes to voicemail — or to whoever else he tries next.
Your phone runs on the kitchen’s clock, not yours.
Restaurants call when the line goes quiet. Collection runs on business hours. The gap between those two is where pickups get lost.
The full-drum call
Site, address, container type, how full, how urgent. Captured properly the first time, so nobody has to ring the kitchen back the next morning to ask what they already said.
The rate question
What you are paying per gallon or per pound this week. Answered from the rate you supplied, stated with when it was set, and withheld once it is stale.
The new account
A restaurant that wants a container and a schedule. The agent takes the site details and hands a qualified enquiry to whoever signs accounts — it does not agree terms.
The service problem
A missed collection, an overflowing bin, a leaking container. You mark these as escalate-immediately and it moves them to a person instead of logging them.
What it will not commit you to.
A route is a physical promise. An agent that hands one out lightly has cost you a truck movement, not a phone call.
- No invented arrival times. It does not promise a truck on a day or in a window unless that is a rule you gave it. Otherwise it captures the request and says a person will confirm.
- No stale rates. Every time-sensitive number you supply carries the time it was written down and how long it stays good for.
- No contract terms. Pricing for a new account, exclusivity, container supply — those reach a person. It gathers the detail so that person starts the call already knowing the site.
Start with the hours you already cannot cover.
Evenings and weekends are where a UCO operation loses calls, and they are also the safest place to test something new: nothing about your daytime line changes. That is what a 14-day pilot is — overflow and after-hours only, on your own rules. The after-hours page walks through the same argument in a yard’s words, and the PhoneOps AI homepage has the live demo number.
STRAIGHT ANSWERS
Questions yards ask first.
- Can it schedule a pickup?
- It captures the request in full — site name, address, contact, container type and how full it is — and passes that to whoever builds the route. Where a booking rule is simple enough to state plainly, you can let it confirm inside that rule; anything outside it goes to a person.
- Can it quote what we pay for oil?
- Only from the rates you supply, and only while they are current. A rate you give it is stated with when it was set, and once it is past the window you defined the agent says so and offers a callback rather than reading out an old number.
- What happens on a call from outside our service area?
- You supply the area you cover and it answers accordingly, then takes the caller's details rather than committing you to a route you do not run.
- Most of our calls come in after the kitchens close.
- That is the case a pilot is easiest to justify on. After-hours coverage is the safest place to start, and it does not require changing how anyone reaches you during the day.
Don’t take our word for it. Call it.
The demo line is configured as one fictional scrap yard. Ask it a price, then ask it something it should not answer and listen to what it does instead.