ask deep >_ console

Conversations per day · resolved (green) vs refused

Most asked

Weekly digest · emailed to the host every Monday 09:00

Suggested questions · live on the widget

Bookings made in the chat · lead score from the pre-call brief (open a row for the full brief)

What the lead score learned from your call outcomes

Left an email, no call booked · scored with the same rules

Drafted answers · approve one to teach the assistant, and the people who asked get the answer by email

Questions the assistant could not answer

Add the missing information to the site, or write a custom answer for it.

Answers marked "not helpful"

whenwherenetworkchannelcame fromlanding pagevisitormsgsleadsip

Guidance for the assistant (applies within the fixed rules: cite only, no outside knowledge, anonymity)

Add a custom answer · fires when a visitor's question is close to yours (no model involved)

questionanswerlinkhitson

Variables you can use in any subject or body

{brand} comes from the brand map below: the first keyword found in the call type's name wins, otherwise the default brand. {host_url} is the host's private booking page: filled in host emails only, empty in visitor emails. Empty fields fall back to the built-in text. Previews on the right use a sample booking and update as you type.

Brand

Host brief (to {host_email})

Visitor confirmation after a booking step

Visitor acknowledgement after asking for a human

Visitor confirmation after booking in the chat (carries the .ics invite)

Host "New booking" after a booking in the chat

Visitor reminder when a Zoom hand-off is still unconfirmed after 24 h

Visitor email after moving a call (chat or manage link)

Visitor email after cancelling a call

Visitor reminder the day before the call

Visitor email with the answer to a question the assistant couldn't answer (after you approve a drafted answer)

Preview · host brief

Preview · visitor booking

Preview · visitor hand-over

Preview · visitor reminder

Preview · visitor booking confirmation (chat)

Preview · visitor call moved

Preview · visitor call cancelled

Preview · visitor day-before reminder

Preview · host new booking (chat)

Preview · visitor answer to their question

Proactive outreach · the greeting bubble speaks up when a rule matches what the visitor is doing

Rules are checked in priority order (lowest number first) when a page loads, and again when a time-on-page or scroll threshold a rule waits for is reached. One rule bubble per page view; a visitor who closes a rule bubble or opens the chat is left alone for the rest of the visit. Each rule fires at most once per cooldown per device. Counts are for the period selected above.

Visitor context · returning visitors who never chatted

A browser is recognised by its device id only, never by IP. The IP only looks up the organisation or country of the current network; it is not stored. A company is named only after two visits from its network, or once you approve it below. Nothing happens for GPC/DNT browsers or (by default) EU/UK visitors.

on#rulewhensaysshownopenedchattedbooked

Add a rule

When

Then say

Variables: {first_name} {booking} {schedule} {topic} {visits} {page_title} {company} {industry} {company_line} {country}. Empty values disappear cleanly. A rule using {company} or {country} only fires when it is known; quick replies cannot use them, and such a rule must not say how we know.

Try it · which rule would fire for this visitor? (nothing is recorded; cooldowns ignored)

Recent firings

Organisations visiting · the networks your visitors came from (host-only: visitors never see this list)

Devices, visits and pages of browsers whose last organisation network was this one, and what its pop-up did. A company network is named in pop-ups after two visits; universities, government and unknown networks wait here as candidates until you approve them. An IP guess can be wrong (guest wifi, partners' offices): switch any organisation off.