Once your form is published, there are a few ways to get it in front of people: embed it on your own website, share a public link or QR code, send it privately to named clients, or attach it to a proposal so it appears automatically once a client accepts. This guide covers them all.
Public or private
Before you share, decide whether the form is public or private, using the toggle on the form.
Public means anyone with the link or QR code can open and complete it, which is ideal for capturing new enquiries from your website or an email.
Private means the form is only for clients you send it to directly. The public link is still shown but won't work on purpose, so private forms go out through the send options below.
Embedding the form on your website
Rather than sending people off to a Socket page, you can put the form directly on your own site. Your enquiry page keeps your branding and navigation, and the enquiry still lands in Socket.
Open the form's share screen and choose Embed on website. This works for any form, not just lead capture ones.
Inline or popup
Pick how the form should appear:
Inline sits in the page and sizes itself to fit. Best for a dedicated enquiry or contact page.
Popup gives you a button that opens the form in a window over the page. Best where you want a "Get in touch" button in a header or alongside other content.
Getting the code onto your site
Under the snippet, click Copy snippet. It's ready to use as it is, with your form already referenced in it, so there's nothing to fill in or edit.
That snippet needs pasting into the HTML of the page you want the form on. If someone else looks after your website, this is the point to send it to them, and it's a two minute job at their end.
The snippet is in two parts: a script line, and the bit that places the form. You only need the script line once per page however many forms you put on it, so if you're embedding two forms on the same page, the second one only needs its placement line.
Tidying up how it sits on the page
A couple of settings underneath adjust the snippet as you change them, so set these before you copy it.
Sticky header offset. If your website has a header that stays put as you scroll, the form can end up tucked underneath it. Enter the height of your header in pixels and Socket leaves room for it, so the form stays fully visible when someone scrolls to it. Your web developer will know the number, or it's a case of trying 60 or 80 and looking.
Fixed height. By default the form grows and shrinks to fit whatever step the person is on, which is usually what you want. Set a fixed height instead if you'd rather it stayed one size and scrolled inside, for example to keep the rest of your page layout still.
For a popup you can also set the maximum width of the window, which is worth increasing if your form has wider questions like a table.
On a phone
On smaller screens the form breaks out of its box and runs down the page as part of it, so people scroll the page as normal rather than scrolling inside a little window. It's a much better experience on a phone, and there's nothing to configure.
Keeping it up to date
The embedded form stays in sync. Publish a change in Socket and your website picks it up, with no need to go near the code again.
⚠️ An embedded form relies on the form being public and active, exactly like the link does. If you set the form to private or deactivate it, the embed stops working too. Worth remembering before you tidy up an old form that's still sitting on your website.
Knowing which page an enquiry came from
Socket records the page the form was embedded on and puts it on the response, so if you've got the same form on your contact page and your pricing page you can tell which one someone used.
Sharing a public link or QR code
On the form's share screen you have two options.
Copy the link and paste it wherever you like, such as your website, an email or a message.
Use the QR code: copy it, let someone scan it, or download it as a PNG to drop into a document or print out.
Sending to a single client
To send a form to one client from their record:
Open the client record and go to the "Forms" tab.
Click "Send a form" and choose one of your active forms.
Pick the contact to send it to. The primary contact is highlighted by default.
Compose the email: the subject line, who it's sent from such as the client owner, and the body.
Hit "Send".
The form then shows on the client's "Forms" tab, where you can see its status and click in to view any responses they've filled in.
Sending to multiple clients
To send a form to lots of clients at once:
From the "Forms" area, open the form and choose "Send to clients", then "Multiple".
Choose who gets it: all active clients, or select by criteria such as a particular client manager's clients, certain entity types, or clients on certain services.
Choose whether to send to each client's primary contact or all their contacts.
Click "Review" to see the full list, and click anyone you want to exclude.
Continue to the message, set the subject, sender and body, then send.
As with a single send, each one shows on the individual client's record.
Attaching a form to a proposal
As well as sending a form on its own, you can attach an onboarding form to a proposal so the client is prompted to complete it the moment they accept. On the proposal accepted page they see a "Complete your onboarding" step, with a button to start the form straight away or come back to it later, and Socket also emails them a link to it.
There are two places to set this up.
A practice-wide default
In Settings, go to Proposals, then Proposal Settings, and find "Which onboarding form should clients complete after accepting a proposal?". You can pick a different form for new clients and existing clients, or leave either as "No onboarding form". Socket always uses the current active version of the form you choose, so editing and republishing that form keeps this working. This setting is also covered in our Your Practice Settings guide.
Per proposal
When you build a proposal, the Customise step has "Which onboarding form should this client complete after accepting?". Leave it on "Use practice default" to follow your practice setting, choose a specific form just for that client, or clear it so no form is attached.
💡 If the client picks "Maybe Later", they can still use the link Socket emails them to complete the form whenever they're ready.
💡 A private form's public link is shown but won't work, by design. Share private forms using the single or multi-client send above.
Once your form is out there
Getting notified about form responses, for in-app, email and Slack notifications, and passing responses into your other tools.
Viewing and managing responses, for reading, filtering and exporting what comes back.
Editing a live form and versions, for changing a form that is already out with clients.