Connecting Your Visitor Map to Your Admissions CRM: iSAMS, Admissions+, OpenApply, HubSpot and the Rest

An enquiry that lands in a mailbox nobody owns is an enquiry you have lost. Admissions teams run on their CRM, whether that is a school MIS with an admissions module or a dedicated recruitment system, and anything that captures interest on an open day needs to end up there without someone retyping it. There are four ways to do that from a web page, and most systems support at least two. Here is how they work and which fits which system, as we have set them up for Signposted pages.

The four routes

A form embed. Your CRM gives you a snippet of code (an iframe or a script) that draws its own form on the page. The enquiry never touches anyone else's server and arrives in the CRM exactly as if it had come from your website. Best when the system offers it.

A webhook. The page's own form posts each enquiry as a small JSON record to an address you give it. Your CRM, or an automation tool in front of it, creates the record. Best when the CRM has an API but no public form, or when you want to add the enquiry to a sequence or tag it.

Email. Each enquiry is emailed to admissions with the sender as reply-to. Universal, instant, and fine for small volumes, though someone still has to create the record.

CSV export. The page keeps every enquiry in a list you download and import. The fallback for systems that take nothing else.

System by system

• iSAMS. No public enquiry form embed. Use email notifications, or a webhook into Zapier, Make or Power Automate with a step that creates the enquiry via the iSAMS API. CSV import works for a batch after an open day.
• Admissions+ (Applicaa). Create an Enquiry form in Admissions+ and paste its embed code. Enquiries land straight in the pipeline.
• OpenApply. Inquiry forms can be embedded with an iframe from Admin, Forms, Inquiry, Embed.
• SchoolBase. Web enquiry forms via its web forms module, or a webhook into an automation.
• Arbor, Bromcom, SIMS. No embeddable public form. Email notifications plus CSV import, or a webhook into an automation tool that writes to the MIS.
• Finalsite. Forms give you an embed snippet under Forms, Embed.
• HubSpot. Marketing, Forms, Embed gives a script; or point the webhook at a HubSpot Workflow with a webhook trigger to enrol the contact in a sequence.
• Salesforce Education Cloud. Web-to-Lead generates an HTML form to paste, or a Flow with an HTTP endpoint takes the webhook.
• Microsoft Dynamics 365. Customer Insights marketing forms embed with a script; Power Automate's "When an HTTP request is received" takes the webhook.
• Gecko and Slate. Both offer form embeds from the form's share options.
• Unibuddy. Not an enquiry system: link your ambassadors to their Unibuddy profiles and keep the enquiry form for enquiries.

What to capture

Name, email and an "I am a…" field (prospective parent, student, agent) are enough to route an enquiry; phone and a message are optional. Add a consent sentence you have agreed with your data protection lead, and make it a tick box rather than small print. Pass the open day the enquiry came from as a hidden field so the CRM can attribute it.

A note on GDPR

Whichever route you use, the enquiry is personal data and the page is a processor for you. Keep the form minimal, say what you will do with it, do not store it longer than you need, and prefer the embed route where the data goes straight to the system you already have a processing agreement with. In Signposted, the built-in form stores enquiries only until you export or delete them, emails you with the sender as reply-to, and sends the webhook once; the CRM presets in the Enquiries tab carry the notes above so the admissions team can set it up without IT.