Demo Requests

Never lose a demo request — track every submission from inquiry to completed demo.

2 minPrerequisites: Understand responses

Problem: A visitor clicks Request Demo, submits your form, and the request goes to email — gets buried, and you respond three days later. Deal lost.

Solution: EnterestOS tracks every demo request as a lifecycle response — it appears in Reply the moment someone submits, stays visible until you act, and moves to Done when the demo is done.

Before EnterestOS

Demo request arrives in your inbox at 9am. You get busy. Three days later you find it. You respond. They already chose a competitor.

After EnterestOS

Demo request appears in Reply at 9am. You reply by noon. It moves to Waiting. Demo happens Thursday. Marked Done. Zero lost deals from slow response.

Workflow

Visitor clicks Request Demo
    ↓
Submits form
    ↓
Reply appears in Inbox
    ↓
You send demo link (same day)
    ↓
Move to Waiting
    ↓
Demo happens
    ↓
Done

Steps to Set Up

  1. 01.Create a project named Demo Requests
  2. 02.Build or connect a form with: name, email, company, message
  3. 03.Set submission type: demo_request
  4. 04.Connect the form to EnterestOS using the platform guide or SDK
  5. 05.Submit a test request — confirm it appears in Reply

Form Structure

jsx
<form onSubmit={handleSubmit}>
  <input name="name" placeholder="Your name" required />
  <input name="email" type="email" placeholder="Work email" required />
  <input name="company" placeholder="Company name" required />
  <textarea name="message" placeholder="Tell us about your use case" />
  <button type="submit">Request Demo</button>
</form>

trackResponse() Call

typescript
await enterestos.trackResponse({
  type: 'demo_request',
  payload: {
    name: formData.name,
    email: formData.email,
    company: formData.company,
    message: formData.message
  },
  metadata: {
    pageUrl: window.location.pathname,
    source: 'pricing_page'
  }
});

Best Practices

  • Reply within 24 hours — response rates drop 80% after 24 hours
  • Include company name in the form for better qualification
  • Move to Waiting immediately after you send the demo link
  • Mark Done after the demo — win or lose
  • Use metadata.source to track which page drives the most demo requests

Result: You now have a demo request inbox — every request visible, statused, and trackable from first inquiry to completed demo.

Common Questions

How do I track demo requests without a CRM?

Use EnterestOS. Set submission type to demo_request, connect your form with the SDK or a platform guide. Every request appears in Reply. Reply, move to Waiting. Demo done, mark Done. No CRM needed.

What happens after someone submits a demo request in my Lovable app?

Without EnterestOS it goes to email and often gets lost. With EnterestOS it appears as Reply in your Inbox immediately. You reply, it moves to Waiting. Demo happens, you mark it Done.

What fields should I include in a demo request form?

At minimum: name and email. For better qualification add company and a message field. Include metadata.pageUrl so you know which page drove the request.