Questions
The things worth knowing before you talk to us. If your question is not here, ask it directly; we answer these ourselves.
A voice and text agent that lives on your website. Visitors talk to it or type, and it answers from your catalogue, your opening hours and your own knowledge base of policies and terms, loaded by us and approved by you. It helps them choose, books the visit, and hands your team the lead with the whole conversation behind it.
A search box returns everything that matches. A chatbot follows a script. The Concierge asks what the visitor is trying to do, explains the trade-off between the options, and narrows to the one that fits, the way a good salesperson does. General knowledge of your field comes from the model; anything particular to your business comes from your systems.
Yes. It goes for the outcome you want first: a visit at a real slot, then a callback, then a registered interest. Every capture is read back and confirmed before it is sent. The moment the visitor confirms, the lead is posted where your team already works, with the transcript, the summary and what they looked at, or it waits for you in the Intentport app.
Leads are posted to Salesforce, HubSpot, Zoho, GoHighLevel, Odoo, SAP, or any system with an API or a webhook, with your fields and your picklists. The connection is set up during the build, so there is nothing for your team to configure. Teams without a CRM read their leads in the Intentport app.
English, Arabic, Russian, German and Dutch, each with its own voice and its own translated prompt. It opens in your site's language and moves to Arabic, Russian, German or Dutch the moment the visitor does. It is not a translation layer: every change to its wording is measured in each language it speaks before it goes live.
Yes, and this is most of what makes it useful. Catalogue, stock, opening hours and appointment slots are checked at the moment of asking, so it never quotes yesterday's price or books a slot that is gone. Anything it writes, a booking or a lead, goes through a single endpoint you control.
Every conversation, text and voice, is stored in an isolated environment in our database and cloud storage. Your conversations are never mixed with another client's. Nothing is deleted automatically: they stay for as long as you want them, and they are deleted when you ask. On request, your conversations are stored in your own database and cloud storage instead.
One script tag on your page, in your colours and with your copy. It is locked to your domain, so only pages on your site can start a conversation and no one can embed your Concierge elsewhere. Adding it is a change to your site's template, not a rebuild of your site.
We build it and we run it. That covers working out what your visitors ask, designing the conversation, connecting the Concierge to your catalogue, your calendar and your CRM, and monitoring and tuning it after launch. You do not need an AI team to work with us.
It depends on how long it is and which models it uses, so we quote per engagement. Every conversation is costed by component (transcription, language model, speech), so you can see what a specific conversation cost rather than only a monthly total.
No. It has a name your customers will use, and asked whether it is a person, it answers plainly that it is an AI. No booking or lead is written without a spoken yes, and a closed location or a past hour is refused with a reason it can read aloud.
Plenty. It is good at the same handful of questions your staff answer every day, and bad at long, unusual or emotionally difficult conversations. It stays on your subject and politely declines the rest, and it will not book a slot it cannot check against real opening hours. We will tell you which of yours are which before you spend anything.
Tell us the two or three questions your visitors ask most and we will tell you honestly whether the Concierge handles them well.
Ask us directly