Collecting enquiries

Your assistant can take details from a conversation and save them for you: a catering enquiry, a trial class sign-up, a callback request, an order.

Setting it up

Tell the builder what you want to collect and what you need to know. It will ask for:

• A title in your words — “Catering enquiries”, “Trial class sign-ups”. This is the heading the list gets, so name it the way you would say it out loud.
• The details to ask for — name, phone, date, how many people, and so on. Up to twelve.
• Which of them are required, and which your assistant should accept a conversation without.

How it behaves

Your assistant asks for the details in the flow of the conversation rather than presenting a form, confirms them back to the person, and only then saves them. It saves once per request — it will not file the same enquiry three times because someone rephrased it.

In the preview it does not save anything, and it says so, so your own testing never fills your real list with invented bookings.

Finding them again

Everything collected is in the Collected tab of your assistant. Each row shows what was collected, where the conversation happened and when. You can download the whole list as a spreadsheet, and the columns cover every detail ever collected — so rows from before you added a question still line up with rows from after.

The tab shows the most recent 1,000.

Knowing about it

When your assistant saves something, you get a notification. It tells you that something was saved and where to look — it never carries what the person wrote or the details themselves, so the notification is safe to read over someone’s shoulder.

Next: Your conversations.