Four audiences, one intake architecture
Sellers, buyers, wholesalers and professionals need different questions but the same treatment after submission: store it durably, notify the owner, write it into the universal inbound pipeline, then copy it into the pipeline for its type with a linked identifier.
That structure means adding a fifth form later is a configuration change, not a rebuild.
What to capture at submission
- — The page path the submission came from.
- — UTM parameters, gclid and fbclid where present.
- — A submission type, so routing is explicit rather than guessed from the content.
- — A short need signal in plain language for the daily review list.
- — Timestamp and a stable submission id used for idempotency.
Notifications without dependence on notifications
Email alerts are the most fragile part of the chain — spam filtering, provider outages and full inboxes all break them. Treat the notification as a convenience and the written record as the system of truth. If the notification fails, the record still exists and still appears on the daily list.
Verification and honesty in the routing
A website submission is a claim, not a credential. New buyers should be written as unverified until funding and closing capability are confirmed by a human, and new professionals should enter the partner list without a verified marker. Automatic verification is how bad matches get made at speed.
Request an operations fit review
Tell TKC what you need. We review the fit and come back with one clear next path.
Request an operations fit review