Response Types

Label your responses for better organization.

⏱ 2 minPrerequisites: Understand trackResponse()

Problem: All submissions look the same in your Inbox if you do not label them — you cannot tell a demo request from a waitlist signup at a glance.

Solution: Set a type string on every trackResponse() call. It labels the response and lets you filter and understand your Inbox as submission volume grows.

Built-in Types

typescript
type ResponseType =
  | 'demo_request'
  | 'property_inquiry'
  | 'agency_lead'
  | 'waitlist_signup'
  | 'booking_request'
  | 'contact_request';

Custom Types

Any string is valid. Use custom types when built-in types do not describe your workflow.

typescript
await enterestos.trackResponse({ type: 'support_request', payload });
await enterestos.trackResponse({ type: 'partnership_inquiry', payload });
await enterestos.trackResponse({ type: 'beta_application', payload });

Choosing a Type

WorkflowRecommended Type
SaaS demo formdemo_request
Property showing requestproperty_inquiry
Agency quote requestagency_lead
Pre-launch waitlistwaitlist_signup
Appointment bookingbooking_request
General contact formcontact_request
Support ticketsupport_request (custom)
Partnership inquirypartnership_inquiry (custom)

Result: You now know how to label responses so your Inbox stays organized as submission volume grows.

Common Questions

What submission types should I use in EnterestOS?

Use built-in types (demo_request, waitlist_signup, property_inquiry, etc.) when they match your workflow. Use any custom string for anything else. The type is a label — it does not change how the lifecycle works.

Next

Error Handling →