← Duckout

What’s improving

Duckout is being built with real tradies. Here's what's changed, and what we're still working on. Anything we know is still not right is listed at the bottom.

What's changed

Sunday 27 September 2026

A morning when it couldn’t understand answers

Was For part of Thursday morning it could not understand what callers said in reply, so it kept asking the same question. A limit on our side had run out, and nothing warned us.

Now Our own testing no longer uses up what the phones need.

We now hear about it within minutes

Was When the line stopped understanding answers, nothing told us — we only found out from the calls themselves.

Now If it ever happens again, we’re alerted within minutes.

Giving your address the way people actually say it

Was Start with “number”, pause partway through, or leave out the house number, and it could refuse the address, keep only a piece of it, or ask for the whole thing again and again.

Now It takes an address that starts with “number”, keeps all of it when you pause, and when only the house number is missing it asks for just that.

Correcting an address it read back to you

Was If it read your street back wrong and you corrected it — or simply said the street again — it could lose the address or mix the old and new streets together.

Now Say “No, it’s Bay Street”, or just repeat the street, and it keeps the address and moves on. The corrected address is the one that reaches you.

Answering “when suits you?”

Was A plain “yeah” to the timing question could end the call or be written down as the time, and a time said before the day could be refused.

Now If “yeah” isn’t an answer it asks again, and it takes a time said before the day.

Your number, read back like a person would

Was Parts of a mobile number could come back sounding like an amount instead of digits, and a leading digit could go missing.

Now It reads your number back digit by digit, starting from the very first.

A number given in parts is added up

Was Read out the first few digits, pause, then give the rest, and it asked you to start again from the beginning.

Now It puts the parts together and reads the whole number back for you to check. This was fixed a little while ago — our page hadn’t caught up.

It hangs up once it has said goodbye

Was When it had finished, it said goodbye and then sat on the open line until you hung up yourself.

Now It ends the call itself once it has said goodbye. This was also fixed a little while ago — our page hadn’t caught up.

It tells you it’s taking the details down

Was After you explained what was wrong there could be a silence long enough to wonder whether the line had dropped.

Now It lets you know it’s taking the details down while it works on what you said.

It keeps the caller’s doubt

Was If a caller said “I think” about what was wrong, the doubt disappeared: it read the problem back as certain, and your job page showed it as fact.

Now It keeps the “I think” when it reads the problem back, and your job page notes that the caller wasn’t sure.

Hear the call on your job page

Was Pressing play on a job’s recording didn’t play anything.

Now Open the job from your text and tap Hear the call to play the whole call. Only your link has it — your customer’s never does.

Tell a customer you’ll call them back

Was There was no way to promise a customer a call back, or to be reminded to make it.

Now Tap I will call you back on a job and pick when. Your customer gets a text saying you’ll ring, and we remind you when the time comes.

Your text shows the whole suburb

Was When the map couldn’t confirm an address, the suggestion in your text could stop halfway through a word.

Now You get the map’s suggestion in full, or a line telling you to check the job page.

An emergency text that could go missing

Was If a call became an emergency after its ordinary job text had already gone out, the emergency text to you could be dropped.

Now You get the emergency text as well.

Thursday 17 September 2026

A caller's “umms” no longer end up in your text

Was Whatever the caller said was passed through fairly raw, so their “umms” and false starts could end up in your message. It also read their own words straight back at them, so a problem they had described as theirs came back sounding like ours.

Now The tidying happens once, where the job is written down, so what the caller hears, what you read and what is on the job page all say the same thing. What they were unsure about stays unsure — if they said something was “sort of” wrong, it still says “sort of”.

Wednesday 9 September 2026

It stops asking what's wrong when you've already told it

Was Say the problem in your first breath and it could still ask for it again a few questions later, as though it had not been listening.

Now It says back what it heard before it asks the next thing — “Got it, the hot water's stopped” — so the caller knows it was listening the first time.

Monday 7 September 2026

A failed text now tells you what to do, not a supplier's error code

Was If a text to a customer didn't get through, the message we sent you included a supplier's error code. It told you nothing you could act on, and it read like something had gone badly wrong at our end.

Now You're told plainly that the customer didn't get their text and to give them a ring. The technical detail goes to us, where someone can actually use it.

Sunday 6 September 2026

It tells you when it cannot place an address

Was It wrote down whatever it thought it heard, and a job could arrive at an address that doesn't exist.

Now It looks the address up while you're still on the phone. When it can't find a match it says so out loud instead of pretending, and the job is flagged for checking.

It can answer “what does it cost to come out?”

Was With no call-out price loaded it dodged the question — the fastest way to lose someone who is ready to book.

Now A business can have its call-out price loaded, and the assistant answers plainly instead of deflecting.

A call that has gone quiet now ends by itself

Was If nobody was speaking, the line just sat there open.

Now A call that has gone quiet now ends by itself, instead of staying open.

What we know about and are working on

These are things we have seen and captured. They are not being brushed aside.

There can be a pause after you answer

After each answer there can be a short silence before it replies — long enough to notice. We know about it and we’re working on it.

It can mishear what the problem is

It can mishear the caller’s first description of what’s wrong, and the wrong description then goes into your text and the customer’s. We’ve seen it on a test call and it’s captured.

It can mishear a street name and still read it back to you

It heard "Oak Plains" when the caller said "Oak Place". It knew it couldn't find that street and said so, but it still read the wrong name back. We're working on it.

Correcting an address with “No, wait” can lose it

If it reads an address back and you answer “No, wait, it’s Bay Street”, the job can end up with no address. Saying “No, it’s Bay Street” works. We’re on it.

It can ask for the time before you’ve confirmed the address

When it checks an address with you, it can ask you to confirm it and then ask when suits you in the same breath, before you’ve had a chance to answer.

It can stop mid-sentence, or talk over you

The assistant can stop part-way through a sentence, or start talking while you're still going — which makes a caller think the line has dropped, or start again from the top.

It doesn’t ask follow-up questions about the problem yet

It takes down what’s wrong, but doesn’t yet ask the questions a good receptionist would to get the full picture. That’s what we’re building now.