Skip to content
TalkDemo
Product and flows

Connect your demo tenant

Give TalkDemo a dedicated demo tenant for live product mode. Credentials are sealed, never shown to the AI, and the browser stays on hosts you allow.

Live product mode needs somewhere safe to click. That is your demo tenant: a separate account of your product, filled with sample data, that prospects can see without risk. TalkDemo signs a cloud browser into it at the start of every session and closes the browser at the end.

Who can do this: Admin saves the demo login and the reset signing secret. Admins and Members set the tenant address, allowed hosts and reset method. Nobody can read the credentials or the secret reference back. · Plans: Growth and up.

Before you connect

  • Create a demo tenant or workspace in your product. Fill it with realistic sample data, never real customer data.
  • Create a demo user for TalkDemo. Give it the least access a demo needs (a member, not an owner).
  • Sign in as that user once yourself and close any welcome tour or "what's new" dialog, so every demo starts on a clean screen.
  • Turn off two-factor sign-in for that user, or add its time-based code secret with the login.

Connect it

  1. Open Agents, choose the agent and open Product.
  2. Enter the Demo tenant address, the page the demo opens on, such as https://demo.yourproduct.com/w/demo. It must use https.
  3. Enter the Login page if sign-in happens on a different page.
  4. Under Other hosts and paths the browser may load, add any other host the demo needs (a single sign-on or bot-check host such as challenges.cloudflare.com, or a reports domain). To keep the browser inside one area of your app, add paths such as /w/demo/. The tenant's host is always included.
  5. Click Save demo tenant.
  6. Under Demo login (admins only), enter the username and password, then click Save demo login. They are sealed straight away and never shown again, not even to you.

Keep the login in AWS Secrets Manager instead

If your team keeps the demo login in AWS Secrets Manager with TalkDemo, an admin can point to it instead of pasting it:

  1. Under Demo login, choose AWS Secrets Manager under Where the login lives.
  2. Enter the Secret reference: aws-sm:// followed by the secret name, or the secret's full ARN. The name must start with the prefix shown under the field (talkdemo/demo-logins/ and your workspace's id), and the secret must be in your workspace's data region (Mumbai, ap-south-1, for India).
  3. The secret's value must be JSON with username and password, and totpSecret if the demo user has two-factor sign-in, for example {"username": "demo@yourproduct.com", "password": "..."}.
  4. Click Save secret reference. TalkDemo reads the secret once to check it, then forgets the value.

At the start of each session TalkDemo reads the login once, uses it to sign the browser in and keeps nothing. If the secret can't be read at that moment, the live screen isn't shown and the agent carries on answering questions. If the option says "Secrets Manager isn't set up for this workspace; paste the login instead", paste the login as in step 6 above.

At the start of each session TalkDemo's platform opens the login page in the session's cloud browser, fills the first email or username box and the password box, submits the form once its button is ready, and checks the browser left the login page. Only then does it hand the signed-in browser to the AI agent, which never receives the login itself. Sign-ins with several steps (a "Next" button between email and password, a one-time code) need recorded sign-in steps: record the sign-in with Playwright codegen or the Chrome Recorder, import it on Flows, and as an Admin click Save as the Product tab's sign-in in the preview (see Import a flow recording). The steps are saved with placeholders such as {{credential.password}}, never what you typed, and are listed under Sign-in steps on Product, where an Admin can click Use the standard sign-in form to remove them. If you move the login page to another address, recorded steps are dropped and the standard sign-in is used.

What prospects see

The prospect hears the greeting straight away while the browser signs in, with a calm "Opening the live product" screen. The shared screen switches to your product only after sign-in, so a prospect never sees the login page or the credentials being typed. The screen is shared at 1280 by 720, at 15 to 20 frames per second. The cloud browser runs in the provider's region nearest your workspace (Singapore for India, which has no region of its own yet), with the provider's session recording and logging turned off, and it is closed within a few seconds of the call ending.

Reset demo data after each session

Every session already gets its own browser, which is signed out, cleared and closed when the session ends, so nothing one prospect saw reaches the next. Demo data a prospect changed in your tenant is a different matter. Choose how it goes back to normal under After each session:

OptionHow it works
No reset (read-only demo data)Nothing is restored. Fine when guardrails keep the agent read-only.
Call a reset webhook after each sessionTalkDemo sends a signed POST to an address on your side after every live product session that used the tenant. Your endpoint restores the data.
Restore a snapshot after each sessionStored for now. Ask us to set it up.
Run a reset script (set up with our team)Stored for now. Ask us to set it up.

Set up the reset webhook

  1. Under After each session, choose Call a reset webhook after each session, enter the Reset webhook address (public https, no secrets in it) and click Save demo tenant.
  2. A Reset webhook panel appears. As an Admin, click New signing secret and copy the secret. It is shown once.
  3. On your endpoint, check the X-TalkDemo-Signature header exactly as for our other webhooks: compute the HMAC-SHA256 of <t>.<raw body> with the secret and compare it with v1, and refuse timestamps more than 5 minutes old (see Webhooks).
  4. Click Send test reset. The panel shows what your endpoint answered.

The body carries ids and times only, never prospect details:

{"id": "rst_<session id>", "type": "demo.reset", "created": "2026-11-19T10:00:00.000Z", "workspaceId": "…", "data": {"envId": "…", "agentId": "…", "sessionId": "…", "endedAt": "…"}}

Answer with any 2xx status. If your endpoint fails or can't be reached, TalkDemo tries again over about 8 minutes, then records the failure in your audit log and on the panel. Retries carry the same X-TalkDemo-Delivery id, so you can ignore repeats.

Faster start (optional)

By default each call starts a new browser and signs it in, which takes a few seconds while the agent greets the prospect. Warm browsers, which keep 1 to 3 browsers open and already signed in so the product appears sooner, are coming soon. Until TalkDemo turns them on for your account, Faster start → Warm browsers says "Not available on this deployment yet" and stays Off (start a browser for each call). Once on, each warm browser is used for one call only, then closed and replaced; they run all the time and use cloud browser minutes even when nobody calls, so they stay off unless an Admin chooses them.

Privacy

Your demo tenant should hold sample data only. The agent is blocked from typing anything that looks like an email address or phone number, so prospects' details never land in your tenant.

Frequently asked questions

Can I see the stored password?

No. Credentials can be replaced or removed, never read back. To change them, enter new ones and save.

Can I see which secret a reference points to?

No. Like a pasted login, the reference is write-only on the Product tab. Saving a new one, or pasting a login, replaces it.

Does the AI agent ever get the password?

No. TalkDemo's platform signs the browser in before handing it to the agent, so the login never reaches the agent or the AI model. The agent can only see that it is signed in.

What if the login stops working?

The agent tells the prospect the live screen isn't available and carries on answering questions. The Product tab shows Login failing with the step that failed. Check the login, the sign-in steps and the session's timeline. See Flow health and broken flows.

ShareXLinkedIn Email

View as Markdown

Something unclear or missing? Tell us