Integration · Reads its emails
Tock automated.
Notifications read; reservations confirmed by the team. Built for restaurants, working inside Tock rather than around it.
Reads its emails
We read the notification emails it already sends, parse them the second they land, and act on them. Nothing to install on the platform side.
One enquiry, start to finish
- Trigger. A table request by phone, WhatsApp or web arrives.
- Reply in seconds. The workflow answers in your tone, asks the qualifying questions, offers real times.
- Written back to Tock. The table booked, the reminder sent and the review asked for, logged in Tock so your team sees exactly what happened.
- Handoff when it matters. Anything unusual goes to a person with the full context, not a cold transfer.
Priced one at a time
Before you ask
Do we have to change how we use Tock?
No. Your team keeps working in Tock as they do now. The workflow reads and writes the same records, in the background.
What if Tock changes its API or pricing?
The workflow is yours to keep and we maintain it under the monthly running fee. If the platform changes, we adapt the connection; your process doesn't change.
Where does the data go?
Into your own accounts. Nothing is copied to a third-party AI service beyond the message being answered, and we publish exactly what is sent on our security page.
Next stepTwenty minutes on the phone. Then a straight answer.
Tell us what you keep doing by hand. We'll tell you which workflow pays back first, what it costs, and whether it's worth doing at all. If it isn't, we say so.