The AI concierge for your SaaS product

To add an AI assistant to your SaaS app, let AskMyWebsite AI scan your product's pages. Then paste one script tag into your app shell's index.html or base template, right before the closing body tag - no plugin and no code changes beyond that single line. Because the widget detects client-side route changes, it keeps guiding users correctly as they navigate between screens in a React, Vue or Angular dashboard.

Add it to your app in three steps

  1. Let AskMyWebsite AI scan your site, so the AI concierge knows your product's pages, features and flows.
  2. Paste the tag in your app shell (the index.html of your SPA, or your base template) before the closing body tag:
    <script src="https://cdn.askmywebsiteai.com/sdk.js" data-app-id="YOUR_APP_ID" defer></script>
    The app id comes from your dashboard.
  3. Done. The assistant answers questions and highlights the exact steps to take, right inside your product.

What your users get

The assistant answers only from your own content and from notes you add yourself, never from the open internet. It reads the visible text of the screen the user is currently on, so answers stay relevant to where they are in your product. When a question needs action, it highlights the exact element to click, step by step, without ever clicking, filling or submitting anything itself. It replies in whatever language the user writes in, and it keeps working across client-side route changes, so a multi-step flow that spans several screens in your dashboard still gets guided correctly.

Built for onboarding, activation and support inside your product

A new user who does not know where to start can simply ask, and the assistant walks them to the right place instead of leaving them to hunt through menus. In-app questions like "where do I change my billing email" or "how do I invite a teammate" get answered and pointed to directly, without a support ticket. Questions your documentation already answers can be deflected the same way, since the assistant reads your product's own pages. For anything not written anywhere, you can add notes yourself, and the assistant will use them alongside the scanned content.

You stay in control of what the assistant can see. You can exclude specific URLs, such as sign-in or password screens, and exclude specific page areas, so the assistant never reads screens or sections you choose to keep off limits. This matters more inside a product than on a marketing site: actions in a SaaS dashboard have consequences, which is why the assistant never clicks, fills or submits anything on the user's behalf. It only highlights the path; the user always acts.

That boundary is worth stating plainly, because it is what makes an assistant acceptable inside a product at all. An assistant that clicks on a user's behalf inherits every permission that user has, and a wrong guess becomes a deleted project, a cancelled subscription or an invitation sent to the wrong address. Highlighting instead of acting keeps the blast radius at zero: the worst case is that the user is pointed at the wrong control and does not press it.

The practical effect on support is straightforward. The tickets a small team spends most of its time on are rarely bug reports; they are people who cannot find something that is already there. Those questions arrive at the moment the user is stuck, on the exact screen where they are stuck, and that is precisely the context the assistant has - the visible text of the screen in front of them, plus everything it scanned from your site and the notes you wrote. Answering there means the question never becomes a ticket, and the user does not have to leave the product and wait.

Notes are where most of the value accumulates over time. Every product has answers that live in a founder's head or in a support inbox rather than on a page: the limits of a beta feature, the reason a plan change takes effect at the end of the period, the workaround for something you have not built yet. Written once as a note, each of those stops being a conversation you have again.

Privacy and GDPR

AskMyWebsite AI is operated in the EU (Spain) with EU hosting (Barcelona). The widget sets no cookies; it uses sessionStorage only after a user opens it, and that storage dies with the browser tab. Conversations are automatically deleted after 90 days, and your content is never used to train AI models. The assistant reads visible page text only and never captures values typed into form fields. See the [Privacy Policy] and the [Data Processing Agreement] for details.

Pricing

AskMyWebsite AI is in private beta and we are onboarding a few websites at a time. Tell us your website address and what you would want the concierge to do, through the [contact page], and we will come back to you with access and pricing.

SaaS questions, answered

Does it work in a single-page app dashboard?

Yes. The widget detects client-side route changes, so guidance keeps working as users navigate between screens in React, Vue or Angular without a full page reload.

Can the assistant take actions for my users, like changing a setting?

No. It highlights the exact element to click, step by step, but it never clicks, fills or submits anything itself. The user always performs the action.

Can I keep it out of certain screens, like sign-in?

Yes. You can exclude specific URLs and specific page areas from the dashboard, and the assistant will never read those screens or sections.

Also see

Get in touch

AskMyWebsite AI is in private beta. Tell us about your site through the [contact page], and we will come back to you with access and pricing. You can also look around from [the homepage].