Toast Tables - Smart Algorith

[Sdaniel]

Hi everyone,

Two of our locations recently switched to using the smart algorithm wait time estimator and followed the recommended adjustments for this transition. We also toggled on Allow guests to join online if there is no wait.

However, we encountered a couple of issues:

1. When guests joined the waitlist online via the waitlist link or Google, the wait time displayed as 0 minutes, despite there being parties already waiting.

2. On the iPad, once a guest joined the list, we saw a negative (-1) quote time or 0.

Since this is a new feature for us, we suspect there might be something we overlooked during the switch to the smart algorithm. We switched back to the manual wait time estimator, and the quote times returned to more accurate estimates.

Has anyone experienced similar issues, or do you have any suggestions for resolving this?

I appreciate any insight! 🙂

[rcmck]

I've never used it as one of the main requirements for it to work properly was putting every table in regardless of wait time which is not feasible for me. You said you followed all the recommendations so I assume you are already doing that? 

[Sdaniel]

Hi! Yes, we are putting in every table regardless of wait times. Or at least that is what is expected of managers, but it's possible they are not doing that. I opened a case, and the agent mentioned the next update is supposed to fix smart algorithm syncing, so it seems like smart algorithm just isn't the best feature to use at this time, at least until updates are made. 

[Kirsten_H]

Acknowledging the issues you're having with smart quote...wondering if the time estimates are shown to your hosts for walk-ins, too, or if the quote is strictly for guests looking to add to the list online?  We don't do online waitlist, but would love a more accurate wait quote in house.

Thanks!

[Sdaniel]

Hi!

Yes, when on smart algorithm, it shows 0 minutes for the hosts as well. I was told the issue was fixed with the last update, however over the weekend we had the same issue again, and so we switched back to manual estimator for more accurate quote times.