Deployment-specific public website intake
Understand the protected website submission endpoint, validation, customer matching, case creation, emails and deployment limits.
Guides in this workflow
Follow the guide that matches the exact action, filter, menu change or issue.
Understand the deployment-specific public intake
Recognise that the supplied endpoint is hard-restricted to one tenant path and is not a generic public form builder.
Use the required POST submission
Submit the website form by POST to the configured protected endpoint.
Protect the private intake token
Keep the server-side intake token secret and never expose it in Help Centre content or client-side logs.
Use the honeypot spam check
Leave the hidden website field empty; populated submissions are filtered.
Complete public intake fields
Provide name, company, email, phone, property address, compliance service, authority, deadline, priority and message as applicable.
Meet public intake validation
Provide name, property address and at least one of email or phone.
Use supported public priorities
Use Normal, Urgent or High; unsupported values fall back to Normal.
Match or create the CRM customer
Reuse an existing active contact by email where possible, otherwise create the client/contact records supported by the current schema.
Create the case from website intake
Create a Case started application and compiled summary from validated website fields.
Record the website-submission timeline event
Add a landlord-visible event identifying website intake.
Send website-intake emails
Send an administrator notification and customer confirmation when the email address is valid.
Return the generated reference
Redirect to the configured success page with the new case reference.
Review deployment-specific values before reuse
Review tenant path, website domain, email identities, success URL and external wording before deploying elsewhere.