Adoomi emails your team when a lead is captured, when a conversation needs a human and when the assistant meets a question it cannot answer — and only for the events you switch on. Each alert carries the question, the captured details and the page context, so whoever opens it can act without logging in anywhere.
An alert can go out when a lead is captured, when a conversation needs a human, and when the assistant meets a question your approved content could not answer. You decide which of those email you, so knowing what happened does not cost you a noisy inbox.
The alert carries the customer's question in their own words, the details they chose to give, and the page context around the conversation. Alerts are localised too, arriving in your team's language rather than always in English.
Alerts go to the address or addresses you set. Quote enquiries can land with whoever prices the work, and a sensitive matter can go to a named person rather than a shared inbox the whole office can read.
The email says what happened; what follows is your team's call — a phone call back, a reply, or WhatsApp if the customer asked to carry on there. Adoomi never emails the customer on your behalf.
Point Adoomi at your site so the assistant answers from your own pages, FAQs and approved content. Every Adoomi assistant starts here, and it is those conversations the alerts report on.
Notification preferences are part of the same review: turn on the event types that deserve an email and leave the rest off. The ones you leave off never send.
Set the destination address. One shared inbox works, and so does splitting them: quote enquiries to whoever prices work, sensitive matters to a named person, so the alert arrives with someone who can actually answer it.
Read what the assistant proposes to say and what it asks for before any customer sees it, because you approve the wording. Then add one line to your website. Connecting the site, reviewing and adding that line takes ~10 min in total.
Supplies the enquiry the alert carries: contact details, what the customer needs and the context around it. Limit: an alert can only report what the visitor chose to share, so a partial enquiry arrives partial and a visitor who leaves without giving details produces no alert at all.
Handles the customer side of the same moment, carrying the original question and captured details into WhatsApp while the alert tells your team it happened. Limit: the two run separately — an alert does not move anyone into WhatsApp, and replying to the email does not reach the customer.
Sends the same events into the tools your team already works in, for teams that would rather not run follow-up from an inbox. Limit: a webhook needs an endpoint on your side that receives and acts on the event, so email stays the route that works with nothing to build.
CustomerDo you take short-notice house moves? We're out of our flat by the end of next week and still need a quote.
AdoomiShort-notice moves are covered on our moves page. The price comes from a survey the office does rather than from me, so I can't put a figure on it, but I can put this in front of the person who prices moves so it's waiting for them in the morning. What's your name and the best number to reach you?
CustomerDan Okoro. Mobile is best, evenings are easiest. Two-bed flat, second floor, no lift, and it has to be done by the end of next week.
Your teamIn the quotes inbox that evening: Dan Okoro, mobile number, short-notice house move, upstairs flat with no lift, needed by the end of next week, asked from the moves page. Enough to ring back with a price.
The alert went to the address this business set for quote enquiries, carrying the question, the details Dan chose to give and the page he asked from. The assistant quoted nothing, because pricing is the office's job. The owner read the alert over breakfast and rang Dan back, without logging in to know the lead existed.
There are no assignments, statuses, queues or SLAs behind an alert, and nothing marks one as handled. Two people can act on the same enquiry, or each can assume the other did.
Delivery ends at an inbox your team already checks. Nothing chases a team that does not open it and nothing escalates an alert that is ignored. If you need events pushed into a tool your team lives in, use webhooks instead.
Adoomi sends no marketing email, no nurture sequence and no automated follow-up to the person who asked. Whatever the customer hears next comes from one of your people.
Hitting reply puts your message into your team's normal email flow, not back into the conversation the customer had. The visitor has probably closed the chat window, so reach them the way they asked to be reached.
The alert reports only what the visitor chose to share — nothing is looked up or added from anywhere else.
An unread alert never loses the lead — the enquiry is captured and stays in your dashboard regardless. And the customer details inside it stay EU-hosted, with GDPR export and deletion built in.
Alerts can fire on a newly captured lead, a conversation that needs a human, and a question the assistant could not answer from your content. You choose which of those email you: notification preferences are part of the same review, so the ones you leave off never send.
Routing is by address. You set where alerts land, so quote enquiries can reach whoever prices work and sensitive matters can reach a named person instead of a shared inbox. Adoomi does not assign an owner or track who picked it up: the routing is the address, not a workflow.
Each alert carries the customer's question in their own words, the details they gave and the page context around the conversation, so a teammate can act from the email without opening a dashboard. Alerts are localised, arriving in your team's language rather than always in English.
Alerts go to your team only. Adoomi sends no marketing email, no nurture sequence and no automated follow-up to the customer. Replying to an alert goes into your normal email flow rather than back into the chat window, so the customer's next contact comes from a person.
Webhooks carry the same events into the tools your team already uses, which matters because an unread alert is an unread lead. A webhook needs an endpoint on your side that receives and acts on the event, so email remains the option that works with nothing to build.
Email alerts are part of the assistant, with no separate charge. Plans are Free at £0 for 50 message credits a month, Local £8 for 200, Growth £20 for 500 and Scale £75 for 4,000. One credit is one AI answer, so credits are counted on the answering, not on the notifying.
Adoomi starts with your public business knowledge and routes the moments that need a person to your team.