Built for whoever talks to customers.
Whatever website, support workflow, or sales pipeline you run, Elennai answers from your own content and then finishes the job on your site - not a generic model guessing at your business. It works in 100+ languages. Below is what it finishes, and how each kind of team puts it to work.
Four kinds of team. The same three words: get it done.
Every job below ends on a page on your own site. The agent answers the question first, then opens that page and completes the steps on it, stopping at whatever you marked as needing a person.
Ecommerce: returns, order status, address changes
Pre-purchase questions decide whether the basket converts, and post-purchase questions decide whether the customer comes back. Both end in a form on your own storefront.
- Start a returnThe agent answers from your returns policy, opens the returns page, fills in the order number it already has from the conversation, and stops on the confirm button.
- Where is my orderIt answers from your shipping content, and where you have wired a read-only tool against your own order system it can look the order up during the conversation.
- Change a delivery addressA recorded flow on your account pages, with the address step marked sensitive so the customer is the one who confirms the change.
SaaS: onboarding, plan changes, account settings
The questions that arrive in the first week are the ones that decide whether a trial becomes a customer, and almost all of them are a setting somewhere in your product.
- Get a new user set upIt answers from your own documentation and then walks the visitor through the setup screen, filling what it knows and leaving the decisions to them.
- Change plan or account settingsA saved flow on your billing or settings page. Anything that costs money is a sensitive step, so the run stops and asks before it goes further.
- Find the setting that does the thingGrounded answers with the source page attached, so the customer can check the claim, and a guided run when the setting is two screens deep.
Services and agencies: booking, quoting, intake
Every enquiry is the same three questions followed by the same form, and the form is where enquiries go to die.
- Book a callIt answers what you do and who it is for, then opens your booking page and fills in what the visitor already told it.
- Request a quoteThe intake form, completed from the conversation, and left on the submit button so nothing is sent in the visitor's name without them.
- Qualify before a human spends an hourThe conversation, with its sources and whatever the agent completed, lands in your inbox when it hands over.
Internal teams: policy and process lookups
The same policy question, asked by a different colleague, every week. Internal documentation is usually excellent and usually unfindable.
- Answer the policy questionGrounded in your handbook, your runbooks and your Notion, with the section it read attached so nobody has to take it on faith.
- Start the internal processA flow recorded on your own internal tools while you were signed in, which is exactly what the recorder is for.
- Find out what the handbook is missingCoverage certification names the sections it could not answer well, and the questions that exposed them.
Six teams, one platform.
Every segment below uses the same Elennai stack - same retrieval, same tool calling, same admin CRM. The persona, system prompt, and data sources change; the platform underneath stays the same.
Companies that want a bot on their own site.
Your customers shouldn't have to dig through a help center to find the one paragraph that answers their question.
Drop a script tag on your marketing site, support portal, or knowledge base and the bot answers from documents you control. No iframe scaffolding, no off-platform widget that redirects users away. Source attribution on every answer means visitors can verify the bot's claim against the underlying doc.
ExampleA B2B SaaS marketing site embeds the widget on its docs subdomain. Visitors ask 'does it support SAML?' and get the answer with a link to the section that confirms it.
Founders who need a bot live this week.
You don't have a quarter to spend on a support-agent project. You have an afternoon.
Sign up, upload your docs, and ship the embed snippet the same day. The permanent Free tier covers solo builders and beta-stage products; upgrading to a paid plan is a click in the dashboard when traffic justifies it. No procurement cycle to enable basic features.
ExampleA two-founder seed-stage startup launches its landing page Monday morning and has a docs-trained bot answering pricing and onboarding questions on the site by Monday afternoon.
Teams with thousands of pages of documentation.
When the doc corpus is large, retrieval accuracy is what separates a useful bot from an embarrassing one.
Smart search handles both kinds of questions out of the box - exact wording like "order #1234" and fuzzy phrasing like "my package hasn't arrived." Every answer cites the source so your team can spot-check what the bot is reading before customers see it.
ExampleA 200-person company with a decade of internal runbooks in Notion connects the OAuth integration, picks the relevant spaces, and gets a bot that answers from the live corpus and resyncs on every edit.
A sales agent, not just an answer bot.
Elennai is built for the top of the funnel, not just the deflection of inbound tickets.
Configure the bot's persona and system prompt to qualify leads, answer product questions in depth, and route serious buyers to a human. Tool calling can post lead data to your CRM the moment intent is clear, so reps follow up on warm conversations instead of cold form submissions.
ExampleAn enterprise software vendor puts the bot on its pricing page. The bot answers feature questions, asks about team size and use case, and books a demo with the AE the moment a fit is detected.
Deflect Tier-1 tickets without flattening the experience.
Most support tickets are the same five questions answered slightly differently every time.
Train the bot on your existing help center, runbooks, and FAQs. It gives the same answer every time, with the same tone, citing the article the user could have read themselves. Conversations that escalate are visible in the admin chat CRM, so CSMs can follow up with full context instead of guessing what the user already tried.
ExampleA B2B platform's support team feeds in the existing help center plus a curated FAQ. The bot handles password resets, billing questions, and integration setup; only edge cases reach the human queue.
Product Q&A, sizing, shipping, and returns - in one place.
Pre-purchase questions abandoned on a product page are revenue you never see.
Embed the widget on product detail pages and feed the bot your catalogue, sizing charts, shipping policies, and returns terms. Shoppers ask 'does this run small?' or 'can I return after 30 days?' and get an immediate, accurate answer without leaving the page.
ExampleA Shopify-based fashion shop with 2,000 SKUs uploads its size guide and policy docs. The bot answers fit and return questions on every product page, with a fallback to a human when a question falls outside the catalogue.
B2B and B2C - same platform, different persona.
Elennai doesn't care whether your customers are procurement teams or shoppers. Change the system prompt, change the tone, and the same retrieval grounds every answer in your own documents.
B2B
Long sales cycles, complex docs, internal stakeholders to convince. The bot speaks the language of your own documentation and gives reps a tireless first-line responder that never goes off-message.
B2C
High volume, short questions, low patience. The agent answers at 3am with the same accuracy as during business hours, never tells one shopper something different from the next, and finishes the return rather than linking to the policy.
What every team gets out of the box.
Included on every plan
- A bot trained on documents you control - no shared corpus, no cross-tenant leakage
- Source attribution on every answer so the team can audit what the bot read
- Embed widget, REST API, and backoffice chat tester from day one
- Per-bot persona and system prompt - the same platform speaks differently to different audiences
- Admin CRM over every conversation across every channel
- EU data residency and encryption at rest - your data is hosted in the EU and GDPR-ready, wherever your team works. See the security page
Pick a use case. Ship the bot.
Permanent Free tier for solo builders and small projects. Paid plans start the moment your traffic justifies it.