HelpFix a problemContact support

Contact support

Fastest first — search answers most questions in seconds, the in-app assistant handles the rest, and a human is one message away when something's genuinely broken.

Everyone 5 min read

Answer it yourself, fast

Press the search shortcut anywhere in this help centre and type a few words — it's instant and typo-tolerant.

If something's misbehaving, start at the troubleshooting index — it matches what you're seeing (like "nobody can join" or "the board is blank") to step-by-step fixes.

Ask turndaAI

The Ask turndaAI button in the top bar takes a question in your own words — like "why did that person get called first?" — and answers from this help centre only, with a link to the full page.

It's private, and it knows the page you're on.
It never makes things up. If the answer isn't written here, it says so.

Reach a human

Two ways in	What happens
Report issue	On the Queue, select the visitor something went wrong for. Describe what happened and press Send to support — it bundles that visitor's full queue journey with your message, so support can see exactly where it broke. You can also press Download journey (PDF) for your own records.
Ask turndaAI → Report an issue	For anything else. You don't have to explain where you were or what you're using — it attaches the page, the line, the version and the last thing that failed automatically. Tick Include a picture of this screen — usually the fastest way for us to see the problem.

The other tickbox Tick This is blocking me right now if it's stopping you serving people — it's treated as urgent.

Why it's no longer an email A manager mid-shift doesn't stop to write an email, so problems went unreported. Reporting from inside the app takes one press and carries detail an email never would.

Every report becomes a conversation you can follow. Our reply lands on your Support page — Your reports lists everything you've reported and every answer — and the bell in the top bar tells you when there's a new one.
You can add to a conversation later — "it happened again this morning at 9am" — and a closed one reopens simply by reporting the problem again.
Phone numbers and email addresses are stripped from the technical details before they reach us. A screenshot is the one exception — it shows whatever is on your screen, so glance at it before you tick the box.

If the app itself hits an error The error page shows a reference code (like ERR-3F2A9C71) and a Report this button — customers never see it.

Pressing it reports the problem the same way as the other two, straight to your Support page, with the code attached automatically.
If that can't be sent (say you've just lost your connection), it falls back to opening your email program instead — never a button that does nothing.

What the report asks you

The report box is short on purpose. You are not expected to describe a fault — "I tapped Call next and nothing happened" is a perfect report. Everything technical is collected for you.

What you'll see	What it means
"You were on the Queue page for Boon Keng. What went wrong?"	The question is already filled in with where you are. If the app doesn't know which branch, it just names the page; if it knows neither, it asks plainly what went wrong. You only supply the part only you know.
This is blocking me right now	One tick, not a list of priorities. Tick it if you can't serve people until it's fixed — it's marked on the report and shown when you open the conversation later.
Include a picture of this screen	On unless you turn it off. The picture is taken the moment you press the button, not when you send, so it shows the screen as it was when you noticed the problem.

One line about privacy, above the button Phone numbers and email addresses are stripped from the technical details. The picture is the exception — it shows whatever is on your screen, guest names included, so glance at it before you leave the box ticked.

Press Send report and you get a short confirmation listing what actually arrived — the page and build details, the screenshot if included, and that guest's timeline if you reported from the Queue.

The confirmation offers See your reports, which takes you straight to the conversation.

Your reports, and our replies

Support in the app is where every problem you've reported lives, under the heading Your reports. Newest activity first, and each row tells you the state of it at a glance.

Status	What it means
New reply	We've answered and you haven't read it yet. The row is bold.
With us	It's on our side; nothing for you to do.
Closed	Finished. If the problem comes back, report it again and we pick up where we left off.

Each row also shows how many messages the conversation has and when it last moved, in your shop's own time zone.
Open a row for the whole conversation, oldest first, each message stamped with who wrote it and when. About this report lists when you reported it, when it last moved, and whether you flagged it as blocking.
A very long conversation shows the first message and the most recent ones, and says openly the middle isn't shown.
Add to this conversation at the bottom takes a follow-up, and Send posts it — the button stays off until you've typed something.
If we closed the conversation while you were writing, your words stay in the box so you can copy them and report it again, rather than losing what you wrote.

"We couldn't find that report." You can only open your own reports. If a colleague filed it, it's in their list, not yours — ask them to open it, or report the problem yourself and mention theirs.

Before anything's been reported The page says so and offers the report button right there, so a brand-new shop never lands on an empty screen with nothing to press.