Summary
One row per conversation with what the caller wanted, so you can see the day at a glance instead of opening calls one by one.
Activity → Summary turns each conversation into a single row: who called, what they wanted, and the details the assistant collected. It is the page to open when you want the shape of the day rather than a specific call.
Stat cards across the top count the rows below them, so a filter tells you both which conversations matched and how many.
Request types
Section titled “Request types”Each row is classified by what the caller was after:
| Type | What it means |
|---|---|
| Enquiry | A question, with no booking attached. |
| Single booking | An ordinary reservation. |
| Group booking | A booking for a group. |
| Long stay | A stay long enough to be handled differently. |
| Event | An event enquiry. |
| Spa | A spa booking or enquiry. |
| Golf | A golf booking or enquiry. |
| Day pass | A day-pass booking or enquiry. |
Two markers sit on top of the type:
- Urgent — the conversation needs somebody to act on it.
- Converted — the enquiry turned into a booking.
What each row holds
Section titled “What each row holds”Not every field applies to every request type — an enquiry about opening hours has no check-out date — but the ones that were collected are on the row:
- Who: client name, contact number, and the language they spoke.
- When: date and time of the request; for stays, check-in date, check-out date and number of nights.
- How many: number of people, adults, guests.
- Where: the venue, and the accommodation number where one applies.
- What they asked: the question itself, for enquiries.
- Follow-up: whether a WhatsApp message was sent back to the guest.
Related
Section titled “Related”- Calls — the recording and transcript behind any row.
- Requests — event and large-group enquiries you accept or reject, rather than only read.
- Inquiry Log — how to configure what the assistant asks before it fills these rows in.