Channels
Connect hosted enquiry email
Configure SendGrid Inbound Parse, verified sending and signed delivery events.
What you need
An organisation administrator configures Sorsana. Your email/DNS administrator configures SendGrid sender authentication, an inbound subdomain and routing. Use a dedicated subdomain so you do not replace the MX records serving your existing company inbox.
Save the connection
Open Integrations → Live enquiry connections → Configure a connection.
- Choose Hosted Email, select the Default property when appropriate and enter your Enquiry email address and Verified sender email.
- Enter the SendGrid API key with Mail Send access. Create a separate strong Inbound email username and Inbound email password for the callback.
- Enable signed Event Webhook delivery in SendGrid and copy its verification public key into SendGrid signed event public key. This is the public verification key, not another API secret.
- Choose Save settings and Test. Open Provider callback addresses in the saved provider row.
Configure SendGrid and forwarding
Your DNS/email administrator completes these steps in the provider console.
- Authenticate the sending domain in SendGrid and publish the DNS records SendGrid supplies. Use an authorised From address.
- Configure an Inbound Parse host on the dedicated receiving subdomain and publish SendGrid’s specified MX record for that subdomain.
- Copy the Inbound Parse callback address from Sorsana. Configure HTTPS Basic authentication using the saved inbound username/password. Use URL-encoded credentials if your provider requires them embedded in the destination URL; do not share that credential-bearing URL.
- Copy Signed delivery events into SendGrid’s Event Webhook URL, enable signature verification and select delivery, bounce and failure events.
- Forward portal enquiry notifications to the configured Enquiry email address. Preserve the original sender details, body, message identifier and listing reference.
- Send a fresh enquiry and a controlled reply. Verify one enquiry, the correct property, delivery status and a bounce test before launch.
Troubleshooting
A successful API-key test does not verify DNS, Inbound Parse or the sender domain. Check those independently if mail does not arrive. Hosted ingress rejects attachments and oversized payloads; arrange text-only forwarding or have staff review the original mailbox. Keep the original mail accessible to your team.