Adoomi connects to your website, WhatsApp, email, Calendly, any webhook endpoint you name and, through Zapier, the thousands of apps in Zapier's own catalogue. There is no native CRM connector, so this page lists each connection with what it does and exactly where it stops.
The chat window is the surface everything else hangs off. It goes on any website or CMS with one line added to the site, answers 24/7 in the customer's own language, and answers only from your approved website, FAQ and policy content.
When a conversation needs a human, the handoff goes somewhere real. Customers who would rather keep typing move to WhatsApp. An email alert reaches your account email, once you switch it on. A Calendly link appears when a call is the obvious next step.
Webhooks post a signed JSON request to an endpoint you choose the moment something happens: a new lead arrives, a handoff is requested. Where nobody wants to write code, the leads list exports as CSV for import into whatever CRM or spreadsheet you already run.
Those same webhook events feed Zapier's Catch Hook, which passes them on to the thousands of apps in Zapier's catalogue: a Slack message, a spreadsheet row, a CRM record. Both routes are documented publicly, so this is checkable rather than a logo wall.
Point Adoomi at your site so the assistant answers from your own pages, FAQs and approved content rather than general knowledge. Every Adoomi assistant starts here, whatever it goes on to connect to.
Nothing routes anywhere until you supply the destination: the WhatsApp number handoffs should land on, or your Calendly account if you want times offered. Email alerts always go to your account email. WhatsApp, Calendly and webhooks are set per assistant, so a support bot and a sales bot can route differently on the same site.
Paste the HTTPS URL that should receive events, either your own endpoint or the Catch Hook URL Zapier generates for you, pick which events it receives, and keep the signing secret so your side can verify each request came from Adoomi. The secret can be rotated later, with the previous one still accepted during the changeover.
Read what the assistant proposes to say, including how it introduces a booking link or offers to move to WhatsApp, before any customer sees it. Then add one line to your website. Connecting the site, reviewing the answers and installing that line takes ~10 min.
Goes live on any website or content management system — WordPress, Shopify, Wix or hand-built alike with one line added to the site, and is the surface every other connection starts from. Limit: this is the only channel the assistant answers on; there is no in-app or social-messaging version of it.
Moves the conversation to your team on a WhatsApp number you configure, carrying the customer's original question and captured details across so nobody restarts from a blank chat. Limit: it is a handoff destination, not WhatsApp automation, and there is no Adoomi bot answering messages inside WhatsApp.
Sends an email to your account address when something happens, such as a new lead or a chat handed to a human. The new-lead email holds no contact details; it points you to the dashboard. The handover email names the bot, the reason and the conversation id. Limit: every alert goes to that one address, and it is a notification, not a ticketing system, with no queues, assignments or reminders behind it.
Shows up to three free times from your connected Calendly at the point in a conversation where a call becomes the obvious next step. Limit: the assistant does not book the meeting; the visitor clicks a time and finishes on Calendly's own page. Calendly sends its invite.
Posts a signed JSON request to any HTTPS endpoint you register, the moment an operator event happens: a new lead, a handoff request and others. Limit: this needs a developer, or a tool that accepts incoming webhooks; the payload shapes and the signature header are published at https://app.adoomi.ai/docs/webhooks so your side can check them first.
Works today through Webhooks by Zapier: you paste the Catch Hook URL Zapier generates in as an Adoomi webhook destination, and your events reach the thousands of apps in Zapier's own catalogue. Limit: this is the generic Catch Hook route documented at https://app.adoomi.ai/docs/zapier, not a one-click native Adoomi listing in Zapier's directory, so you filter by event type inside the Zap.
Downloads the captured leads list as a CSV file that imports into any CRM or spreadsheet you already work in, with no technical help needed. Limit: it is a manual download, so nothing appears in your CRM on its own and nothing edited there flows back to Adoomi.
CustomerDo you handle commercial fit-outs as well as domestic work, and do you cover Leeds?
AdoomiCommercial fit-outs are covered and Leeds sits inside the service area listed on the site. I can't put a figure or a start date on a job like that, so the commercial team should pick this up. Can I take your name and the best email, plus a line about the site itself?
CustomerDan Ellery, and I'll leave my work email. Two retail units, both still trading, so any work has to happen overnight.
AdoomiThanks Dan, the team has your details now. If you'd rather carry on from your phone, I can move us to WhatsApp and they'll pick it up there with everything you've already told me.
Your teamA new-lead email reached the owner's account email, pointing to the lead in the dashboard. The same enquiry, with Dan's details, also landed in their operations tool. The new-lead webhook posted it as JSON to a Zapier Catch Hook, and the Zap raised the task.
Your teamNothing was typed twice. At month end the leads list was exported as CSV and the month's enquiries went into the CRM in one import, because no connector is doing that live.
The assistant answered the coverage question from the business's own content, then refused to guess a price or a start date, which is the answers-only-from-approved-content rule every connection inherits. Everything after that was routing: one enquiry delivered by email, by webhook and eventually by CSV, with no CRM connector anywhere in it.
There is no HubSpot app, no Salesforce app and no connector for any other CRM. Getting leads into a CRM means one of two honest routes: export the leads list as CSV and import it, or point the new-lead webhook at your CRM or at a Zap that creates the record.
Every connection except Calendly runs one way, out of Adoomi. From Calendly, Adoomi reads free times and receives booking notices. Nothing else is read back in. A lead you mark as won in your CRM, a contact you edit or a record you delete there never reaches Adoomi.
Someone has to supply an HTTPS endpoint and handle JSON, or set up a Zap. There is no one-click native Adoomi app in Zapier's directory yet, so a Zapier connection is built from the Catch Hook trigger and an event filter rather than picked off a list.
The customer chooses to continue on WhatsApp, and your team answers there as people. Adoomi does not reply inside WhatsApp, cannot start the conversation from your side, and does not pull WhatsApp threads back into the dashboard.
The AI phone agent is waitlist only and is not something you can switch on today, and there are no social-messaging connectors. The chat window on your website is the one place the assistant answers.
Adoomi connects directly to your website, to WhatsApp as a handoff destination, to email for enquiry alerts, to Calendly for booking links, and to any HTTPS endpoint you register as a webhook. Leads also export as CSV. Everything else is reached through Zapier.
No native CRM connector exists: Adoomi has no HubSpot app and no Salesforce app. Leads reach a CRM two honest ways instead. Export the leads list as CSV and import it, or point the new-lead webhook at Zapier and let a Zap create the record in the CRM you already use.
Zapier works today through the Catch Hook trigger in Webhooks by Zapier: you paste the URL Zapier generates into Adoomi as a webhook destination, then filter by event type inside the Zap. There is no one-click native Adoomi listing in Zapier's app directory.
Webhooks need an HTTPS endpoint and someone comfortable with JSON, or a tool that accepts incoming webhooks such as Zapier. Adoomi sends a signed request your endpoint can verify. The guide at https://app.adoomi.ai/docs/webhooks publishes the payloads, the signature header.
WhatsApp is a handoff destination rather than a channel the assistant answers on: the customer moves there to reach your team, with the original question and captured details carried over. Phone is not available, as the AI phone agent is waitlist only.
Credits are spent on AI answers, not on connections. One credit is one AI answer, whether or not that answer shares a booking link or sets off an alert. Plans are Free at £0 for 50 credits a month, Local £8 for 200, Growth £20 for 500 and Scale £75 for 4,000.
Data held in Adoomi is stored in the EU, with GDPR export and deletion built in and no tracking cookies in the chat window. When you connect a webhook or a Zapier hook, the event data goes to the endpoint you chose — from there its handling is governed by that tool, so pick destinations you trust.
Adoomi starts with your public business knowledge and routes the moments that need a person to your team.