# Make Asa your own
Source: https://docs.asa.so/get-started/make-asa-your-own
Match Asa's look, voice, and handover behavior to your brand — appearance, responses, guidance, and where escalations go.
Shoppers form an impression of your brand in seconds. How Asa looks and responds either reinforces that impression or breaks it. This guide walks you through both.
Navigate to **Configuration > Appearance** in the sidebar.
![Appearance settings showing avatar, theme, widget position, brand color and assistant name fields]()
| Setting | Description |
| --------------------- | ----------------------------------------------------------------------------------------------------------------------------------------- |
| **Avatar** | Your logo or a recognizable icon. Shown in the chat header and as the widget button on your storefront. |
| **Theme** | Match your storefront — use dark if your store is dark. Consistency reduces friction. |
| **Widget Position** | Bottom right works for most stores. Use bottom left only if a fixed element (cart button, sticky bar) would overlap the widget. |
| **Brand Color** | Primary brand HEX for message bubbles and highlights. Most merchants match their storefront CTA color. |
| **Assistant Name** | How Asa introduces itself — for example, *Ask Nike* or *Zara AI*. |
| **Input Placeholder** | Placeholder text when a shopper starts a new chat — for example, *Find your fit...* or *Ask about ingredients, routines, or products...*. |
Use the preview panel on the right before saving. Click **Save Changes** in the top right to apply.
Navigate to **Configuration > Responses** in the sidebar. Three tabs control how Asa behaves.
![Responses Behaviour tab showing response length, tone of voice, and default language]()
| Setting | Description |
| ---------------------- | ------------------------------------------------------------------------------------------------------------------------------- |
| **Response Length** | How concise or detailed answers are. Preview changes on the right. |
| **Tone of Voice** | Brand personality in replies. If unsure, read three strong product descriptions out loud — that tone is usually the right pick. |
| **Default Language** | Primary customer language. Asa still adapts to the shopper's language in chat; this is the default only. |
| **Proactive Messages** | Helpful prompts while shoppers browse — before they ask. Works well on product pages, cart, and search. |
| **Storefront Events** | Tracking for shopper behavior on your store. Turn this on to power proactive messages and contextual replies. |
![Responses Guidance tab showing Communication Style and other instruction fields]()
Guidance is your brand voice in plain language — not a dropdown. Think of it as the brief you would give a new teammate on day one.
Set tone, vocabulary, and terminology. Be specific — vague instructions produce vague answers.
| Brand type | What to write |
| -------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Fashion and apparel | "Use aspirational but accessible language. Refer to products by their full name. Never use slang. Suggest complementary pieces when recommending." |
| Health and wellness | "Use warm, science-informed language. Avoid medical claims. Recommend consulting a professional for medical conditions. Use ingredient names accurately." |
| Skincare and personal care | "Use clean, ingredient-forward language. Acknowledge concerns with empathy. Never guarantee results — use 'may help' or 'known to support'." |
Tell Asa when to ask a follow-up before answering.
Good examples:
* "When a shopper asks for a routine, ask skin type and primary concern first."
* "When a shopper asks for a size, ask their usual size and preferred brand first."
* "When a shopper asks about supplements, ask their health goal before recommending."
Define what Asa should never handle alone. Asa follows these literally.
Good examples:
* "Hand over when a shopper requests a refund or mentions a damaged product."
* "Escalate if the issue involves an account, payment, or order that cannot be found."
* "Always hand over complaints — never resolve dissatisfaction without a human."
Anything else — for example:
* "Do not discuss competitor products."
* "Add 'Results may vary' when discussing outcomes."
* Products to prioritize or avoid in recommendations.
Each Guidance field has a 1,000 character limit. One clear instruction beats three vague ones.
Under **Human Support Contact**, choose where escalations go:
| Destination | What it does |
| ----------------- | -------------------------------------------------------------------------------------------------- |
| **Email Contact** | Shoppers see your support email in the widget when Asa hands off. |
| **Redirect URL** | Shoppers are sent to your help page or contact form. |
| **Gorgias** | Escalations create tickets in Gorgias. See the [Gorgias integration guide](/integrations/gorgias). |
Set handover before you go live. Those conversations are tagged **Redirected** in **Activity > Conversations**.
Click **Save Changes** in the top right after you connect Gorgias or change the destination.
Use the preview panel on the right before saving. Click **Save Changes** in the top right to apply.
# Get Live in 15 Minutes
Source: https://docs.asa.so/get-started/quickstart
Go from a new account to Asa live on your storefront in about 15 minutes.
Go to [asa.so](https://asa.so) and click **Sign In** in the top right. Create an account with your email and set a password. Complete account verification. When you finish, you land in your Asa dashboard.
Asa answers from what it knows. Go to **Add Content** in the sidebar.
![Add Content screen showing Apps, Files, Websites and Snippet tabs]()
**On Shopify?** Connect it first — it is your most valuable source. Train **products**, **blogs**, **pages**, and **policies**; Shopify keeps them in sync after that.
Connect your store and choose what Asa should learn from.
**Everything else** — use the tabs across the top:
| Tab | What to add |
| ------------ | --------------------------------------------------------------- |
| **Apps** | Shopify, Notion, Google Drive, Judge.me, Yotpo, Klaviyo Reviews |
| **Files** | PDFs, CSVs, Docs — policies, guides, spec sheets |
| **Websites** | Any URL Asa can read and learn from |
| **Snippet** | Paste text directly — short policies or FAQs |
Start with products and policies. They answer most shopper questions. Add the rest after you are live.
After you connect apps or upload content, go to **Manage Content** to watch training status in real time.
Go to **Manage Content** in the sidebar. Wait until every source shows **Trained** before moving on.
![Manage Content screen showing trained sources with green status indicators]()
Click **View content** on any trained row to see what Asa extracted. If something looks wrong, delete the source and retrain.
Go to **Configuration** in the sidebar, then **Appearance** or **Responses**.
Set your avatar, brand color, widget position, assistant name, and other appearance settings. The preview panel on the right updates in real time.
![Appearance settings showing avatar, theme, widget position, brand color and assistant name fields]()
Set your avatar, brand color, and assistant name first. You can refine the rest later.
Under **Responses**, use three tabs:
* **Behaviour** — tone of voice, response length, proactive messages, and storefront event tracking
* **Guidance** — written instructions for how Asa should speak and when to ask follow-ups
* **Handover** — where shoppers go when they need a person (email, redirect URL, or [Gorgias](/integrations/gorgias))
![Responses Behaviour tab showing tone of voice and response length settings]()
For a full walkthrough, see [Make Asa your own](/get-started/make-asa-your-own).
Click **Save Changes** in the top right to apply your updates.
Go to **Configuration > Deploy** in the sidebar. Open the **Channels** tab and choose where Asa should appear.
![Deploy Channels screen showing Shopify, HTML/JS, Headless and coming soon options]()
Today, deploy with **Shopify (Custom App)** — paste a snippet in your theme via the theme editor. A Shopify App Store listing is in review; install-from-store deploy will be simpler once it is live.
On the **Shopify (Custom App)** card, click **Deploy**. A sidesheet opens with step-by-step instructions. Follow them in order.
![Shopify Custom App deploy instructions sidesheet]()
Click **Deploy** on the card for your stack:
* **HTML/JS Website**
* **Headless Storefront (NextJS)**
* **WhatsApp** (coming soon)
* **Instagram** (coming soon)
* **Voice** (coming soon)
Want to test before going live? Open the **Playground** tab under **Configuration > Deploy**.
After you deploy, open your storefront and ask Asa about a product or policy as a shopper would. You are live.
The widget can take a moment to appear. Try a hard refresh if you do not see it. Still stuck? [Contact us](mailto:help@alphablocks.ai).
# See Asa working
Source: https://docs.asa.so/get-started/see-asa-working
Read shopper conversations in the inbox, inspect sources and behavior, and spot what to improve in your training.
Once Asa is live, your job shifts from setup to observation. This guide shows what to look at, what it means, and what to do next.
Navigate to **Activity > Conversations** in the sidebar. Every shopper conversation is listed here.
![Conversations inbox showing list of conversations with status indicators]()
Filter with the tabs across the top:
| Tab | What it shows |
| --------------------- | -------------------------------------------------------- |
| **All Conversations** | Every conversation Asa has had |
| **Assisted** | Resolved without human intervention |
| **Redirected** | Handed to your team — by Asa or at the shopper's request |
Each row shows a title, a one-line preview, and how long ago it happened. The badge on the right is the conversation status:
| Status | What it means |
| -------------- | ------------------------------------------------- |
| **Ongoing** | Started but not yet marked assisted or redirected |
| **Assisted** | Asa resolved it without a human |
| **Redirected** | Escalated to your team |
| **Low-Intent** | Short or low-engagement thread |
| **Closed** | Conversation ended |
Open any conversation to see what happened between Asa and a real shopper.
![Conversation detail showing shopper message, Asa response with product cards and shopper behavior events]()
Four areas to review:
**The conversation**
Does the reply sound like your brand? Is it accurate? Is the product recommendation relevant?
**Shopper behavior events**
A trail of storefront actions during and after the chat — product views, add to cart, remove from cart, cart nudges. This shows whether Asa influenced behavior, not only whether the shopper replied.
**Good and Sources**
* **Good** — mark a strong reply as a quality example.
* **Sources** — trained content Asa used for that answer. Wrong answer? Sources tell you if it is a knowledge gap or poor source material.
**Add Guidance and Add Snippet**
Top right of the conversation. Fix tone or add content without leaving the inbox.
Click **User Activity** in the top right of a conversation for the full picture of that shopper.
![User Activity panel showing shopper profile, storefront events and conversation history]()
| Section | What it shows |
| --------------------- | ---------------------------------------------------------------------------------- |
| **Profile** | Name, email, and location when available |
| **Storefront Events** | What they did on your store in the selected period — context Asa uses in real time |
| **Conversations** | All prior chats with Asa — useful for returning shoppers or repeat escalations |
The inbox is a diagnostic tool, not a log. In your first week, watch for:
**Repeated redirected topics**
Same handover theme (returns, one SKU, an ingredient) → add or improve training, then retrain.
**Off-brand replies**
Tighten **Configuration > Responses > Guidance** → **Communication Style**.
**Rephrased questions**
Same question asked three ways → first answer was weak. Check **Sources** — the knowledge may exist but needs clearer structure.
**Assisted chats with add-to-cart**
Behavior events showing **Add to Cart** after Asa helped → note the question type and ensure strong coverage there.
Spend 10 minutes in the inbox daily for your first two weeks. You will learn more about performance and shopper needs than from reports alone.
For volume and trends over time, open **Activity > Analytics** once traffic grows.
# Google Drive
Source: https://docs.asa.so/integrations/google-drive
Train Asa on selected Google Drive files and documents so answers stay grounded in your internal knowledge.
Product sheets, policies, and help docs often live in Google Drive before they reach your storefront. This guide connects Drive to Asa and trains only the files you choose.
Navigate to **Add Content** in the sidebar, open the **Apps** tab, and click **Connect** on the **Google Drive** card.
Click **Connect**. Google’s sign-in window opens.
* If you are not signed in to Google, sign in with the account that owns the files you want to train.
* After you authorize the connection, the **Google Picker** opens automatically.
Connecting Drive does not train Asa on your files yet. You choose which documents to train in the next step.
In the Google Picker, select the files you want Asa to learn from and confirm your selection. Training starts automatically.
Supported file types: Google Docs, PDF, and plain text (`.txt`). Training usually takes 1–2 minutes, depending on file size and how many documents you selected.
Go to **Manage Content** and confirm your Google Drive sources appear with a **Trained** status.
## Keep content up to date
| Action | How |
| ------------------- | ----------------------------------------------------------------------------------------------------------------- |
| Add more files | On the Google Drive card, open the **Connected** menu and choose **Manage integration** to open the picker again. |
| Retrain after edits | Update the file in Drive, then retrain from **Manage Content** so Asa uses the latest version. |
| Workspace accounts | If you use Google Workspace, confirm your account is allowed to connect third-party apps. |
If you need help, reach out at [help@alphablocks.ai](mailto:help@alphablocks.ai).
# Gorgias
Source: https://docs.asa.so/integrations/gorgias
Connect Gorgias as your handover destination so escalations become support tickets your team can pick up in Gorgias.
When Asa hands a conversation to your team, Gorgias can receive it as a ticket instead of only showing an email card in the widget. Set this up in **Configuration**, not **Add Content** — Gorgias powers handover, not product training.
Navigate to **Configuration > Responses** in the sidebar, then open the **Handover** tab.
Under **Human Support Contact**, choose **Gorgias** from the destination dropdown.
In your [Gorgias](https://www.gorgias.com/) helpdesk, go to **Settings > REST API**.
Create or copy an API key for the account that should own escalated tickets. You need:
| Field | Where to find it |
| ------------------------- | -------------------------------------------------------------------------------- |
| **Gorgias Subdomain** | The subdomain in your helpdesk URL — e.g. `acme` from `https://acme.gorgias.com` |
| **Gorgias Account Email** | Email for the Gorgias user who owns the API key |
| **Gorgias API Key** | **Settings > REST API** in Gorgias |
Back in Asa, click **Connect** next to the Gorgias handover option.
![Connect to Gorgias dialog with subdomain, email, and API key fields]()
Enter your credentials:
| Field | What to paste |
| ------------------------- | -------------------------------------- |
| **Gorgias Subdomain** | Your helpdesk subdomain (e.g. `acme`) |
| **Gorgias Account Email** | Account email for the API key owner |
| **Gorgias API Key** | API key from Gorgias REST API settings |
Click **Connect**. When setup succeeds, the Gorgias row shows **Connected**.
Click **Save Changes** in the top right to confirm your handover settings after Gorgias connects successfully.
In **Activity > Conversations**, a redirected Gorgias handover shows ticket details and an **Open in Gorgias** link on the conversation.
## How handover works with Gorgias
* **Guidance** controls *when* Asa escalates — under **Configuration > Responses > Guidance**, use **Handover to Team** to define the lines Asa should not cross alone.
* **Handover** controls *where* shoppers go — with Gorgias selected, escalations create a ticket in your helpdesk.
* If ticket creation fails, Asa still records the escalation and falls back to your **Email Contact** handover so the shopper is not left without a path to support.
Pair Gorgias with clear Handover to Team instructions — for example, refunds, damaged orders, or explicit requests to speak with a person.
## Notes
* Disconnecting Gorgias restores handover to **Email Contact** until you choose another destination.
* Use the same Gorgias subdomain, email, and API key you use in the Gorgias admin — typos are the most common connection failure.
If you need help, reach out at [help@alphablocks.ai](mailto:help@alphablocks.ai).
# Judge.me
Source: https://docs.asa.so/integrations/judge-me
Connect Judge.me so Asa can surface real product reviews when shoppers ask about your products.
Shoppers trust answers backed by real reviews. Connect Judge.me once and Asa can use your review data alongside your Shopify catalog — about three minutes end to end.
In your **Shopify admin**, go to **Settings > Apps and sales channels**.
Under **Installed apps**, find **Judge.me Reviews**, open it, then click **Open app** in the top right.
In the **Judge.me** sidebar, go to **General Settings > Integrations**.
Click **View API Token** and copy:
| Field | Where to find it |
| ---------------------------- | -------------------------------------------------- |
| **Private API Access Token** | Shown in the API token dialog |
| **Shopify Subdomain** | The part before `.myshopify.com` in your store URL |
Example integrations URL:
`https://admin.shopify.com/store/[your-shopify-subdomain]/apps/judgeme/shop/general_settings/integrations`
![Judge.me Integrations tab showing Private API Access Token and subdomain]()
Navigate to **Add Content** in the sidebar, open the **Apps** tab, and click **Connect** on the **Judge.me** card.
![Asa Connect to Judge.Me dialog with Shopify Subdomain and Private API Access Token fields]()
Enter the values from Judge.me:
| Field | What to paste |
| ---------------------------- | ------------------------------------------------------------ |
| **Shopify Subdomain** | Your store subdomain (e.g. `acme` from `acme.myshopify.com`) |
| **Private API Access Token** | The token from Judge.me |
Click **Connect**. When setup succeeds, the card shows **Connected**.
Only one reviews app can be connected at a time. If you already use Klaviyo Reviews or Yotpo, disconnect that integration before connecting Judge.me.
## Notes
* Your **Shopify Subdomain** must match the subdomain in your Shopify admin URL exactly.
* The API token gives Asa read access to review data only — not full store admin access.
If you need help, reach out at [help@alphablocks.ai](mailto:help@alphablocks.ai).
# Klaviyo Reviews
Source: https://docs.asa.so/integrations/klaviyo
Connect Klaviyo Reviews so Asa can surface real product reviews when shoppers ask about your products.
Shoppers trust answers backed by real reviews. Connect Klaviyo Reviews once and Asa can use your review data alongside your Shopify catalog — about two minutes end to end.
Navigate to **Add Content** in the sidebar, open the **Apps** tab, and click **Connect** on the **Klaviyo Reviews** card.
![Add Content Apps tab showing integration cards including Klaviyo Reviews]()
Klaviyo’s authorization window opens in a new tab.
* Sign in with the Klaviyo account tied to your store’s reviews.
* Review the permissions Asa requests.
* Click **Allow** or **Authorize** to grant access.
![Klaviyo OAuth authorization screen for Asa]()
When authorization completes, you return to Asa and the connection finishes automatically — usually in under a minute.
On the **Klaviyo Reviews** card, the status shows **Connected**.
Only one reviews app can be connected at a time. If you already use Judge.me or Yotpo, disconnect that integration before connecting Klaviyo Reviews.
## Notes
* Authorize the Klaviyo account and workspace that match your Shopify store.
* If the authorization window does not open, check your browser’s popup blocker and try again.
If you need help, reach out at [help@alphablocks.ai](mailto:help@alphablocks.ai).
# Notion
Source: https://docs.asa.so/integrations/notion
Train Asa on selected Notion pages so answers stay grounded in your internal knowledge.
SOPs, FAQs, and product notes often live in Notion before they reach your storefront. This guide connects Notion to Asa and trains only the pages you choose.
Navigate to **Add Content** in the sidebar, open the **Apps** tab, and click **Connect** on the **Notion** card.
![Add Content Apps tab showing integration cards including Notion]()
A Notion sign-in window opens. Sign in with the workspace account that owns the pages you want to train, then approve Asa’s access request.
Authorizing Notion does not train Asa on your content yet. You choose which pages to train in the next step.
After OAuth completes, the **Allow Asa to access these Notion pages** dialog opens automatically.
![Notion page selection dialog with checkboxes and Proceed button]()
Select the pages you want Asa to learn from, then click **Proceed**. Training usually takes 1–2 minutes depending on how much content you selected.
Go to **Manage Content** and confirm your Notion sources appear with a **Trained** status.
## Keep content up to date
| Action | How |
| ------------------- | ---------------------------------------------------------------------------------------------------------------- |
| Add more pages | On the Notion card, open the **Connected** menu and choose **Manage integration** to open the page picker again. |
| Retrain after edits | Update the page in Notion, then retrain from **Manage Content** so Asa uses the latest version. |
If you need help, reach out at [help@alphablocks.ai](mailto:help@alphablocks.ai).
# Shopify
Source: https://docs.asa.so/integrations/shopify
Connect Shopify so Asa can learn from your products, pages, blogs, and policies — the foundation for accurate storefront answers.
Your Shopify catalog is Asa's most important content source. Connect your store, then choose exactly what Asa should learn from.
**Today, use the Custom app path.** The official Asa Shopify app is in App Store review and is not generally available yet. Once it is approved, you will be able to install from the Shopify App Store instead of creating a custom app.
Use this path now — connect Asa with a **Shopify custom app** and Admin API credentials from the [Shopify Dev Dashboard](https://shopify.dev/docs/apps/build/dev-dashboard).
In your **Shopify admin**, go to **Settings > Apps and sales channels**, then **Develop apps** and open **Build apps in Dev Dashboard**.
Click **Create app** and name it **Asa Custom App**, then click **Create**.
If you cannot access the Dev Dashboard, you may lack the required permissions. Ask your store admin. For help from Asa, email [help@alphablocks.ai](mailto:help@alphablocks.ai).
In your custom app, open **Access > Scopes** and paste these scopes:
```
read_app_proxy,read_content,read_customer_events,read_customers,read_discounts,read_fulfillments,read_inventory,read_legal_policies,read_metaobject_definitions,read_metaobjects,read_online_store_pages,read_orders,read_pixels,read_product_listings,read_products,read_publications,read_themes,write_app_proxy,write_pixels
```
Click **Release**, then **Install** and select the store to install on.
Open the **Settings** tab in your custom app.
Under **Credentials**, copy the **Client ID** and **Secret** — you need both in Asa.
Navigate to **Add Content** in the sidebar, open the **Apps** tab, and click **Connect** on the **Shopify (Custom App)** card.
![Connect to Shopify Legacy dialog with Client ID, Client Secret, Storefront Public URL, and Shopify Subdomain]()
Enter your credentials:
| Field | What to paste |
| ------------------------- | ------------------------------------------------------------------------ |
| **Client ID** | Client ID from your custom app |
| **Client Secret** | Secret from your custom app |
| **Storefront Public URL** | Your live store URL (e.g. `https://acme.com`) |
| **Shopify Subdomain** | Subdomain from **Settings > Domains** — the part before `.myshopify.com` |
Example: if your admin URL is `https://admin.shopify.com/store/acme/settings/domains`, your subdomain is `acme`.
Click **Connect**. When setup succeeds, the card shows **Connected**.
Connecting Shopify does not train Asa on your catalog yet. You choose what to train in the next section.
Use this path after the Asa app is live on the [Shopify App Store](https://apps.shopify.com/). It is the simpler install flow once listing approval is complete.
**Asa customers:** The Shopify app is still in App Store review and is not available for general use yet. To connect your store today, use the [**Custom app**](#custom-app) tab above.
The steps below walk Shopify App Store reviewers through the install and connect flow. They will apply to all customers once the app is approved.
In your **Shopify admin**, open the **Shopify App Store**, search for **Asa**, and open the Asa listing.
Click **Install**, then choose the store you want to connect if you manage more than one.
Shopify shows a permissions screen for what the Asa app can access — products, content, orders, metafields, and related store data.
Review the permissions, then click **Install app** to approve.
Shopify redirects you to the Asa dashboard when installation finishes.
On the Asa sign-in screen:
* **Log in** if you already have an account.
* **Sign up** if you are new to Asa.
After sign-in, you land on **Add Content** and the Shopify connection flow opens for the store you just installed.
After install, Asa opens the Shopify connection on **Add Content**. You may see one of two dialogs:
**A — Confirmation dialog (most common after App Store install)**\
The **Connect Asa to Shopify Store** dialog shows which **Asa AI Agent** (by ID) you are connecting and your Shopify store subdomain.
This step is required to enable the Shopify integration in Asa, even if the Asa Shopify app is already installed on your store.
Click **Connect** to finish the connection.
**B — Full connect dialog**\
If you connect manually from the Shopify card, open **Connect to Shopify App** and confirm both fields:
| Field | What to enter |
| --------------------------- | ------------------------------------------------------------------------ |
| **Shopify Store Subdomain** | The part before `.myshopify.com` (e.g. `acme` from `acme.myshopify.com`) |
| **Public Store URL** | Your public storefront URL (e.g. `https://acme.com`) |
![Connect to Shopify App dialog with Shopify Store Subdomain and Public Store URL fields]()
Click **Connect**.
* If the Asa app is not installed on that store yet, Asa redirects you to complete Shopify authorization first.
* When connection succeeds, the Shopify card shows **Connected**.
Connecting Shopify does not train Asa on your catalog yet. You choose what to train in the next section.
## Select content and train
After Shopify connects — on either path — the content selection dialog opens automatically. If it does not, open the **Connected** menu on the Shopify card and choose **Manage integration**.
In **Allow Asa to access these data sources**, select what Asa should learn from — for example **Products**, **Blogs**, **Pages**, and **Policies**.
![Shopify content selection dialog with Products, Blogs, Pages, and Policies categories]()
If you selected products, click **Next** to open **Select Metafields** and choose which product metafields Asa should use.
Click **Proceed** to start training. If you did not select products, click **Proceed** from the content screen instead.
Training usually takes a few minutes depending on how much you selected.
Go to **Manage Content** and confirm your Shopify sources show a **Trained** status.
## Keep content up to date
| Action | How |
| ----------------------------- | ----------------------------------------------------------------------------------------------------------------------------- |
| Add or change catalog content | On the Shopify card, open **Connected** → **Manage integration** to update your selection. |
| Retrain after Shopify edits | Update products or pages in Shopify, then retrain from **Manage Content**. |
| Custom app permissions | Custom app setup must include all Admin API scopes from the **Add Admin API scopes** step — Asa only accesses what you grant. |
To put Asa on your storefront after training, go to **Configuration > Deploy** and follow the Shopify channel instructions.
## Notes
* Until the Asa Shopify app is approved, use the **Custom app** path and the **Shopify (Custom App)** card in **Add Content**.
* After App Store approval, the **Shopify app** tab describes the install-from-store flow.
* Double-check credentials and store URLs — typos are the most common connection failure.
* Only the scopes or permissions you approve are used by Asa.
If you need help, reach out at [help@alphablocks.ai](mailto:help@alphablocks.ai).
# Smartrr
Source: https://docs.asa.so/integrations/smartrr
Connect Smartrr so Asa can answer subscription questions with live account data and let shoppers manage their subscriptions.
Smartrr powers subscription status, next order dates, and account actions (pause, skip, cancel, reactivate, and change frequency). Connect it in **Configuration > Integrations**, then enable the skills in **Responses**. This integration requires the **Growth** plan.
In Shopify, open the **Smartrr** app. In the left sidebar, go to **Integrations**, then **API Keys**.
Click **Add Key** (or **Create Key**) and give it a nickname such as `ASA`.
Set **Subscriptions** to **Read and Write** so Asa can pause, skip, cancel, reactivate, and change frequency. Leave **Selling Plan** on **Read** if that option is shown.
Create the key and copy the token. You will not be able to view the full token again.
In Asa, go to **Configuration > Integrations**, open **Smartrr**, and click **Connect**.
Paste the token into **Smartrr API Token** and click **Connect**. When setup succeeds, the page shows **Connected**.
Smartrr subscription skills are available on the Growth plan. If Connect is locked, upgrade first.
Still on the Smartrr page, click **Open Skills**, or go to **Configuration > Responses > Skills**.
Turn on the subscription skills you want shoppers to use: pause, skip, cancel, reactivate, and change delivery frequency.
Ask Asa a subscription question on a logged-in storefront session. Asa should return live status or offer the actions you enabled.
## What Asa can do after you connect
* **Account data** — live subscription status and next order dates.
* **Pause and skip** — pause an active subscription or skip the next delivery.
* **Cancel and reactivate** — cancel an active subscription or resume a paused one.
* **Frequency** — change delivery frequency (for example 4 weeks to 8 weeks).
Shoppers must be logged in for management actions. Status lookup uses the connected Smartrr account data.
## Notes
* Create the API token in Smartrr (**Integrations > API Keys**), not in Shopify admin settings.
* If connection fails, generate a new key and confirm **Subscriptions** is set to **Read and Write**.
* Disconnecting Smartrr turns off live subscription answers until you connect again.
If you need help, reach out at [help@alphablocks.ai](mailto:help@alphablocks.ai).
# Yotpo
Source: https://docs.asa.so/integrations/yotpo
Connect Yotpo so Asa can surface real product reviews when shoppers ask about your products.
Shoppers trust answers backed by real reviews. Connect Yotpo once and Asa can use your review data alongside your Shopify catalog — about three minutes end to end.
In your **Shopify admin**, go to **Settings > Apps and sales channels**.
Under **Installed apps**, find **Yotpo: Product & Photo Reviews**, open it, then click **Open app** in the top right.
![Shopify Settings showing Yotpo in installed apps]()
In the **Yotpo** sidebar, go to **Settings > Store Settings > API Credentials**.
Copy both values:
| Field | Where to find it |
| -------------- | -------------------- |
| **App Key** | API Credentials page |
| **Secret Key** | API Credentials page |
Example credentials URL:
`https://admin.shopify.com/store/[your-shopify-subdomain]/apps/yotpo/reviews/settings/api-credentials`
![Yotpo API Credentials page showing App Key and Secret Key]()
Navigate to **Add Content** in the sidebar, open the **Apps** tab, and click **Connect** on the **Yotpo** card.
![Asa Connect to Yotpo dialog with Yotpo App Key and Yotpo Secret fields]()
Enter the values from Yotpo:
| Field | What to paste |
| ----------------- | -------------------------- |
| **Yotpo App Key** | Your App Key from Yotpo |
| **Yotpo Secret** | Your Secret Key from Yotpo |
Click **Connect**. When setup succeeds, the card shows **Connected**.
Only one reviews app can be connected at a time. If you already use Klaviyo Reviews or Judge.me, disconnect that integration before connecting Yotpo.
## Notes
* Copy **App Key** and **Secret Key** exactly as shown in Yotpo — extra spaces break the connection.
* API credentials give Asa read access to review data only — not full store admin access.
If you need help, reach out at [help@alphablocks.ai](mailto:help@alphablocks.ai).
# Limitations of Asa
Source: https://docs.asa.so/legal/asa-limitations
Learn what are the limitation of ASA and its guidelines
**Effective day 1 January 2025**
We built Asa to help you shop with confidence by answering questions about our products, policies, and store. But since Asa is powered by AI, there are a few important things to know:
### **✅ What Asa Can Do**
* Answer questions about our catalog, reviews, and store policies.
* Suggest products, bundles, or alternatives based on your needs.
* Share information drawn directly from our site and uploaded content.
* Connect you with brand team if your question needs a human touch.
### **⚠️ What Asa Can’t Do**
* **Guarantee 100% accuracy** — Asa relies on the latest synced data, and mistakes are possible.
* **Replace expert advice** — Asa is not a doctor, pharmacist, lawyer, or financial advisor. For health, safety, or legal questions, please consult a professional.
* **Reflect instant changes** — Prices, promotions, or stock updates may take time to sync.
* **Handle emergencies** — Asa isn’t designed for urgent or critical situations.
### **🔒 Privacy & Safety**
* Conversations with Asa are kept secure and follow our store’s privacy policy.
* Personal or sensitive information should not be shared with Asa - except for order tracking - but should be limited to only required.
### **🧑 Human Support**
If Asa can’t answer your question or you’d prefer to speak with a real person, you can always reach to storefront support directly.
# Cookie Policy
Source: https://docs.asa.so/legal/cookies
Information about what cookies ASA uses and its reasons
**Effective day 1 January 2025**
This Cookie Policy explains how Alphablocks Tech Pvt. Ltd. (collectively "Alphablocks", "we", "us", and "our"), our service providers, and advertising partners automatically collect information through [ww.alphablocks.com](http://ww.alphablocks.com) and our other websites (the “Sites”), and in connection with services and our marketing activities.
## **Cookies and similar technologies we use**
* **Cookies** are text files that websites store on a visitor’s device to uniquely identify the visitor’s browser or to store information or settings in the browser for the purpose of tracking user activity and patterns, helping the visitor navigate between pages efficiently, remembering preferences, improving the visitor’s browsing experience, and enabling functionality, analytics, and targeted advertising. Cookies used on our Sites include cookies that we serve as well as cookies served by third parties that we work with to enable the services they provide, such as analytics services that track traffic and usage. You can learn more about cookies and how to control them at [www.allaboutcookies.org](http://www.allaboutcookies.org).
* **Web beacons, also known as pixel tags or clear GIFs**, are typically used to demonstrate that a webpage or email was accessed or opened, or that certain content was viewed or clicked, typically to compile statistics about usage of websites and the success of marketing campaigns.
* **Browser web storage** (including HTML5), also known as locally stored objects, functions like cookies but enables the storage of a larger amount of data.
* **Session replay**. We use third party software code to record users’ interactions with the Sites in a manner that allows us to watch and analyze visual reconstructions of those user sessions. The replays include users’ clicks, mobile app touches, mouse movements, scrolls, and keystrokes/key touches during those sessions. These replays help us diagnose usability problems and identify areas for improvement. One of the providers of this technology is Posthog, which you can learn about here: [https://posthog.com/session-replay](https://posthog.com/session-replay)
* **Chatbot features.** The Sites provides users with chatbots that users can use to get information and support. We and the third parties that support these features monitor and record the information you submit to the chat to enable the chat and for the other purposes described in our Privacy Policy. When you use these features, you are not communicating with a human.
## **First Party Cookies Policy for Asa Widget**
Asa is a Storefront AI tool owned fully by Alphablocks. It allows D2C brands to offer Sales, Support and Shopping Experience to their customers and online visitors using AI.
Cookies used by the Asa widget (technology that allows us to offer Asa to you as a no-code/ low-code tool) are "first-party" cookies assigned to the domain of your website. We take the privacy of your data seriously and these cookies cannot be read by Alphablocks on other sites, or by other sites using the Asa widget. All cookies are unique to your domain.
Here are the cookies used by the Asa widget, their purpose, duration and a brief description:
| Cookie Name | Purpose | Default Duration | Description |
| :------------------------------------- | :-------------------------- | :--------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| alphablocks-sessionId-\[assistant\_Id] | Unique anonymous identifier | 1 year | Anonymous visitor identifier cookie. As people visit your site they get this cookie. This is used to uniquely to track each visitor and their interactions with your Asa AI Agent over time. |
If you wish to learn more about the cookies we use, and how we safeguard your privacy in context of cookies, please reach out to us at [help@alphablocks.ai](mailto:help@alphablocks.ai)
# Fair Usage Policy
Source: https://docs.asa.so/legal/fair-usage
Information about fair usage policy of ASA
**Effective day 1 January 2025**
This Fair Usage Policy (“FUP”) is incorporated into, and forms part of, the Alphablocks’ Terms of Service. This FUP applies to all Customers, Permitted Users and People who use the Services.
## **General**
To keep the Services running safely and smoothly, you agree not to and not to permit or encourage anyone else to:
1. use the Services for any illegal or prohibited purpose or in violation of any applicable laws (including without limitation data protection, privacy, artificial intelligence (AI) and export control laws) in connection with using the Services;
2. probe, scan, or test the vulnerability of any system or network used with the Services;
3. tamper with, reverse engineer or hack the Services, circumvent any security or authentication measures of the Services or attempt to gain unauthorized access to the Services (or any portion thereof) or related systems, networks or data (including through spoofing or social engineering);
4. modify or disable the Services or use the Services in any manner that interferes with or disrupts the integrity or performance of the Services or related systems, network or data;
5. access or search the Services by any means other than our publicly supported interfaces;
6. copy, modify, create derivative works of, distribute, or disclose any part of the Services in any medium, including without limitation by any automated or non-automated “scraping”;
7. access or use the Services in order to monitor its availability, performance, or functionality for competitive purposes;
8. overwhelm or attempt to overwhelm our infrastructure by imposing an unreasonably large load on the Services that consume extraordinary resources, such as by: (i) using “robots,” “spiders,” “offline readers” or other automated systems to send more request messages to our servers than a human could reasonably send in the same period of time using a normal browser; or (ii) going far beyond the use parameters for any given Service as described in its corresponding documentation;
9. use the Services to generate or send unsolicited communications, advertising, phishing or spam, or otherwise cause Alphablocks to become impaired in its ability to send communications on its own or on its customers’ behalf (e.g., by causing Alphablocks to become registered on any Email DNS blocked list or otherwise be denied services by any other third party communications service provider);
10. misrepresent yourself or disguise the origin of any data, content or other information you submit (including by “spoofing”, “phishing”, manipulating headers or other identifiers, impersonating anyone else, or falsely implying any sponsorship or association with Alphablocks or any third party) or access the Services via another user’s account without their permission;
11. Submit (or post, upload, display, share, instruct to be used or otherwise provide) data, content, fonts or other information, that (i) you don’t have the right to utilize (including confidential or personal information you are not authorized to disclose) or which otherwise infringes Alphablocks’ or a third party’s intellectual property or other rights; (ii) and/or is deceptive, manipulative, exploitative, fraudulent, bullying, threatening, misleading, illegal, obscene, defamatory, libelous, threatening, harmful to minors, pornographic, indecent, harassing, hateful, violent, encourages illegal or tortious conduct, is religiously, racially or ethnically offensive, or is otherwise inappropriate in Alphablocks’ discretion; (iii) contains viruses, malware, bots, worms, scripting exploits or other similar materials; or (iv) could otherwise cause damage to Alphablocks or any third party;
12. use meta tags or any other “hidden text” including Alphablocks’ trademarks; or
13. engage in any activity that may result in unlawful bias or discrimination of an individual or group of individuals.
## **AI Products**
In addition to the restrictions outlined above that generally apply when using the Services, this section also applies when you are using any AI Product. You agree not to use and not to permit or encourage anyone else to use (including by means of prompting or generating any Output) any AI Products for the following purposes:
1. To make or directly facilitate automated decisions that will impact an individual's safety, rights, well-being, or which produces legal effects concerning an individual or similar significant effects concerning an individual;
2. To provide any financial, legal, medical or other professional advice or the practice of any occupation subject to licensing requirements under applicable laws;
3. In a manner that constitutes use as a medical device or medical device software;
4. To provide any illegal gambling, real money gambling, payday lending or sports betting;
5. To engage in political or electoral campaigning or lobbying, including generating campaign materials personalized to or targeted to specific demographics;
6. Input image or text that potentially is classified harmful across several categories as per OpenAI’s content moderation policies.
7. Generating or promoting disinformation, misinformation, or other intentionally deceiving or misleading content.
8. Any use case which is deemed “high-risk” under applicable AI legislation, including but not limited to use of an AI Product for: biometric identification and classification; emotional recognition; the safety component of critical infrastructure; the safety component of a product; determining access to education and vocational training; recruitment, monitoring or terminating employment of individuals; making a creditworthiness assessment or establishing a credit score; risk assessing or pricing life and health insurance, evaluating eligibility for essential services.
## **Remedies**
A violation of this FUP is a violation of the Agreement. Without affecting any other remedies available to us, Alphablocks may permanently or temporarily terminate or suspend a user’s account or access to the Services without notice or liability if Alphablocks (in its sole discretion) determines that a user has violated this Fair Usage Policy.
# Privacy Policy
Source: https://docs.asa.so/legal/privacy
About privacy policy and guidelines of ASA
**Effective day 1 January 2025**
**Last update on 21 July 2025**
## **Purpose and Scope**
1. At Alphablocks, we respect your privacy and data protection rights and recognize the importance of protecting the personal data we collect and process. This Privacy Policy is designed to help you to understand what personal data we collect about you and how we use and share it.
2. When we refer to Alphablocks, we mean Alphablocks Tech Pvt. Ltd., a company registered in India with office at \_5 S.F., Satyam Shopping Center, Nr. Inqalab Society, Gulbai Tekra, Ahmedabad, Gujarat, India 380015 \_("**Alphablocks**", "**we**", "**us**", "**our**").
3. This Privacy Policy applies to you if you:
* interact with any of Alphablocks’ websites (including [www.alphablocks.ai](http://www.alphablocks.ai), [www.tryasa.com](http://www.tryasa.com) and any of its domains, subdomains or related domains ) or our applications or widgets or our social media pages (collectively, the "Sites") ("**website users**");
* visit any of Alphablocks’ premises ("**office visitors**");
* attend an Alphablocks event or an event which Alphablocks sponsors ("**event attendees**");
* use Alphablocks' applications, widgets, AI products, workspaces, mobile applications, and our other applications and services (collectively, the "**Alphablocks** **Services** ") ("**customers**");
* are a marketing prospect, who is anyone whose data Alphablocks processes for the purposes of assessing customer eligibility ("**marketing prospect**"); or
* receive marketing communications from Alphablocks.
The below Privacy Policy applies to you irrespective of where you are based. There are certain additional parts of the Privacy Policy that will apply to you where you are a resident of the California. These additional parts do not apply to everyone.
## **Personal Data Collected by Alphablocks**
### **Personal Data We Collect And Receive**
### **Cookies And Other Tracking Technologies**
## **How And Why We Use Your Personal Data**
We collect and process your personal data for the following purposes:
* **Providing and facilitating delivery of the Alphablocks Services and Sites**: We process your personal data to perform our contract with you for use of our Services and Sites and to fulfill our obligations under applicable terms of service. Where we have not entered into a contract with you, we process your personal data in reliance on our legitimate interests to operate and administer the Alphablocks Services and Sites. For example, to create, administer and manage your account.
* \*\*Session Replays: \*\*We use session recording tools (such as PostHog), specifically on user dashboards, to better understand how users interact with our Services. These tools may capture anonymized usage patterns such as clicks, scrolls, and navigation paths — but they do **not** collect sensitive information like passwords or payment details. This data is used solely to improve functionality, identify usability issues, and enhance user experience. It is strictly for internal use — never shared with third parties or used for any other purpose.
* **Communicating with you about the Alphablocks Services and providing customer support**: We may send you service, technical and other administrative messages in reliance on our legitimate interests in administering the Alphablocks Services. For example, we may send you messages about the availability or security of the Alphablocks Services. We also process your personal data to respond to your comments and questions and to provide customer care and support. When we have entered into an agreement with you, we process your personal data as necessary to meet our contractual obligations to you.
* **Improving the Alphablocks Services and Sites**: We process your personal data to improve and optimize the Alphablocks Services and Sites and to understand how you use the Alphablocks Services and Sites, including to monitor usage or traffic patterns and to analyze trends and develop new products, services, features and functionality in reliance on our legitimate interests or, where necessary, to the extent you have provided your consent.
* **Sending marketing communications**: We process your personal data to send you marketing communications via email, post or SMS about our products, services and upcoming events that might interest you in reliance on our legitimate interests or where we seek your consent.
* **Complying with legal obligations**: We process your personal data when cooperating or complying with public and government authorities, courts or regulators in accordance with our obligations under applicable laws and to protect against imminent harm to our rights, property or safety, or that of our users or the public, as required or permitted by law.
## **Sharing Your Personal Data**
We may disclose some or all of the personal data we collect to the following third parties:
* Business entities and Product entities owned by Alphablocks;
* Consultants and vendors engaged by us to support our provision of the Alphablocks Services and Sites and the operation of our business;
* Professional advisors, such as lawyers, auditors and insurers, in the course of the professional services that they render to us;
* Compliance with Law Enforcement
We may also share aggregated or anonymized information with third parties for other purposes. Such information does not identify you individually, but may include usage, viewing and technical information such as the websites you generally use, the configuration of your computer, and performance metrics related to the use of websites which we collect through our technology, products and services. If we are required under applicable law to treat such information as personal data, then we will only disclose it as described above. Otherwise, we may disclose such information for any reason.
**Third party websites**. The Sites may also contain links to third party websites. This Privacy Policy applies solely to information processed by us. You should contact the relevant third party websites for more information about how your personal data is processed by them.
## **Retention Of Your Personal Data**
* We retain your personal data only for as long as necessary to fulfill the purposes set out in this Privacy Policy.
* Note that content you post may remain on the Sites even if you cease using the Sites or we terminate access to the Sites.
## **How We Store and Safeguard Your Personal Data**
We care about protecting personal data. That is why we put in place appropriate measures that are designed to secure your personal data. You can reach out to us at [help@alphablocks.ai](mailto:help@alphablocks.ai) to find out more about our technical and organizational safeguard.
## **Your Privacy Rights and Choices**
* If you wish to access, correct, update or request deletion of your personal data, you can do so at any time.
* You can object to processing of your personal data, ask us to restrict processing of your personal data or request portability of your personal data.
* You have the right to opt-out of marketing communications we send you at any time. If you no longer wish to receive our newsletter and promotional communications, you may opt-out of receiving them by clicking on the "unsubscribe" or "opt-out" link in the communications we send you. Please note, however, that it may not be possible to opt-out of certain service-related communications. You can let us know at any time if you do not wish to receive marketing messages by contacting us using the contact details below.
* Similarly, if we have collected and processed your personal data with your consent, then you can withdraw your consent at any time. Withdrawing your consent will not affect the lawfulness of any processing we conducted prior to your withdrawal, nor will it affect processing of your personal data conducted in reliance on lawful processing grounds other than consent.
## **Children’s Privacy**
Our Services and Sites are not intended for use by anyone under the age of 16. Alphablocks does not knowingly collect personal data from anyone under the age of 16. If you are under 16, you may not attempt to register for our Services or send any information about yourself to us, including your name, address, telephone number, or email address. If we become aware that we have collected personal data from someone under the age of 16 without verification of parental consent, we will delete that information promptly. If you are a parent or legal guardian of a child under 16 and believe that a child has provided us with their personal data, please contact us at [help@alphablocks.ai](mailto:help@alphablocks.ai)
## **Changes To This Notice And Questions**
We may amend this Privacy Policy from time to time in response to changing legal, technical or business developments. When we update it, we will take appropriate measures to inform you, consistent with the significance of the changes we make. If we make material updates to this Privacy Policy we will update the effective date at the top of the Privacy Policy.
If you have any questions, comments or concerns about this Privacy Policy or the way your personal data is being used or processed by us, please contact us at [help@alphablocks.ai](mailto:help@alphablocks.ai)
# Refunds Policy
Source: https://docs.asa.so/legal/refunds
Information about refund policy by ASA
**Effective day 1 January 2025**
**Last update on 28 August 2025**
At [alphablocks.ai](http://alphablocks.ai) & [app.asa.so](https://app.asa.so), we strive to provide high-quality digital products and services. Due to the nature of our offerings, all purchases are generally non-refundable. However, if you experience technical issues or believe you have been charged in error, please contact our support team at [hello@alphablocks.ai](mailto:hello@alphablocks.ai) within 7 days of your purchase, and we will review your request on a case-by-case basis. If a **full or partial refund** is approved, it will be processed promptly, and the amount will be credited to your bank account within **5–7 working days**. Our goal is to ensure fairness and customer satisfaction.
# Terms of Service
Source: https://docs.asa.so/legal/terms-of-service
Terms and condition for ASA product
**Effective day 1 January 2025**
These Alphablocks Terms of Service (the “**Agreement**") are entered into by and between the Alphablocks entity set forth below (“Alphablocks") and the entity or person placing an order for, or accessing, any Services (“**Customer**” or “**you**"). If you are accessing or using the Services on behalf of your company, you represent that you are authorized to accept this Agreement on behalf of your company, and all references to “you” or “Customer” reference your company. This Agreement permits Customer to purchase subscriptions to online software-as-a-service products and other services from Alphablocks and sets forth the terms and conditions under which those products and services will be provided.
The “**Effective Date**” of this Agreement is the date that is the earlier of: (a) Customer's initial access to any Services through any online provisioning, registration or order process or (b) the effective date of the first Order Form referencing this Agreement.
As used in this Agreement, “Alphablocks” means Alphablocks Tech Pvt. Ltd., a company registered in India with office at \_5 S.F., Satyam Shopping Center, Nr. Inqalab Society, Gulbai Tekra, Ahmedabad, Gujarat, India 380015 \_("**Alphablocks**", "**we**", "**us**", "**our**").
**Modifications to this Agreement**: From time to time, Alphablocks may modify this Agreement. Unless otherwise specified by Alphablocks, changes become effective for Customer upon renewal of Customer's current Subscription Term, or entry into a new Order Form. Alphablocks will use reasonable efforts to notify Customer of the changes through communications via Customer's account, email or other means. Customer may be required to click to accept or otherwise agree to the updated Agreement before renewing a Subscription Term or entering into a new Order Form, but in any event continued use of the Services after the updated version of this Agreement goes into effect will constitute Customer's acceptance of such updated version. If Alphablocks specifies that changes to the Agreement will take effect prior to Customer's next renewal or new Order Form (such as for legal compliance, product or pricing change reasons) and Customer objects to such changes, Customer may terminate the applicable Subscription Term on notice in writing to Alphablocks and receive as its sole remedy a refund of any fees Customer has pre-paid for use of the applicable Services for the terminated portion of the Subscription Term, commencing on the date notice of termination was received. The amount of these fees will be decided on case to case basis depending on the subscription plan customer had subscribed to prior termination.
**BY INDICATING YOUR ACCEPTANCE OF THIS AGREEMENT OR ACCESSING OR USING ANY SERVICES, YOU ARE AGREEING TO BE BOUND BY ALL TERMS, CONDITIONS, AND NOTICES CONTAINED OR REFERENCED IN THIS AGREEMENT. IF YOU DO NOT AGREE TO THIS AGREEMENT, PLEASE DO NOT USE ANY SERVICES. FOR CLARITY, EACH PARTY EXPRESSLY AGREES THAT THIS AGREEMENT IS LEGALLY BINDING UPON IT.**
## **Alphablocks Services**
1. **Services Overview**: Alphablocks Services are a suite of ecommerce focussed software products, largely enable by AI, offered as a software-as-a-service solutions offered through an online platform. The Services are designed to enable Companies to manage interactions with their customers through the entire lifecycle of their purchase journey and beyond.
2. **Provision of Services.** Each Service is provided on a subscription basis for a set term designated on the Order Form (each, a “**Subscription Term**"). Customer will purchase and Alphablocks will provide the specific Services as specified in the applicable Order Form.
3. **Access to services:** Use of and access to the Services is permitted only by Permitted Users. If Customer is given API keys or passwords to access the Services on Alphablocks’ systems, Customer will require that all Permitted Users keep API keys, user ID and password information strictly confidential and not share such information with any unauthorized person. User IDs and related credentials are granted to individual, named persons and may not be shared. If Customer is accessing the Services using credentials provided by a third party (e.g., Google), then Customer will comply with all applicable terms and conditions of such third party regarding provisioning and use of such credentials. Customer will be responsible for any and all actions taken using Customer's accounts and passwords. If any Permitted User who has access to a user ID is no longer an employee (or Contractor, as set forth below) of Customer, then Customer will promptly delete such user ID and otherwise terminate such Permitted User's access to the Service. Alphablocks reserves the right to suspend access to any Services or features if Customer has exceeded applicable usage limits (if any) or if Alphablocks otherwise determines, in its sole discretion, that Customer is using the applicable Service in a manner that has become excessive (e.g., substantially exceeds typical use projections or exceeds usage by similar-sized customers, including, but not limited to, storage and bandwidth consumption) and/or negatively impacts the operability, integrity, or security of the Service until usage is reduced to reasonable levels, as determined by Alphablocks and/or such impact is resolved to Alphablocks’ satisfaction. We may change usage limits at any time, in our sole discretion, without notice.
4. **Alphablocks Apps:** To the extent Alphablocks provides Alphablocks Apps for use with the Services, subject to all of the terms and conditions of this Agreement (unless otherwise indicated in the specific Alphablocks App), Alphablocks grants to Customer a limited, non-transferable, non-sublicensable, non-exclusive license during any applicable Subscription Term to use the object code form of the Alphablocks Apps internally, but only in connection with Customer's use of the Service and otherwise in accordance with the Documentation and this Agreement.
5. **Alphablocks Code:** The right to use the Services includes the right to deploy Alphablocks Code to enable core functionalities and deploy them to customer’s end users. Subject to all of the terms and conditions of this Agreement, Alphablocks grants to Customer a limited, non-transferable, non-sublicensable, non-exclusive license during any applicable Subscription Term to copy and implement the Alphablocks Code in the form provided by Alphablocks on Deploy section in the dashboard solely to support Customer's use of the Service and otherwise in accordance with the Documentation and this Agreement. Customer must implement Alphablocks Code on the Dashboard in order to enable the relevant features of the Services. Customer will implement all necessary Alphablocks Code in strict accordance with the Documentation and other instructions provided by Alphablocks. Customer acknowledges that any changes made to the deployment code after initial implementation of Alphablocks Code may cause the Services to cease working or to function improperly and that Alphablocks will have no responsibility for the impact of any such code changes and rather the customer is responsible to ensure the necessary changes are made to make it work. Customers can always reach out to us at [hello@alphablocks.ai](mailto:hello@alphablocks.ai) if they run into any issues at any point of time when implementing Alphablocks code.
6. \*\*Contractors and Affiliates: \*\*Customer may permit its employees and Contractors and its Affiliates' employees and Contractors to serve as Permitted Users, provided Customer remains responsible for compliance by such individuals with all of the terms and conditions of this Agreement and any use of the Services by such Permitted Users is for the sole benefit of Customer.
7. **General Restrictions:** Customer will not (and will not permit any third party to): (a) rent, lease, provide access to or sublicense the Services to a third party; (b) use the Services to provide, or incorporate the Services into, any product or service provided to a third party other than the customer’s own sites and services; (c) reverse engineer, decompile, disassemble, or otherwise seek to obtain the source code or non-public APIs to the Services, except to the extent expressly permitted by applicable law (and then only upon advance notice to Alphablocks); (d) copy or modify the Services or any Documentation, or create any derivative work from any of the foregoing; (e) remove or obscure any proprietary or other notices contained in the Services and/or on any reports or data printed from the Services (unless otherwise expressly permitted by Alphablocks in advance); (f) publicly disseminate information regarding the performance of the Services; (g) use the Services for competitive analysis purposes; or (h) otherwise violate our [FUP](https://linear-stingray.super.site/fair-usage-policy).
8. **Alphablocks APIs:** If Alphablocks makes access to any APIs available as part of the Services, Alphablcoks reserves the right to place limits on access to such APIs (e.g., limits on numbers of calls or requests, or usage). Further, Alphablocks may monitor Customer's usage of such APIs and limit the number of calls or requests Customer may make if Alphablocks believes that Customer's usage is in breach of this Agreement or may negatively affect the security, operability, or integrity of the Services (or otherwise impose liability on Alphablocks).
9. **Trial Subscriptions:** If Customer receives free access or a trial or evaluation subscription to the Service (a “**Trial Subscription**"), then Customer may use the Services in accordance with the terms and conditions of this Section (and any other supplemental trial terms agreed by Customer) for a period of days listed as the trial period duration or such other period granted by Alphablocks (the “**Trial Period**"). Trial Subscriptions are permitted solely for Customer's evaluation to determine whether to purchase a paid subscription to the Services or an upgrade to a service plan. Trial Subscriptions may not include all functionality and features accessible as part of a paid Subscription Term and may be subject to usage limits. If Customer does not enter into a paid Subscription Term prior to the expiration of the Trial Period, this Agreement and Customer's right to access and use the Services will terminate at the end of the Trial Period, except as otherwise set forth herein. If stated in the Order Form or Additional Product Terms for a specific Service or otherwise communicated in advance by Alphablocks to Customer, a paid Subscription Term will commence automatically once the Trial Period expires, and Customer will be charged for any continued use of the Services. Alphablocks has the right to terminate a Trial Subscription at any time for any reason.
10. **Beta Offerings:** Customer may choose to use Beta Offerings in its sole discretion. Use of Beta Offerings may be subject to additional terms. Alphablocks, in its discretion, may offer a Beta Offering with or without charge. Alphablocks reserves the right to start charging and/or modify the pricing for a Beta Offering upon prior written notice to Customer. Beta Offerings may be changed at any time without notice and may not be maintained and/or become generally available. Beta Offerings are to be used for Customer's internal testing and evaluation purposes only and are not subject to the same security measures as for the general availability offerings. Alphablocks will have no liability arising out of or in connection with Beta Offerings and disclaims any warranty, indemnity, support, SLA, or other obligations with respect to its Beta Offerings. **CUSTOMER USES BETA OFFERINGS “AS IS” AND AT ITS OWN RISK.**
# Best practices for training Asa
Source: https://docs.asa.so/resources/best-practices
Practical ways to keep Asa accurate: what to train, how to maintain content, and how to learn from shopper conversations.
Asa answers from what you train in the [dashboard](https://app.asa.so). Strong content beats volume — clear, current, non-conflicting sources produce the most trustworthy storefront answers.
Train the sources that resolve real questions first.
1. Go to **Add Content** in the sidebar.
2. Connect **Shopify** if you sell there — products, policies, and key pages cover most pre-purchase and support questions.
3. Add policies, sizing guides, or FAQs via **Files**, **Websites**, or **Notion** / **Google Drive** if they live outside Shopify.
In **Manage Content**, every item you need at launch shows **Trained**. Use **View Content** on a row to confirm Asa extracted what you expect.
Auto-sync products, pages, policies, and blogs.
Plan limits and what counts as one source.
| Practice | Why it helps |
| ----------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Use integrations over one-off uploads** | Shopify, Notion, and Google Drive stay closer to your live catalog and docs. Shopify updates retrain the same source — they do not inflate your count with duplicates. |
| **Remove outdated trained sources** | Delete retired products, old policies, or broken URLs from **Manage Content** so Asa cannot cite stale answers. |
| **Retrain after major edits** | Changed a Notion page or re-uploaded a file? Retrain from **Manage Content** so the latest version is what shoppers get. |
Conflicting facts across sources (two different return windows, mismatched shipping copy) can confuse answers. Pick one canonical source per topic and remove or fix duplicates.
Use **Activity > Conversations** to read what shoppers actually ask and where Asa escalated to your team (**redirected** conversations).
| Signal | What to do |
| -------------------------------------- | --------------------------------------------------------------------------------------------------------------------- |
| Same question many times | Add or improve a trained source (product copy, policy page, Notion FAQ). |
| Wrong or thin answer | Open **View Content** on the relevant source; fix the source material, then retrain. |
| Team handles the same macro repeatedly | Turn the answer into a **Snippet** under **Add Content > Snippet** — snippets do not use plan knowledge source quota. |
On **Starter** and **Growth**, **Activity > Analytics** helps you spot volume and themes over time as traffic grows.
More files do not always mean better support.
* Train pages shoppers reference — shipping, returns, sizing, ingredients, compatibility — not internal drafts.
* Write in plain language; Asa passes through structure and facts from your sources.
* Stay within your [knowledge source limit](/resources/trained-source-count). If you hit the cap, remove low-value trained rows or upgrade on [Plans and pricing](/resources/plan-pricing).
**Snippets** are ideal for short, stable answers (warranty one-liner, promo rules). Publish trained snippets as widget FAQs from **Manage Content** when you want them on the greeting screen.
Once training looks good, align how Asa speaks and when it hands off:
* **Configuration > Appearance** — brand look and widget placement ([Make Asa your own](/get-started/make-asa-your-own)).
* **Configuration > Responses** — tone, length, human support contact, and **Guidance** instructions.
* **Configuration > Responses > Handover** — when to route to Gorgias or your team ([Gorgias integration](/integrations/gorgias)).
Content quality and behavior settings work together; fix training gaps before chasing tone tweaks alone.
## Quick reference
| Do | Avoid |
| -------------------------------------------------------- | ---------------------------------------------------------------- |
| Connect Shopify and train high-intent catalog + policies | Training every product when only a subset is in stock or on sale |
| Delete unused sources in **Manage Content** | Leaving conflicting return or shipping copy in multiple files |
| Use **Snippet** for repeatable short answers | Uploading the same FAQ as PDF, URL, and Notion page |
| Review **Conversations** weekly after launch | Ignoring redirected threads that reveal missing policies |
Need help prioritizing content for your catalog? Contact [help@alphablocks.ai](mailto:help@alphablocks.ai).
# Plans and pricing
Source: https://docs.asa.so/resources/plan-pricing
Compare Free, Starter, and Growth plans — conversations, knowledge sources, integrations, and capabilities. Outcome-based pricing with no upfront cost.
Asa uses outcome-based pricing: start free, upgrade when you need more conversations, knowledge sources, and intelligence. Every paid plan includes a **14-day free trial**. No setup fees or long-term contracts.
For live prices and the full comparison matrix, see [asa.so/pricing](https://asa.so/pricing).
All prices are in **USD**. The website may show **Early Adopter** rates for Starter and Growth.
## Plan overview
| Plan | Price (per month) | Best for |
| ----------- | ----------------- | ------------------------------------------------- |
| **Free** | \$0 | Trying Asa on your store with no commitment |
| **Starter** | \$49 | Stores ready to turn conversations into revenue |
| **Growth** | \$199 | Brands that want full intelligence and visibility |
### Free
Try Asa on your store for free.
* **50** conversations / month
* **50** knowledge sources
* Shopify auto-training, files, URLs, snippets
* Google Drive and Notion integrations
* Self-serve support
### Starter
Everything in Free, plus:
* **500** conversations / month
* **250** knowledge sources
* Review integrations (Judge.me, Yotpo, Klaviyo Reviews)
* Advanced behavior, tone, and response controls
* Context-aware product guidance and personalized recommendations
* Reviews and AI summaries
* Basic upsell, cross-sell, and proactive nudges
* Session-only shopper memory
* Email support and immediate escalation notifications
* Basic conversation analytics, event tracking, and insights
### Growth
Everything in Starter, plus:
* **2,500** conversations / month
* **500** knowledge sources
* Advanced appearance customization
* Granular behavior, tone, and response controls
* Recommendations with past-purchase signals
* Advanced upsell, cross-sell, and proactive nudges
* Long-term shopper memory
* Priority email + Slack support
* Advanced inbox, analytics, event tracking, and business insights
## Compare plans
### General
| Feature | Free | Starter | Growth |
| --------------------- | --------------- | ------- | ---------------------- |
| Conversations / month | 50 | 500 | 2,500 |
| Knowledge sources | 50 | 250 | 500 |
| Support | Self-serve docs | Email | Priority email + Slack |
### Training and customization
| Feature | Free | Starter | Growth |
| ------------------------------------ | ------------------------- | ----------------------------------------------- | ----------------------------------------------- |
| Auto-trained on store data | Shopify | Shopify | Shopify |
| Custom knowledge upload | Files, URLs, snippets | Files, URLs, snippets | Files, URLs, snippets |
| Content integrations | Google Drive, Notion | Google Drive, Notion + Judge.me, Yotpo, Klaviyo | Google Drive, Notion + Judge.me, Yotpo, Klaviyo |
| Appearance customization | Basic | Basic | Advanced |
| Behavior, tone and response controls | Basic | Advanced | Granular |
| Escalation and handover | Email + link to your team | Email + link + immediate notifications | Email + link + immediate notifications |
| WISMO automation | Standard | Standard | Standard |
### Intelligence capabilities
| Feature | Free | Starter | Growth |
| ------------------------------- | ----- | -------------------------- | -------------------------------------------------- |
| Product guidance | Basic | Context-aware | Context-aware |
| Product recommendations | Basic | Personalized, intent-based | Personalized, intent-based + past-purchase signals |
| Reviews and AI summaries | — | Included | Included |
| Upsell and cross-sell | — | Basic | Advanced |
| Proactive engagement and nudges | — | Basic | Advanced |
| Shopper memory | — | Session only | Session only + long-term memory |
### Insights and observability
| Feature | Free | Starter | Growth |
| --------------------------- | ----- | ------- | -------- |
| Conversations inbox | Basic | Basic | Advanced |
| Conversation analytics | — | Basic | Advanced |
| Event tracking | — | Basic | Advanced |
| Business + product insights | — | Basic | Advanced |
## How to choose
* **Free** — Evaluate Asa, connect Shopify, and train a small catalog slice.
* **Starter** — You need review apps, stronger customization, nudges, and analytics as volume grows.
* **Growth** — You need higher limits, advanced nudges and insights, long-term shopper memory, and priority support.
Knowledge source limits count products, pages, files, and integration items individually. See [How knowledge sources are counted](/resources/trained-source-count) for details.
Usage limits are per month and may change. The comparison table on [asa.so/pricing](https://asa.so/pricing) is the canonical reference when in doubt.
If you need help choosing a plan, reach out at [help@alphablocks.ai](mailto:help@alphablocks.ai).
# How knowledge sources are counted
Source: https://docs.asa.so/resources/trained-source-count
Understand what counts toward your plan's knowledge source limit and how to check usage in the dashboard.
Every Asa plan caps how many **knowledge sources** Asa can have trained at once. Each trained source is one row in **Manage Content** — except snippets, which are unlimited and do not count.
Plan limits: **50** (Free), **250** (Starter), **500** (Growth). See [Plans and pricing](/resources/plan-pricing) for the full comparison.
## What counts as one knowledge source
| Source type | How it is counted |
| ------------------------------- | -------------------------------------------- |
| **Files** (PDF, DOCX, CSV, TXT) | One file = one knowledge source when trained |
| **Websites** (URL) | One URL = one knowledge source when trained |
| **Shopify — Products** | One product = one knowledge source |
| **Shopify — Blogs** | One blog article = one knowledge source |
| **Shopify — Pages** | One Online Store page = one knowledge source |
| **Shopify — Policies** | One store policy = one knowledge source |
| **Notion** | One selected page = one knowledge source |
| **Google Drive** | One doc or file = one knowledge source |
When you select content to train, the dashboard shows how many **Knowledge source(s)** you are about to use — for example in the Shopify and Notion selection dialogs.
## What does not count separately
These are included with the parent source, not billed as extra knowledge sources:
| Item | Included with |
| ---------------------- | ------------------------------------------ |
| **Product metafields** | The Shopify product you trained |
| **Judge.me reviews** | The linked Shopify product |
| **Yotpo reviews** | The linked Shopify product |
| **Klaviyo Reviews** | The linked Shopify product |
| **Snippets** | Do not count toward your plan limit at all |
Snippets are added under **Add Content > Snippet**. Use them for short FAQs or macros without using plan capacity. You can publish trained snippets as widget FAQs from **Manage Content**.
## Shopify stays in sync without extra sources
When Shopify is connected, product and content updates sync via webhooks. Retraining updates the **same** knowledge source row — it does not create a duplicate count for the same product, page, or article.
Prefer **Add Content > Apps** (Shopify, Notion, Google Drive) over manual uploads when content lives there already. Integrations keep answers current with less manual re-uploading.
## Check your usage
Open **Billing** from your account menu (or subscription settings) and find **Usage Summary**. **Total Knowledge Sources** shows trained count versus your plan limit (for example `42 / 250`).
If training is blocked, the dashboard explains how many sources you have left or prompts you to upgrade.
## Plan limits at a glance
| Plan | Knowledge sources |
| ----------- | ----------------- |
| **Free** | 50 |
| **Starter** | 250 |
| **Growth** | 500 |
Conversations, integrations, and feature comparison by plan.
Questions about a specific source? Reach out at [help@alphablocks.ai](mailto:help@alphablocks.ai).