EnterestOS sits after your form. Every submission gets a status. Every status moves forward until resolved.
The big picture
EnterestOS does not replace your form, your email tool, or your CRM. It is the layer in between that tracks what happens to every submission.
01 — Your form
01A visitor fills out your existing form on Lovable, Bolt, Cursor, v0, or any React app and clicks submit. Your form keeps its existing design, validation, and logic. Nothing changes for the visitor.
02 — EnterestOS
02EnterestOS receives the submission data via the SDK. A submission record is created in your Inbox instantly — with the person's name, email, message, timestamp, and source page. Status is set to Reply automatically.
03 — You
03You see the submission in Reply. You reply to the person — in email, Slack, or however you normally communicate. You move the submission to Waiting, then Done when finished. Nothing gets lost.
EnterestOS is not a form builder, email tool, or CRM. It is the structured inbox that sits after your form and before your reply — so every submission has a status and nothing disappears into email.
The lifecycle
Every submission starts at Reply and moves forward as real actions happen. You control when it moves.
Someone submitted your form. They have not heard from you yet. Every new submission starts here automatically — you cannot skip it.
You sent a demo link, meeting invite, or follow-up message. The next step depends on them. Move here after you act so Reply stays clean.
The demo happened, the deal closed or passed, the showing was done. Mark Done and it moves out of your active work — but stays searchable.
State 01
Reply
Submission arrived. Action required from you.
State 02
Waiting
You replied. Waiting on their next step.
State 03
Done
Conversation finished. Archived.
Submissions can move backwards too — if a completed deal re-engages, reopen it to Reply.
Integration
You do not rebuild your form. You do not change your design. You add one function call after your form submits.
Go to your Inbox, click New Project, name it after what it tracks (e.g. Demo Requests). Copy the project key — you will need it in the next step.
Upload a screenshot of your form or paste your form code. EnterestOS reads the field names and generates a copy-pasteable prompt specific to your platform — Lovable, Bolt, Cursor, Claude Code, v0, or Replit.
Paste the generated prompt into your AI builder's chat. It installs the SDK, adds the trackResponse() call after your form submit, and preserves everything else exactly as it is.
Fill in your form and submit it. Open your Inbox and confirm the submission appears under Reply. If it does, you are done. Every future submission will appear the same way.
Real submissions start appearing. Reply to each one in your normal email or Slack. Move them from Reply to Waiting to Done as the conversation progresses.
If you built with an AI tool
Upload your form screenshot. EnterestOS generates a Lovable, Bolt, or Cursor prompt. Paste it. Your AI builder handles the rest. Design untouched.
If you have custom React
npm install @enterestos/sdk
Create a client with your project key. Call trackResponse() after your form submit handler succeeds. Wrap in try-catch.
What you never need to do
No new form. No database setup. No redesigning. No redirecting visitors. Your existing form, your existing design, your existing backend — all unchanged.
Under the hood
Four things happen the moment someone submits your form.
01
When your form calls trackResponse(), EnterestOS receives the payload — your form fields exactly as submitted. Name, email, message, and any other fields you include.
02
Your project key tells EnterestOS which project the submission belongs to. If you run multiple sites, each has its own project key and its own inbox. Submissions never mix.
03
Optional metadata — which page the form was on, which campaign drove the visitor, which referrer sent them — is stored alongside the payload so you know where each submission came from.
04
The submission is always created with status reply. You cannot override this. The lifecycle starts here because the person has not been contacted yet — that is the truth.
Real example
Marcus visits your SaaS product page, fills in the demo request form, and submits. Here is exactly what happens next.
He fills in name, email, company, and a message: "Interested in a demo — can we schedule this week?" He clicks Request Demo.
EnterestOS receives the payload, creates a submission record under your Demo Requests project, and it appears in Reply immediately. You see Marcus's name, email, company, and message — all there.
ReplyYou send Marcus an email with a Calendly link: "Would Thursday 2pm work?" You move the submission to Waiting in your Inbox. Reply is now clear.
WaitingMarcus replies and books the slot. The submission stays in Waiting — you are still expecting a future action (the demo itself).
Marcus signs up for Pro after the demo. You move the submission to Done. It is archived. Nothing in Reply. Nothing hanging. The whole thread is visible if you ever need to reference it.
DoneThe code that made this happen
await enterestos.trackResponse({
type: 'demo_request',
payload: {
name: 'Marcus Johnson',
email: '[email protected]',
company: 'Acme Inc',
message: 'Interested in a demo'
},
metadata: {
pageUrl: '/pricing',
source: 'pricing_page'
}
});Questions
Straight answers. No marketing language.
Platform compatibility
If it has a form that submits, EnterestOS can track it. Keep your existing app, your existing design, your existing stack.
Connect in about 5 minutes. Works with your existing form. Nothing gets rebuilt.
Start tracking your first project freeNo credit card. Free plan includes 1 project and 50 submissions per month.