01
Section
Problem
Foundation
A demo form should tell you who is interested, what they want, and how quickly to respond.
Use Cases
Demo Requests
Track product interest and move it into a visible follow-up workflow.
Demo requests should not disappear into a generic inbox. EnterestOS turns them into a tracked submission with a clear next step.
At a glance
What EnterestOS keeps visible
Always visible
Tracked
Who responded
Tracked
What needs a reply
Tracked
What is waiting
Tracked
What is completed
Tracked
Which projects are active
Tracked
What changed recently
02
Section
Solution
Priority
EnterestOS keeps the form intact and turns the submit into a submission stream the team can actually work from.
03
Section
Before EnterestOS
Lifecycle
Demo requests land in email, get buried, and are easy to forget until the lead goes cold.
04
Section
After EnterestOS
Closure
Every request is visible in Reply, then Waiting, then Done, so the team never loses the thread.
05
Section
Workflow
Visibility
The lifecycle stays small so attention stays clear.
Reply ↓ Waiting ↓ Done
06
Section
Steps to Set Up
Visibility
Use the shortest implementation path first.
- Create a project for the product.
- Connect the demo form or screenshot.
- Generate the integration prompt.
- Paste it into your builder or app.
- Submit one test request and verify it appears in the inbox.
07
Section
Form Structure
Visibility
The canonical demo request usually captures enough context to route the lead quickly.
export function DemoRequestForm() {
return (
<form>
<input name="name" />
<input name="email" />
<input name="company" />
<textarea name="message" />
<button type="submit">Request a demo</button>
</form>
);
}08
Section
trackResponse() Call
Visibility
Track the submit once the original form submit succeeds.
await enterestos.trackResponse({
type: 'demo_request',
payload: { name, email, company, message },
});09
Section
Best Practices
Visibility
Keep the form simple and keep the submission visible.
- Do not redesign the existing page.
- Do not block the form if tracking fails.
- Use a small set of submission statuses.
- Keep the project tied to the product that owns the lead.
010
Section
Result
Visibility
The team knows who responded, what they want, and what happens next.
011
Section
Common Questions
Visibility
Focus on the outcome, not the schema.
- How do I keep the existing design? Use the prompt to wire tracking only.
- What submission type should I use? Start with demo_request and refine later.
- What if tracking fails? Keep the form submit working.