InstantAIguru Admin Guide

Admin Console Overview

Layout

The console has a menu down the left side and the open section to its right:

• Left menu — the sections of your Guru: Appearance, General, Instructions, Channels, Knowledge Files, Users, Integrations and Subscription. Below a divider are Settings, a link to the Chat Dashboard, links to the CSAT Dashboard and Live Support when those integrations are on, and this guide. Your account sits at the bottom.
• Top bar — the name of the open section, and the actions that apply to the whole Guru (below).

The address keeps the open section (for example #channels), so a reload, a bookmark or a link opens that section. The ⇤ button beside the logo collapses the menu to icons, and the console remembers it. On a phone the menu is a drawer opened from the ☰ button.

The top bar provides these actions:

Your account menu

Click your name at the bottom of the menu for:

Saving Changes

The Save button in the top-right corner turns solid purple whenever you have unsaved changes. That includes work done elsewhere and handed back to this window — flows, tools and global variables sent over from the Flow Designer, and files brought in with Upload Flows or Upload Tools — not only what you typed into a form.

Review Changes

If you try to Exit or Re-index with unsaved work, the console offers Review Changes. It shows exactly what Save would write: every field, with its Original value beside Your Modification.

Two things worth knowing about what you see there:

• Paths name records, not slots. users[[email protected]] › channels identifies a person, so deleting one user does not make the users below look edited, and reordering flows is not reported as changes.
• The chips count what changed. Flows, Tools and Globals chips appear only when that registry actually differs, and count changed entities — three edits across two flows is “Flows: 2 changed”, because the rows below already itemise the fields. The Flow Designer hands back its whole registry every time it saves, so a registry that came over untouched says nothing at all. In the figure above, Tools has no chip for exactly that reason.

When someone else has been editing

When you click Save, the console performs a 3-way merge: the configuration as it was when you loaded the page (the original), your changes, and the latest version on the server. Anything only you changed is applied. Anything only the other person changed is kept. If you both changed the same field to different values, a conflict resolution dialog asks you to choose — the original value, yours, or theirs — for each conflict.

• Agreement is not a conflict. If you and the other person made the same edit, there is nothing to decide and you are not asked.
• Deletions are resolved whole. If the other person deleted a record while you were editing a field inside it — a user, a channel, a schedule — you are asked about the complete record, not the one field you touched. Keeping “yours” restores the whole thing; several edits inside one deleted record collapse into that single decision.
• If the server changes again while you are still deciding, your resolutions are dismissed and you are asked to click Save again against the newer version.

Permission-Based Access

An administrator gives each user permissions (see Users). A section you have no permission for stays in the menu with a 🔒 lock and does not open; clicking it says so. Each section has its own permission, and General is open to everyone. The Admin permission opens Users, where other users and their permissions are managed. If the section a link points to is locked, the console opens the first section you can use.

Appearance

What your chat widget says and looks like, beside a live preview. Appearance is the first section of the console, and it works like the setup wizard: six steps, one card at a time, with Back and Next, or click a step’s name to jump to it. Nothing here needs an Apply button — every change shows in the preview at once. Click Save to keep it.

The live preview

The right half shows a picture of your own site with your real Guru on it: the chat button there is the actual widget, so you can open it and chat. The picture is taken the first time you open Appearance. If your site cannot be pictured (for example, because it asks visitors to prove they are a person), the frame says why, offers Try again, and the preview works the same on a plain background.

1. Words

2. Colors

Pick one of 8 presets, or set each color yourself. A preset fills in the four colors below:

Colors apply as you pick them.

3. Icon

The button visitors tap to open the chat:

4. Effect

An animation and short teasers that draw attention to the chat button:

5. Position

Choose which corner of the page the chat widget occupies, how far in it sits from the edges, and whether visitors may move it themselves. Every control here previews immediately, so there is no Apply button. Click Save to keep it.

Picking a corner moves the chat button in the preview as you click, so you judge the result against your own site rather than against the form:

6. Install

Add to your site holds the one line of code that puts your Guru on your site. Click Copy and paste it once, before the closing </body> tag. Everything you set in Appearance then reaches your site when you Save, with no new code. See Deploying Your Guru for platform-by-platform steps.

General

Your Guru’s domain and owner, the support contact shown to your visitors, how your site is read, and your own profile.

Your Guru

Reading your site

Your profile

Setting your password for the first time

If you reached the console through an email invitation or a Forgot password link, your account does not have a password yet: the Change button reads Set Password, and the password dialog opens by itself without the Current Password field, because there isn’t one.

Instructions

This is where you define your Guru's identity, expertise, and purpose. These instructions shape how the AI assistant behaves and responds to your visitors.

Who your Guru is

Advanced notes

Collapsed under Advanced notes: optional extra instructions for one step of how an answer is made. Most Gurus never need them — leave them blank to use the default behavior.

Channels

Where your Guru answers besides your website: WhatsApp, text messages (SMS), phone calls (Voice) and email. Add them with the buttons at the top of the section: Connect WhatsApp, Add Twilio number (SMS and Voice) and Add email. Each channel type has its own group below.

WhatsApp Channels

WhatsApp Business uses Meta's Embedded Signup flow. Connecting a WhatsApp number to your Guru is a popup launched from the Connect WhatsApp button at the top of Channels.

Beyond text, WhatsApp customers can send photos, voice notes and PDFs, all handled automatically with nothing to enable. See Sending Media on the Other Channels.

Acknowledge before answering

The WhatsApp and SMS sections each start with an Acknowledge before answering checkbox. When it is on and a question needs a search of your knowledge, the Guru first sends a short message such as “Let me check that for you…”, and the answer follows as usual. A reply from a flow is sent without one. The setting is off by default and applies to every number in that section. The checkbox appears once the section has at least one number.

What you need

A Facebook account that can manage your business on Meta, and a phone number for WhatsApp that can receive a verification code by SMS or voice call. Everything else can be done inside the signup popup: choosing or creating your business portfolio and WhatsApp Business Account (WABA), and adding and verifying the number.

References:

• Meta: the Embedded Signup screens
• Meta: business verification

Connect via Embedded Signup

In Channels, click Connect WhatsApp. Meta’s Embedded Signup popup opens on facebook.com and walks you through:

1. Facebook login — skipped if you are already signed in in this browser.
2. Business portfolio — pick yours, or create one.
3. WhatsApp Business Account — pick one, or create one with the public profile (name, category, description) customers see in WhatsApp.
4. Phone number — enter the number and verify it with the code Meta sends.
5. Permissions and finish — review what InstantAIguru may do on the account and click Finish.

Meta changes these screens from time to time and skips the ones whose answer it already knows, so you may see fewer.

Meta then hands the connection back to our app. A new WhatsApp channel card appears in Channels with these fields:

Twilio Setup (Required for SMS & Voice)

Both SMS and Voice channels run on your own Twilio number, and one number serves both. You connect your Twilio account once from the console, and your Guru answers calls and texts on that number. Twilio bills your account directly for the number, messages and minutes; your subscription with us covers the AI handling on top.

Step 1: Have a Twilio Account

If you don’t have one yet, sign up at twilio.com/try-twilio and upgrade it by adding a payment method. Twilio lets only upgraded accounts approve connected apps, and texting registration needs one too.

Step 2: Connect Twilio and Choose a Number

1. In Channels, click Add Twilio number, then Connect your Twilio account.
2. Sign in to Twilio and approve InstantAIguru. Twilio creates a separate subaccount just for your Guru (Subaccount for ConnectApp: InstantAIguru), so nothing else in your account is touched, and returns you to the console.
3. Pick a number:
   • Numbers ready for your Guru lists the numbers already in that subaccount. Click Use this number.
   • Get a new number: enter an area code, click Search, then Choose and Confirm: buy this number. Twilio charges your account for it, about $1.15 a month in the US, plus usage.
   • A number already in your main Twilio account can be used too: in the Twilio console open it (Phone Numbers › Active numbers), choose Transfer, move it to the InstantAIguru subaccount, then press Refresh.
4. Name the line, choose the Language on calls (English or Spanish here; the line’s own card offers more languages afterwards), and keep Answer phone calls and Answer text messages checked for both. Click Start answering on this number. If your account is subscribed, you approve the change to your subscription, since each line is a channel.

The number’s webhooks are set for you. Calls are answered right away. Texts need the registration in Step 3.

Step 3: Register for Texting (A2P 10DLC)

US carriers deliver business texts only from registered numbers (A2P 10DLC). Once a texting line is added, the same dialog shows Texting registration, and we file it with Twilio for you:

1. Fill in your business details: legal name, EIN, business type, industry, website, address and your contact details.
2. Carriers’ reviewers must see your texting number on a public page of your site with our “Text us” text right next to it, and texting sections in your terms and privacy policy. Enter the three page addresses, copy the three texts onto those pages, and click Check pages.
3. Click Register for texting, then Confirm: file and accept Twilio’s fees. Twilio bills your account about $19.50 once (business registration and campaign review) and $1.50 to $10 a month while texting is on.
4. Your business is reviewed first. Come back to Add Twilio number and press Check: once the business is approved, Check files the texting campaign. When the campaign is approved the dialog reads Registered and your Guru replies to texts.

The console files a registered business with an EIN. Without an EIN, register as a Sole Proprietor in the Twilio console yourself (see Sole Proprietor vs Standard Path).

Approval Timing

Real-world experience for most customers: campaign approval typically lands in 2 to 3 days, sometimes faster, occasionally up to a week. Business (brand) approval comes first, usually within 1 to 3 days.

• Voice is live as soon as the line is added. You can answer calls immediately.
• SMS accepts inbound messages, but replies are not delivered until the campaign is approved, so register as early as you can.

Entering Twilio Credentials Instead

Accounts set up before Twilio Connect, or that prefer to manage the number in Twilio themselves, can still enter credentials by hand: click Add Twilio number, then Enter Twilio credentials instead. You then buy the number, point its webhooks at InstantAIguru and register for texting in your Twilio console.

1. Buy a number with SMS and Voice in the Twilio Console (Phone Numbers → Manage → Buy a number). Reference: Twilio: How to Buy a Phone Number.
2. Open the number’s Configure tab and set its webhooks (both HTTP POST), then save:

   Twilio Section	Field	Value
   Voice and emergency calling	A CALL COMES IN	Webhook: https://api.instantaiguru.com/v1/twilioVoice
   Messaging	A MESSAGE COMES IN	Webhook: https://api.instantaiguru.com/v1/twilioSMS

3. For texting, register in Messaging → Regulatory Compliance: a Customer Profile, a Brand, a Campaign (use case, sample messages, opt-in and opt-out, privacy and terms URLs), then attach the number to the campaign. References: A2P 10DLC Quickstart · Campaign Approval Requirements.
4. From the Twilio Console homepage’s Account Info, copy your Account SID and Auth Token. Enter the phone number with its country code (e.g. +15551234567), the Account SID and the Auth Token, keep SMS and Voice checked, and click Add Channel.

Sole Proprietor vs Standard Path

When you register in the Twilio console yourself, Twilio routes the registration by one question on the Brand form: “Does your company have a business registration number?” (EIN in the US, Business Number in Canada).

SMS Channels

Prerequisite: complete Twilio Setup first. An SMS channel is added with Add Twilio number at the top of Channels, with Answer text messages checked.

Acknowledge before answering works here exactly as it does for WhatsApp. See Acknowledge before answering.

SMS channels also accept MMS: customers can send photos and audio clips, which the Guru reads and transcribes. Nothing needs enabling. See Sending Media on the Other Channels.

Voice Channels

Prerequisite: complete Twilio Setup first. Voice channels are also added with Add Twilio number, with Answer phone calls checked. Besides Voice Phone Number (read-only), Channel Name, Twilio Account SID, Twilio Auth Token, Voice Custom Greeting and Voice Deployment Context, a Voice card has:

Like the SMS card, the Voice card’s Twilio Auth Token field has a Show button to reveal the stored value. The card also includes the Channel Name, Twilio Account SID, Twilio Auth Token, and Voice Deployment Context fields shared with SMS, plus a Voice Custom Greeting.

Live Agent Service Hours

The Live Agent Service Hours editor lets you define when the live agent is available to receive transferred calls. It appears in the Voice channel card as soon as you enter a Live Agent Phone Number and is hidden when the phone number is cleared.

The schedule also sets what callers are told: when someone asks for an agent outside these hours, the Guru states the hours exactly as configured here (for example, "Our agents are available Monday through Friday 9 AM to 7 PM, and Saturday 9 AM to 3 PM, Pacific time."), followed by the Agents Unavailable Message.

Email Channels

Email channels let your end-users email questions to your Guru at a dedicated address. The AI generates a contextual reply with proper RFC threading headers (so it lands in the original email thread in their inbox) and an automatic AI-disclosure footer (required for compliance with California's BOT law and the EU AI Act).

Add an email channel with the Add email button at the top of Channels. Unlike Twilio channels, no external account is needed — the address is provisioned instantly. You may add multiple email channels per Guru (e.g., one for general support, one for sales, one for billing) by giving each its own Department: click Add email again and you are asked for one (lowercase letters, digits and hyphens, e.g. sales), which gives the new channel its own address.

Setup Pattern

Most customers don't change their public-facing email address. The recommended pattern is to forward mail from your existing support address to the channel's inbound address:

1. End-users continue to email [email protected] as usual.
2. You configure your email provider (Google Workspace, Microsoft 365, etc.) to forward all support@ mail to [email protected] (the Inbound Address shown on the card).
3. The AI receives the forwarded copy and replies on your behalf, with the original sender as the recipient.

Built-In Features

Branded From Address (optional)

Until a domain is verified, replies are sent From: the channel's inbound address (<slug>@inbox.instantaiguru.com). To send them from your own domain (e.g., [email protected]), use the channel's From Address field: a new channel pre-fills support@<your domain>. Change it if needed and click Verify Domain. The status line below the field shows ⏳ Not yet verified, ✓ Verified or ✗ Verification failed, and updates as you type.

If verification failed (Amazon SES stops checking about 72 hours after it starts), click Verify Domain again to restart it. DNS records you already added keep counting.

The verify modal shows four DNS records you must add to your domain's DNS host (Cloudflare, Route 53, GoDaddy, etc.):

• Three CNAME records — DKIM signing keys. These prove that mail signed with the matching private key really came from us, on your behalf. Each is a separate, additive record. Cloudflare users: set proxy status to DNS only (gray cloud) on all three.
• One TXT record — the SPF record (see the warning below).

SPF and DKIM are independent layers of authentication, and they don't share the "one record only" constraint. SPF is a single TXT record on the apex domain authorizing approved senders. DKIM uses one CNAME per signing key, so multiple email services on the same domain coexist cleanly — SES adds three CNAMEs without affecting any DKIM records your other services have already created.

After the records propagate (typically 5–30 minutes), click Check Status in the verify modal. Once verification succeeds, save the channel configuration to activate sending from the branded address. If you skip the verification or it fails, the channel falls back to the default inbox.instantaiguru.com From address — you do not lose service.

Knowledge Files

Documents your Guru learns from in addition to your website: price lists, manuals, policies, product catalogs, or anything not on your public site.

The Your files table lists every uploaded file with its Name, Size (KB) and Last modified. Tick files (or the header box to select them all) to delete them.

Users

People who can sign in to this console, and what each may do. Only users with the Admin permission can open this section.

Managing Users

The cards edit your user list directly. Click a card to select it, click a field or the permission grid to edit, and type — every keystroke goes straight into the configuration. There is no per-card Save or Cancel: Save in the top bar commits the section, and checks every user you touched just before it writes.

User Card Fields

These rules are checked when you click Save. Names and addresses are trimmed of stray spaces, and only the users you actually touched are checked — an older record that was already incomplete will not block an unrelated change. Duplicate addresses are the exception: uniqueness is checked across the whole list every time. If a check fails, the save stops and names the user and the field.

Invitations

You never hand out a password. When you Save a new user, they are emailed an invitation automatically: a secure link to set their own password. The email names your account’s domain, the link works once and is valid for 72 hours, and opening it shows the Set Password dialog straight away. A toast confirms “Invitation emailed to {email}”, or says the invitation could not be sent.

Each card shows where its invitation stands:

Permission Checkboxes

Each permission opens a section or a feature:

Integrations

Connect your Guru to third-party platforms to extend its capabilities.

JSFE Workflows

JSFE is the workflow engine that runs the flows you build in the Flow Designer. The card's toggle controls whether JSFE is billed as a channel on your subscription:

• Base integration flows are free. The bundled system and Shopify integration flows run without enabling this card — you are never billed for them.
• Custom flows auto-enable it. As soon as your Guru has one or more custom flows defined, the card locks on (custom flows require the engine) and the status line shows how many flows are driving it.
• No custom flows? The toggle is manual — enable it only if you want the engine billed and available ahead of building flows.

Like any channel change, the toggle is a draft: billing reconciles when you Save, through the same confirmation prompt described under Channels.

API call log (optional)

If your flows call your own API and that API keeps a request log, the card can connect it to the Chat Dashboard. With the URL and token both saved, each conversation in the dashboard shows the API calls it made, in an API Calls column.

Action safety

Some flow steps act on a customer’s account: they charge a card, cancel a service, change contact details. These settings decide how the engine guards those actions against running twice when a reply is lost or a caller repeats themselves. Only a platform administrator sees and changes them; for everyone else the card keeps them as they are.

Shopify Integration

Add the Instant AI Guru app to your store from the Shopify App Store — open the listing at apps.shopify.com/instant-ai-guru and click Install, or search Instant AI Guru under Apps in your Shopify admin. Installing from the App Store connects your store automatically (no API credentials required) and is billed through Shopify.

Activating the Chat Widget on Your Storefront

If you installed the Instant AI Guru app from the Shopify App Store, the storefront chat widget is delivered as a theme app extension. After installation, you must enable the extension in your active theme before the widget appears on your storefront.

The easiest way: the Shopify card in the admin console shows an “Activate your chat widget on your storefront” banner while the widget is pending — its Activate Widget button opens your theme editor with the widget preselected, so all that's left is toggling it on and clicking Save. Or do it manually:

1. In your Shopify admin, go to Online Store → Themes.
2. Click Customize on your active (published) theme.
3. In the theme editor's left sidebar, click the App embeds icon.
4. Locate InstantAIGuru Chat Widget in the list and toggle it on.
5. Click Save in the top-right corner.

The chat widget will now appear on every storefront page. To disable the widget, repeat these steps and toggle the embed off — no code changes required.

The Shopify card also holds an optional MCP Endpoint (empty uses https://<your store>/api/mcp) and the Admin API Version (default 2025-01); leave both as they are unless we ask you to change them. A collapsed Legacy Token section is only for custom apps created before January 2026.

ShipStation — Live Carrier Tracking

Your store already tells the Guru where an order stands. ShipStation adds the carrier’s own scan history on top of that — where the parcel physically is, when it last moved, and any delivery exception — so a customer asking “where is my order?” gets the same detail an agent would read off the carrier site.

CSAT — Post-call Surveys

Automatically text or email a short customer-satisfaction survey link to the customer after a call. By default the survey runs on our managed CSAT — nothing to deploy: create an admin login and choose how the link is delivered. Prefer to run your own? Tick I self-host CSAT and point the card at your own deployment instead.

Managed (default). Leave I self-host CSAT unticked and click Create CSAT Admin Login: we provision a private CSAT space for this Guru and return a one-time invite link. Open it, set a username + password, and you are the admin. Once CSAT is switched on and saved, a CSAT Dashboard link appears in the lower part of the left menu to open your results. It is greyed out while the service is offline, and for users without the CSAT permission or with Read Only.

Self-host. Tick I self-host CSAT to reveal the CSAT Site URL and CSAT Secret fields (below) and connect the card to your own deployment.

curl -fsSL https://raw.githubusercontent.com/ronpinkas/csat/main/install.sh | sudo sh

Toggle CSAT — Post-call Survey on to reveal the configuration panel. The survey choice and invitation messages sit at the top with the general settings; the Twilio plumbing lives in a collapsible SMS delivery section that stays expanded until a From number is saved and collapses (click to expand) once delivery is configured:

In self-host mode the portal requires the CSAT URL + Secret and at least one delivery method — an SMS number (with its credentials) or the email option — before it will save. In managed mode delivery is handled for you; configure SMS/email here only if you want to customise it.

Live Support — Live Agent Calls

Let visitors talk to a live human agent over audio, video, and chat straight from your site or chatbot. Like CSAT, it runs on our managed Live Support by default, or on your own deployment if you self-host. Toggle Live Support — Live Agent Calls on to configure it.

Managed (default) — two ways in for your team:

Self-host — tick I self-host Live Support to reveal the connection fields:

Outbound Call Agent

Your Guru calls a list of contacts from your own voice lines, at the pace and hours you set, and retries anyone who did not answer. When a person picks up, the Guru speaks your greeting and then carries the conversation like any inbound call, with your flows (payments, look-ups, live agent hand-off) available as usual.

Outbound lines and billing

Switch the card on, tick the voice lines the agent may call from, and Save. That subscription is billed at Save like any other channel: one channel for the Outbound Call Agent, plus one channel for each ticked line (on top of that line’s own voice channel). It appears under Billed Channels as Outbound Call Agent and Outbound lines.

• At least one ticked line is required. With the agent on and no line ticked, Save is refused before anything is billed, and the card says so.
• Campaigns call only from ticked lines. A campaign is saved with the lines it calls from, so Save refuses a campaign whose line is not ticked. A line used by a saved campaign cannot be unticked, or removed from Channels, until that campaign is moved to another line or deleted; Save refuses it. (If a line ever does lose its subscription, the campaign is paused before its next call.)
• Switching the agent off pauses every running campaign. Switching it back on does not restart them; press Start on each one you want running.

Creating a campaign

Click New campaign and fill in sections 1 to 4, then Save the page: a campaign’s settings are saved with Save, like every other setting. Section 5 loads its contact list with Load list, which acts right away and does not need a Save. Nothing is called until you press Start, which runs the saved campaign and so waits while the page has unsaved changes. The card lists your campaigns with their status (no list yet until a list is loaded), languages and their Reached, Gave up and Total counts; Refresh updates them. Click a campaign’s name to edit it, or Delete campaign to remove it when you Save (a running campaign must be paused or stopped first). A campaign added with New campaign and left empty (no name, call context, language or list) is dropped when you close it. In an empty name, greeting or context field, press → to start from the example shown in it (see Admin Console shortcuts).

Running a campaign and daily lists

Daily campaigns: keep one campaign with daily hours. Each morning, Stop it (if it is still running), open it, choose the day’s file, check Start and End, load it with Load list, and Start. Anyone from yesterday you still want to reach simply goes back into today’s file.

Subscription

Your plan, the channels you are billed for, and what your Guru knows.

Your plan and your Guru’s knowledge

Coverage Counters

Under Your Guru’s knowledge, a second group records what the last build actually reached. These appear only once a build has recorded them, so a Guru indexed before this was added shows nothing here rather than a misleading zero. Re-index to populate them.

Billed Channels

Lists every channel you are billed for, each at your plan’s per-channel rate: your website (Web), each WhatsApp, SMS and Voice number, each Email slug, JSFE when enabled, and the Outbound Call Agent with its outbound lines. Phone-based channels are listed by number; Email channels by their slug (e.g. sales.acmewidgets.com). While you have no live subscription it is titled Channels (billed when you subscribe) and shows your configured channels — what you would be billed for when you subscribe.

Subscription Actions

AWS Marketplace billing

If you bought instantAIguru through AWS Marketplace, AWS bills you and holds the contract. Subscription shows what AWS reports and replaces the Stripe buttons with an AWS panel. There is no checkout, plan picker or cancel button here; those are all in AWS Marketplace.

Linking your purchase to a Guru

After you buy in AWS Marketplace, AWS sends you to our Activate your AWS purchase page. Sign in to an existing Guru, or create a new one. Linking does not buy a second AWS contract.

Once you are signed in, the admin asks you to confirm which Guru the purchase belongs to:

• Link Purchase moves this Guru’s billing to AWS Marketplace. This cannot be undone from the admin.
• Not This Account leaves it unlinked. Sign in to the correct Guru in the same browser tab and you will be asked again.

Complete the link in the same tab within 24 hours. After that, start again from the setup link in AWS Marketplace. If AWS has not confirmed the purchase yet, the link still succeeds and the status reads Pending AWS Confirmation until it does, usually within a few minutes.

The AWS panel

If AWS reports a problem with the contract (it has ended, has not started, combines more than one plan tier, and so on), a red box in the panel says what is wrong and what to do.

Channels on an AWS contract

• Adding a channel needs room on the contract. If Save would take you past your contracted number of channels, it tells you to upgrade in AWS Marketplace first and saves your other changes without the new channel; add it again once the upgrade appears here. Only a net increase needs room: swapping one channel for another, or removing one, does not. Channels cannot be added while the contract is not active (Save drops the addition the same way).
• Removing a channel frees a slot but does not lower your AWS charge. Save says so and asks you to Continue. A smaller contract takes effect at renewal, in AWS Marketplace.
• A smaller contract at renewal. If you renew for fewer channels than you have configured, the panel shows Action required: choose which channels to remove, then Save. Your Guru stays active in the meantime, and the panel shows the deadline. If you have not chosen by then, we keep the web channel and your other channels in their saved order up to the new limit; JSFE custom flows keep a slot only if one is left.

Settings

Fine-tune how your Guru finds information and talks to people. Settings is in the lower part of the menu.

Session expiry (SMS and WhatsApp)

A phone number is an assumption, not an identity — US carriers reassign roughly 100,000 numbers a day. These three fields decide how long a customer who passed a one-time code stays verified, and how long a conversation survives at all before it is discarded. Leave any of them blank to use the platform default shown in the field.

Answers and references

Search (under Answers and references)

Frequent questions (chat starters) are set in Appearance → Words.

Twilio account

The default Twilio number and credentials for platform features that send SMS outside a specific channel — most importantly Flow (JSFE) SMS steps, which require the Twilio Number to be set. Channel cards keep their own per-channel credentials; this card is the account-level fallback. The panel is open while it still needs a number and closed once one is saved (click its title to open it).

Model set

The Model Set editor lets administrators override which AI model is used for each processing role. By default, all roles use Default (system) — centrally managed defaults that are optimized and updated automatically for best results. The panel is closed by default — click its title to open it. Its 18 roles are listed in six numbered steps, in the order a message meets them.

Each dropdown lists the available models, by their model ID, grouped by provider — OpenAI, OpenAI (reasoning), Bedrock (Anthropic), Bedrock (Meta), Google, Meta Model API, Meta Model API — TRAINS ON YOUR DATA, DeepSeek (PRC-hosted), Bedrock (Anthropic, global routing), Bedrock (Z.ai), Bedrock (Qwen), Bedrock (DeepSeek), Bedrock (OpenAI open-weight), Groq (OpenAI open-weight), Bedrock (Google weights) and TypeSafe (decisions only — no text). The first option is always Default (system), which delegates the choice to the platform’s centrally managed defaults.

Click Reset to defaults beneath the model selects to return all roles to Default (system).

Re-index

Re-indexing re-reads your website and rebuilds the knowledge base that your Guru uses to answer questions. You should re-index when:

• Your website content has changed significantly.
• You have uploaded or deleted Knowledge Files.
• You want the Guru to learn about new pages or products.

Click Re-index in the top bar and confirm with Reindex. If you have unsaved changes you are asked to save or discard them first, and your first and last name (General) must be filled in. A popup then shows 4 progress stages:

1. Launching Worker — Starting the indexing job.
2. Crawling — Scanning your website pages.
3. Indexing — Processing and embedding content.
4. Deploying — Activating the updated knowledge base.

A progress bar and status tiles show real-time updates via a live streaming connection. Click Show Logs to view detailed log output during the process.

When indexing finishes, the popup shows a Reindex Completed Successfully! message with a Done — Refresh Index Info button. Clicking it — or closing the popup with the × — reloads the page so the updated Indexed pages, Index size, and Last indexed values appear.

Deploying Your Guru to Your Site

To make your Guru visible to visitors, embed a single <script> tag on your website. The widget loads asynchronously, displays a chat icon in the corner of every page, and opens the chat interface when clicked.

Universal Embed Snippet

This single line is all you need:

<script src="https://widget.instantaiguru.com/chat-widget.min.js?v=1.67" defer></script>

Place it in your site's HTML — ideally just before the closing </body> tag, or in the <head> if your platform requires it. The widget auto-configures itself from the settings you saved in this Admin panel: colors, chat icon, welcome message, frequent questions and placement flow through automatically. No per-site configuration needed.

Widget Updates

The ?v= in the snippet does not pin a version. widget.instantaiguru.com always serves the current widget, and browsers check for a newer copy on every page load, so updates reach your site without any change to your embed. Keep the snippet exactly as copied from Appearance → Install.

Platform-Specific Installation

Steps for each are typical — your specific theme or version may vary slightly, but the general pattern (head/footer custom-code injection) holds across all of them.

Shopify

Install the Instant AI Guru app from the Shopify App Store — the widget ships as a theme app extension. Activate it: Online Store → Themes → Customize → App embeds → toggle InstantAIGuru Chat Widget on → Save. The Shopify card’s Activate Widget button opens your theme editor with the widget ready to turn on. No code editing is required.

WordPress

Two paths, in order of preference:

1. Instant AI Guru Chat Widget plugin (recommended) — Plugins → Add New, search “Instant AI Guru Chat Widget”, install and activate. The widget then appears on every page; no code editing is needed.
2. Code-injection plugin — If not using our plugin, add the snippet to the site footer with a plugin such as WPCode. In a classic theme you can instead paste it into footer.php just before <?php wp_footer(); ?> (block themes have no footer.php, and many hosts disable the Theme File Editor).

WooCommerce

WooCommerce runs on top of WordPress, so the WordPress instructions apply directly. Use the Instant AI Guru Chat Widget plugin (recommended) or a code-injection plugin. The widget appears on shop pages, product pages, cart, checkout, and account pages alike.

Squarespace

1. Settings → Advanced → Code Injection.
2. Paste the snippet into the Footer field.
3. Save. The widget loads on every page of the site. Code Injection needs a Squarespace plan that includes it (not the entry plan).

Adobe Commerce (Magento 2)

Two paths:

1. Admin panel (no theme edit) — Content → Design → Configuration → Edit your store view (or Global) → HTML Head → Scripts and Style Sheets → paste the snippet → Save Configuration → flush the cache (System → Cache Management).
2. Theme XML — In your custom theme, edit app/design/frontend/<Vendor>/<theme>/Magento_Theme/layout/default_head_blocks.xml and add <script src="https://widget.instantaiguru.com/chat-widget.min.js?v=1.67" src_type="url" defer="true"/> inside <head>. Requires deploying static content and clearing cache.

Wix

1. Site Dashboard → Settings → Custom Code → Add Custom Code.
2. Paste the snippet, give it a name (e.g., "InstantAIguru Widget"), set placement to Body — end, apply to All pages, and toggle on for Load code on each new page.
3. Apply & Save.

Joomla

Two paths:

1. Custom module — Content → Site Modules → New → Custom. Switch the editor to Toggle Editor (or set it to None) so the <script> is not stripped, paste the snippet, assign it to your template’s footer position (Cassiopeia: footer), set Menu Assignment to all pages, save.
2. Template index.php — Edit your active template's index.php and add the snippet before </body>. Lost on template updates — the module approach is preferred.

Drupal

Two paths:

1. Block (recommended) — Structure → Block layout → Place block → Add custom block. Body: paste the snippet in a text format that does not filter HTML (Drupal’s default Full HTML with CKEditor 5 may still strip <script>; the library route below avoids this). Place in a footer region with visibility = All pages.
2. Theme info file / preprocess hook — For developers: add the asset library via your theme's .libraries.yml or use hook_page_attachments() to inject the script.

PrestaShop

1. Install a code-injection module from PrestaShop Addons.
2. Configure the module to add the snippet to the displayFooter or displayBeforeBodyClosingTag hook position.
3. Save. Alternatively, edit themes/<your-theme>/templates/_partials/javascript.tpl directly — lost on theme updates.

WHMCS

1. FTP / file-manager into your WHMCS installation.
2. Edit your active template's header.tpl at /templates/<your-template>/header.tpl, OR footer.tpl for footer placement.
3. Paste the snippet inside the appropriate location and save. The widget appears on the client area pages. (A ClientAreaFooterOutput hook does the same and survives template updates.)

Webflow

1. Site settings → Custom code.
2. Paste the snippet into the Footer code field (code injected before the </body> tag).
3. Save → Publish your site. Custom code needs a paid plan, and runs only on the published site.

Verifying Installation

After deploying, open your site in an incognito/private browser window. You should see the chat icon appear in the corner you chose once the page has loaded. Click it to open the chat — the Welcome message you set in Appearance → Words should appear.

If the icon doesn't appear:

• Open the browser developer tools (F12 / Cmd+Opt+I) → Console tab. Look for any error messages mentioning chat-widget or instantaiguru.
• Check the Network tab for the chat-widget.min.js request — it should return HTTP 200. If 404, the snippet URL is wrong; if blocked, a content-blocker or CSP is preventing the load.
• If your site has a strict Content Security Policy (CSP), allow https://widget.instantaiguru.com in script-src; https://api.instantaiguru.com and https://stream.instantaiguru.com (plus https://connect.instantaiguru.com if you use Live Support) in connect-src; 'unsafe-inline' in style-src; and blob: in img-src.
• If you have a cookie-consent banner that blocks scripts until consent: ensure the InstantAIguru widget is allowed in the "necessary" or "functional" category, or grant consent to test.

The Chat Widget: What Your Visitors See

Everything above covers how you configure and deploy the widget. This section covers the other side of it: what a visitor can actually do once the widget is on your site. Nothing here needs to be switched on, with the single exception of Talk to a live agent, which appears only when Live Support is configured and an agent is currently reachable.

Header Controls

Left to right, after the header caption:

The Input Row

Each answer carries a thumbs-up / thumbs-down pair, so visitors can rate replies. A thumbs-up marks that reply Correct in the Chat Dashboard; a thumbs-down asks the visitor why, marks it Incorrect, and stores their reason in the Revised Answer column. Clicking the same thumb again clears the rating. A fixed line under the input row reads “Note: The Guru can make mistakes. Check important info.”; it is standard practice for AI assistants and is not configurable.

Attachments

Visitors can send the Guru things to look at rather than describe. Attached files appear as chips above the message box, each with its own remove button, and are sent along with whatever the visitor types:

Moving the Widget

When Let visitors drag the widget is on (see Widget Placement), a visitor has two ways to move it out of their way, which matters when your own page has a button under it:

• Drag it. Dragging by the icon or the header moves the widget. It stays where it is dropped, measured from the nearest corner, so it holds that place when the window is resized.
• Right-click the icon. A menu lists all four corners, with the current one marked and greyed out, so the widget's possible positions are visible rather than something to be discovered by accident.

Wherever a visitor leaves it, the choice is remembered on that visitor's device only. It never affects other visitors, and it is dropped as soon as you change and save placement yourself. Turning the checkbox off removes both the drag and the menu.

Sending Media on the Other Channels

Attachments are not limited to the web widget. Each channel accepts what it can carry:

Flow Designer

The Flow Designer is a visual, IDE-style editor for building JSFE conversation flows and the custom tools they call — the deterministic, scripted logic that lets your Guru run multi-step tasks (OTP verification, payments, account lookups, Shopify actions) reliably instead of relying on the AI to improvise. Open it from the Design Flows button in the admin console’s top bar (visible to a platform administrator, or to a user with the Config permission); it launches in a separate window.

Opening it & how changes are saved

When you click Design Flows, the admin hands the Designer your current flows, tools, global variables, and a short-lived auth token (used by the Test runner and the AI Guru). Nothing is saved automatically — persistence is a deliberate two-step flow:

1. In the Designer, click Save → review the changes → Send to Admin. This hands your edited flows, tools and global variables back to the admin window.
2. Switch to the admin and click its Save button to persist them (written via the Config permission).

All three travel in both directions, so global variables can now be created and edited here rather than only in the stored configuration.

The workspace

The palette, inspector, and test panels are all drag-resizable, and your layout is remembered between sessions.

Working with flows

The flow selector lists every flow (primary flows are marked ★); the ALL / ★ PRI button filters to primary flows only. Use New, Duplicate, and Delete to manage flows — built-in system flows are read-only and cannot be deleted. The palette’s Flow Properties section edits the selected flow’s name, id, version, description, prompt and prompt (ES) (the natural-language description the AI uses to decide when to run a primary flow), the primary flag, and its parameters and variables.

Parameters and allowed values

Each parameter has a name, a type (string, number, boolean, object or array) and a description. A string parameter can also list its allowed values, one per line. When a parameter has allowed values, intent detection accepts only those: any other value is dropped, and the flow asks for it. Values are trimmed, matching ignores case, and clearing the list removes the restriction.

The editor flags the same problems the engine would reject when it loads the flow, so you see them while editing:

• A parameter name declared twice.
• Allowed values on a parameter that is not a string (for example, left behind after changing its type).
• The same value listed twice, ignoring case.

Building on the canvas

• Add a step: hover the trunk and click a green + insertion point, then pick a step type (or Paste).
• Select: click a step (single), Cmd/Ctrl-click to multi-select, Shift-click to range-select, or drag a marquee on empty canvas.
• Edit structure: Cmd/Ctrl+C / V to copy/paste, Delete/Backspace to remove (with confirmation).
• Navigate: two-finger scroll to pan, Ctrl/pinch or the + / − buttons to zoom, Fit to frame everything. Steps auto-arrange — you reorder by inserting/deleting and by moving branches up/down, not by dragging nodes freely.
• Sub-flows: a FLOW step can expand inline (chevron) to preview the called flow; a reboot call shows a jump arrow that navigates to the target flow.

The ten step types

Each insertion offers these step types. The table is a quick reference — for exactly what each does and how conditions and expressions evaluate, see the JSFE repository.

Outcome and Reason

The steps that can end a flow (RETURN, END, DISPATCH, and a SAY that is a flow’s last step) can declare how the conversation ended. The engine records it when the flow finishes.

Both fields accept {{…}} variables. Leave Outcome empty to declare nothing; clearing a field removes it from the step rather than saving an empty value. On DISPATCH the outcome is kept only when no flow matches the message.

Select any step to edit it in the Inspector. CASE and SWITCH get a branch editor (add, reorder, and delete branches; the default branch always stays last). Object and array values — parameters, tool args, and tool schemas — use a recursive tree editor with add/rename/delete and type selection.

Tools

Tools are the actions your flows can call (an HTTP API call, or a platform-approved local function). The tool selector lists them; built-in system tools are marked 🔒 and are read-only. Selecting a tool opens the full-canvas Tool Editor:

Flows invoke tools through CALL-TOOL steps. Create a new tool with New while a tool is selected (or via the AI Guru).

Global Variables

Global variables are values shared by every flow in your account — opening hours, a standard disclaimer, a return window — referenced from flow expressions as {{global_business_hours}} and so on. They belong to the account, not to any one flow.

The editor is the Global Variables tree at the bottom of the Test panel, under Session Variables. Click Test to open the panel. The Global Variables editor works there whether or not the test session starts, and a tenant with no globals yet still gets an editor to add the first one.

Globals sit outside the flow undo stack, so they are tracked separately: editing one turns the Save button blue on its own, is included by Ctrl/Cmd + S, and counts as unsaved work when you close the window. They ride back to the admin with your flows and tools on Send to Admin, and reach the account when you click Save there.

The JSON tab

The Inspector’s JSON tab shows the live {flows, tools} model and doubles as an import/export surface: edit it and click Update, or drag and drop a .flows / .json file onto it and click Update. Either way it accepts a bare flows array or a {flows, tools} object. Invalid JSON is flagged and not applied. System flows and tools are merged in for context but are never saved back as your own.

AI Guru (✨)

The ✨ AI button opens The Flows / Tools Guru — describe a flow or tool in plain language and it drafts one for you. Choose New Flow or Modify Current Flow (and the equivalents for tools), pick a model (Claude Sonnet 4.6 is recommended, with Muse Spark 1.3, GPT-6.1 Sol, GPT-6 Sol, GPT-5.6 Luna, Claude Opus 5.5, Claude Sonnet 5.5, Claude Sonnet 5, Claude Haiku 4.5, GPT-4.1 Mini and two Gemini Flash options also offered, ordered by how reliably they produce a well-formed flow), and watch it stream a live preview with an AI Response notes panel; click Done to apply. When modifying, it computes the flow’s dependency set and marks any flow that is also used elsewhere as read-only, so a change can’t silently break another flow. The AI Guru needs the auth token, so open the Designer from Design Flows.

Testing a flow

Click Test to open the bottom panel and start a live session: the Designer loads the real JSFE engine and runs your flows merged with the system (and Shopify, if enabled) libraries against the backend.

Saving your work

The Save button turns blue when you have unsaved edits. Clicking it opens Review Changes: a diff of the added, removed and changed flows, steps and tools, plus a Global Variables section for any globals you edited. Flows are listed by name; each changed step is a drillable row you can open to see the individual fields.

Send to Admin hands the work back to the admin window and a toast reminds you to click Save in the admin to persist it. The admin only stages what actually differs: if you open the Designer and send without editing anything, it says “nothing changed — nothing to apply” and leaves the admin’s Save button dark.

There is no autosave; edits live in memory until you send or download them. (In standalone mode, Save downloads a .flows file instead.)

Keyboard shortcuts

Troubleshooting

Chat Dashboard

The Chat Dashboard provides a comprehensive view of all conversations your Guru has had with visitors. Open it from Chat Dashboard in the admin console’s left menu; it opens in a new tab.

Controls & Filters

Date Range

View Mode

Toggle between two display modes:

• Normal (default) — Shows 20 essential columns for faster loading and easier scanning.
• Advanced — Shows 30 columns including technical details like Log ID, version, token counts, model info, RAG timing, and chat context.

If CSAT or an API call log is connected, CSAT, CSAT Note and API Calls columns are added at the end in both modes. Switching modes resets hidden columns and sorting and reloads the logs. Beside the mode switch, the CSAT and API switches (both on by default) decide whether this Guru’s CSAT surveys and API call log are pulled in with the logs; turn one off if its source is slow.

Loading Controls

While a load is running, the Load Logs button shows a spinner; hover it and it turns into a pause control. Click to pause; the button then reads Resume and continues where it stopped. Clicking into a date field also pauses the load. A red Cancel button appears while a load is running or paused: it abandons the load and clears the results, and the 60-second auto-refresh stays off until you load again.

Theme Toggle

Click the moon/sun icon to switch between light and dark themes. The preference is saved to your browser.

Outbound calls and campaigns

Shown only to users with the Outbound permission. A Direction selector (All, Inbound or Outbound) filters the conversations; choosing Outbound adds a Campaign picker to narrow them to one campaign. The Campaigns button opens the Campaigns view.

The Campaigns view first lists your campaign runs, one row each. Click a run to open it; Close Campaigns returns to the logs.

An open run shows its Status, when it last placed a call and when its window ends, with Refresh, Export CSV and a List picker for its earlier daily lists. ← All campaigns returns to the runs. Tiles sum it up:

Below the tiles is one row per contact: Name, Phone, Lang, Outcome, Attempts, Last attempt, Talk time (for a reached contact) and Conversation.

Conversation says how a reached contact’s call ended, and how many turns it took: Transferred to an agent, Goodbye, Caller hung up, or Conversation for a call that ended any other way. Click it to open the transcript. It reads not in the loaded dates until the dashboard’s loaded dates (see Date Range) cover that call. Click a contact to see each attempt: when, the call status, who answered (human, or the answering-machine verdict), how long, and its result. Export CSV downloads the list with every contact’s state, outcome, reason, attempts, last attempt, talk time, conversation and the list’s own columns.

Statistics Summary Bar

The colored badges below the controls show counts for different interaction categories. They serve a dual purpose — information display and interactive filters:

Non-Clickable Statistics

Clickable Filter Badges

Click a badge to include or leave out its category. A row stays visible while it matches any included category, so switching off one badge often hides little; to isolate a category, Ctrl+Click (Cmd+Click on Mac) it, and Ctrl+Click again to bring every category back.

The JSFE Badge — Who Wrote the Reply

Every reply is authored by the AI, answering from your knowledge base; by the JSFE workflow engine, reading out a line you scripted in the Flow Designer; or — shown as PP — by the pre-processing step that answers some messages before the AI runs. The purple JSFE badge at the end of the badge row counts the scripted ones, in the format total (conversations involved) — so 2 (1) means two scripted replies, inside a single conversation.

Log Table

The main table displays all log entries matching your date range and active filters. Each row represents a single interaction (one user question and one AI response).

Normal Mode Columns (20)

Additional Advanced Mode Columns

When Advanced view mode is enabled, these additional columns appear:

Table Interactions

• Click a column header to sort: ascending → descending → natural order (3-state cycle).
• Right-click a column header for a menu: Hide Column, Filter… (see Per-Column Filtering below), or Clear Filters.
• Hover over a truncated cell to see a tooltip with the full text.
• Right-click a truncated cell to open the full text in a modal. For Chat Context columns, this shows formatted chat bubbles.
• Click a Full Chat button to view the entire conversation thread — including the opening greeting bubble and a timestamp on every message.
• Rows are color-coded to match their category (green for correct, red for incorrect, orange for incomplete, etc.).

Reading a conversation: which turns were scripted

Inside the Full Chat modal, a reply written by a flow rather than by the AI is labelled FLOW instead of ASSISTANT and carries a purple stripe down its left edge. The interaction you opened the modal from keeps its green current outline at the same time, so a scripted current turn shows both marks — purple stripe, green outline.

This is the same fact as the JSFE badge and the Src column, read at conversation level: it shows where a scripted flow took over and where it handed back, which is usually what you want when a conversation went wrong and you need to know whether to fix a flow or the knowledge base.

Reading a conversation: what happened after a transfer

A call transferred to your live agent line ends with one line saying how the transfer went: whether your agent line answered, how long it took to answer, how long the caller stayed on it, and who hung up: the caller, or your side (an agent, or your contact center’s own queue or message). A transfer your line never answered says so, with the reason: no answer, busy or failed. Transfers before October 21, 2026 show no such line.

Per-Column Filtering

Beyond the quick category badges, you can build precise filters on any column. Right-click a column header and choose Filter… to open the Filter Logs dialog. Each condition is a column, an operator, and a value; click + Add Condition to add more, and choose whether a row must match ALL or ANY of them. Right-clicking another header adds a condition for that column to the existing set — filters accumulate, they are not replaced.

Conditions are matched against the value shown in each cell, so From/To on Total Time filter by milliseconds — pairing them (e.g. Total Time From 100 To 500) builds an inclusive range. Click Apply to filter the table. Active conditions appear as removable chips above the table, and each filtered column shows a 🔎 cue in its header. Filtering also flows through to the Analytics Dashboard charts and every export. To clear filters, delete individual chips, click Clear all on the chip bar, or right-click any header and choose Clear Filters.

Export

Three export formats are available, each respecting your current filters and visible columns:

Analytics Dashboard

Click Analytics Dashboard to open a full-screen overlay with charts and statistics based on your currently loaded and filtered logs.

Statistics Cards

At the top, 12 summary cards show key metrics:

• Total Interactions — Total number of log entries.
• Unique Users — Distinct visitor count.
• Total Conversations — Unique thread count.
• Multi-turn Conversations — Threads with more than one exchange.
• Multi-turn Rate — Percentage of multi-turn conversations.
• Avg Conversation Length — Average exchanges per thread.
• Longest Conversation — Maximum exchanges in a single thread.
• Accuracy Rate — Percentage of interactions not marked as incorrect.
• Avg Response Time — Average end-to-end response time.
• Countries — Number of distinct countries.
• Avg Prompt Tokens — Average input token usage.
• Avg Completion Tokens — Average output token usage.

Charts

The analytics dashboard includes up to 14 interactive charts. Some charts have a toggle to switch between "By Interactions" and "By Conversations" views:

1. Usage by Hour of Day — Bar chart showing when visitors are most active.
2. Answer Quality Distribution — Doughnut/bar chart of correct vs. incorrect vs. other categories. Toggle: by interactions or by conversations.
3. Countries Analysis — Horizontal bar chart of top 10 countries. Toggle: by interactions or by conversations.
4. Usage Trends — Line chart of daily interaction volume (last 7 days).
5. Response Time Distribution — Bar chart with time buckets (0–1s, 2–5s, 6–10s, etc.).
6. Conversation Length Distribution — Pie chart showing how many conversations are 1 turn, 2 turns, 3–4, etc.
7. Conversation Quality by Length — Bar chart of accuracy rate by conversation length category.
8. Model Usage — Stacked bar showing, for each pipeline role (qualifier, ranker, guru, and the JSON/guru intervention and fallback roles), which AI model(s) handled it — so you can see the model mix per role.
9. Domain Activity — Doughnut chart showing activity per domain (hidden for single-domain accounts). Toggle: by interactions or by conversations.
10. Channel Distribution — Pie chart of Web, WhatsApp, SMS, Email, Phone, and App channels. Toggle: by interactions or by conversations; by conversations, phone calls are split by how they ended: Live Agent, Goodbye, Call Ended, Switched to SMS or Other.
11. RAG vs Google Sources — Pie chart showing the mix of RAG-only, Google-only, both, or no sources.
12. Token Usage Trends — Line chart of average prompt and completion tokens per day.
13. Accuracy Trends — Line chart of accuracy rate, correct %, and incorrect % over time.
14. User Engagement Patterns — Bar chart of sessions bucketed by depth — Casual (1–2), Regular (3–5), Active (6–10), or Power (11+) interactions per session — plus a Repeat Users bar counting users with 2+ sessions.

Click Close Analytics to return to the log table view.

Saved Views

Save your current filter and display configuration for quick access later:

• Save View — Saves the view mode, hidden columns, sort, and the badge filter states under a name, in this browser only (column filters, the JSFE badge and the date range are not saved).
• Load View — Pick a view in the dropdown and click Load View.
• Reset to Default — Pick it in the dropdown and click Load View to show all columns, clear sorting and turn every badge back on.

Keyboard & Mouse Shortcuts

Chat Dashboard

Admin Console

Chat Widget

Frequently Asked Questions

How do I connect Twilio for SMS and Voice?

In Channels, click Add Twilio number, then Connect your Twilio account. Approve InstantAIguru in Twilio, pick or buy a number, and calls are answered right away. For texting, fill in the Texting registration in the same dialog and we file it with US carriers for you. See Twilio Setup.

Why isn’t my chat widget appearing on my site?

Open your site in a private window and confirm the embed snippet is present before the closing </body> tag. Check the browser console for errors, that the script URL loads, and that a Content-Security-Policy or cookie-consent gate isn’t blocking it. The widget should appear once the page has loaded. See Verifying Installation.

How do I send post-call CSAT surveys, and what do I need?

In Integrations, turn on the CSAT — Post-call Survey card. By default we host CSAT for you (use Create CSAT Admin Login to view results); if you self-host, tick I self-host CSAT and paste your CSAT Site URL and CSAT Secret. Then set delivery: an A2P-registered Twilio number under SMS delivery (you can copy credentials from an existing SMS number) and/or Send CSAT Email. After a voice call the Guru then texts and/or emails the customer a survey link. See CSAT — Post-call Surveys.

How do I reveal a hidden Auth Token or secret so I can copy it?

Masked secrets — the Twilio Auth Token on SMS, Voice and CSAT and in Settings › Twilio account, the CSAT Secret, the Live Support secret, and the Shopify and ShipStation keys — have a Show button beside or beneath them. The WhatsApp Business Token is shown shortened (first and last ten characters); hover it to see the full value.

Why won’t my changes save?

Saving is blocked by field validation before anything is written: Matching documents to evaluate (Settings) must be 1–10; a self-hosted CSAT needs its Site URL, Secret and at least one delivery method (an SMS number with its SID and Auth Token, or Send CSAT Email); an enabled integration needs its required key or URL; Enforce and Forbid references cannot both be ticked; every user you edited in Users needs a first name, a valid email, and an email nobody else already uses; and the Outbound Call Agent needs at least one ticked line, and each campaign a name, call context, and a greeting and disclosure for each language. The form jumps to the offending field. Saving also fetches the latest server config first and offers a conflict-resolution dialog if another user changed the same fields. If Save is not purple, the console sees nothing to write. When it is purple, Exit or Re-index offers Review Changes, which shows exactly what Save would write. See Saving Changes.

What does “Read linked pages on other sites” do?

In General, turning on Read linked pages on other sites follows links that leave your domain while your site is read — useful when your knowledge spans linked external pages. Leave it off to read only your own domain. It takes effect on the next Re-index.

Why does a channel card say “Configuration Required”?

That banner means the channel was added from your subscription but is still missing credentials. Fill in the highlighted fields (for example, the Twilio Account SID and Auth Token) to activate it. See Channels.

How do I reply to customers from my own domain by email?

On an Email channel, type your address (e.g., [email protected]) into the From Address field and click Verify Domain. Add the three DKIM CNAME records and merge the Amazon SES include into your existing SPF record (do not add a second SPF). A status badge shows when the domain is verified. See Branded From Address.

Who can change the AI Model Set?

Only a platform administrator. The Model set panel in Settings is also shown, read-only, to users with the Config permission; everyone else does not see it. See Model Set.

How do I set live-agent transfer hours for phone calls?

Enter a Live Agent Phone Number on the Voice channel and the Live Agent Service Hours editor appears. Set a timezone and add one or more time ranges per day; once any day has hours, days with no ranges are treated as closed and won’t transfer calls; with no hours set on any day, transfers are not time-limited. See Live Agent Service Hours.

What are the Upload Flows, Upload Tools, and Design Flows buttons?

These top-bar buttons (shown to a platform administrator or to a user with the Config permission) manage the Guru’s interactive conversation flows and custom tools: Upload Flows and Upload Tools import JSON definitions, and Design Flows opens the visual Flow Designer to build them interactively — along with your global variables. All three routes stage the result as an unsaved change; nothing is written until you click Save, and an import identical to what is already stored applies nothing. See Flow Designer.

A new user never got their invitation. How do I resend it?

Open Users and click Resend invite on the user’s card (it is marked Invited). You can send it as many times as you need; nothing else about the account changes. A card marked Not saved yet has no account yet: click Save, and the invitation goes out by itself. (An older user shown with neither mark has a Send invite button instead.)

What does the Read Only permission actually allow?

Everything on the console stays visible and readable, and every control that would write something is switched off — forms, buttons, the flow and tool uploads, the Flow Designer, and Save. The top bar shows a Read-only badge so the disabled controls read as intentional. Two things still work: Re-index, which writes no configuration, and changing your own password, so an invited read-only account can still be activated. The server enforces the same restriction independently, so it holds even if the page is tampered with. See Permission Checkboxes.

What’s the difference between the Sole Proprietor and Standard A2P 10DLC paths?

Twilio routes your SMS registration by whether your company has a business/tax registration number. The Sole Proprietor path (no EIN) is limited to one campaign and one number, with low throughput, and the owner must confirm a code sent to their mobile; the Standard path requires a registered business and full Brand vetting but unlocks higher limits. See Sole Proprietor vs Standard Path.