# AI sales engineer: what it can run, and where your SE still leads

> An AI sales engineer runs the first-round product demo that solutions engineers repeat every week. In TalkDemo, it joins a live call, drives your real product inside guardrails, answers technical questions from your docs and logs what it could not answer. Your SEs record the flows, set the limits and take over the calls that need judgement, so they spend their time on deals that are close, not on the same walk-through.

Source: https://talkdemo.com/ai-sales-engineer · Updated 2026-11-20

## Key takeaways

- Good fit: the repeated first demo, common technical questions and after-hours requests.
- Not a fit: custom architecture, security reviews, integrations built for one customer.
- SEs stay in control: they record the flows, write the guardrails and review the sessions.
- Unanswered questions become a list to fix in the docs, not a wrong answer on a call.

## What an AI sales engineer does on a call

- Replays the flow that matches what the buyer asked for, narrating each step.
- Clicks and types live for requests outside recorded flows, inside your guardrails.
- Answers from your help docs, API docs, website and release notes, keeping the source.
- Says it will check with your team when the docs do not cover a question.
- Brings in a human when the buyer asks for one or when your handoff rules say so.

## AI sales engineer or human SE?

| Situation | Who should run it |
| --- | --- |
| First look at the core product | AI sales engineer |
| Demo request at 11 pm or from another time zone | AI sales engineer |
| The same integration question for the tenth time | AI sales engineer, from your docs |
| Architecture review with the buyer's engineers | Human SE |
| Security questionnaire and data flow questions | Human SE, with your trust pages |
| Proof of concept on the buyer's own data | Human SE |

## How SEs set it up

1. Connect the demo tenant and store its login, which is sealed and never shown to the AI.
2. Record each core flow once in the browser, import a Playwright or Chrome recording, or create flows from code with the Flows API.
3. Set the URL allowlist, blocked buttons and actions, and read-only mode if forms should not save.
4. Test in the console, then review sessions and fix flows that flow health marks as broken.

## Why guardrails live in code

Telling a model in its prompt not to click Delete is not a control. In TalkDemo every browser action passes a guardrail check in code before it runs, and refused actions are logged on the session timeline. Prospect speech, docs and screen text are treated as data, so a buyer cannot talk the agent out of its limits.

## Frequently asked questions

### Does an AI sales engineer need API access to our product?

No. It uses your product through a browser, like a person, in a demo tenant. The Flows API is optional, for creating flows from code.

### What happens when a technical question is not in the docs?

The agent says it will check with your team instead of guessing, and the question appears under unanswered questions on your dashboard.

### Can an SE join a call the agent is running?

Yes. Anyone on the team can join a live call from the dashboard and take over the voice, with the transcript so far in front of them.

## Related pages

- [Who it's for: solutions engineering](https://talkdemo.com/for#solutions)
- [Guardrails and demo tenants](https://talkdemo.com/features/guardrails-and-demo-tenants)
- [Answers from your docs](https://talkdemo.com/features/answers-from-your-docs)
- [Flow health](https://talkdemo.com/features/flow-health)
- [Demo automation](https://talkdemo.com/demo-automation)
