Sending questionnaires
Building the request
New questionnaire opens the composer. Related to is Contact, Inquiry or Booking, and then you pick the record.
One recipient per request. To ask two people the same questions, send it twice.
Build the questions, or Start from template to copy a saved set in. Expiry date is optional and can be set here or later.
The footer has Save draft and Save & send. Saving a draft leaves the request in place with nothing sent. Save & send takes you to the email composer.
A draft request doesn't appear in the Questionnaires list, which shows requests that have gone out. Keep the tab open, or send it, rather than saving a draft you plan to come back to.
Sending it
The email composer fills in the recipient, a Subject and a Message you can edit, with a live preview of the email. The client gets a button reading Complete questionnaire.
Use template drops in a saved email template, and Client's first name, in the toolbar's Variables menu, greets them by name.
Resend questionnaire sends the same request again.
Sharing a link
Share with link in the composer, or Share on the request, gives you a link to send however you like: a message thread, WhatsApp, wherever they actually reply to you.
Sharing an unsent request marks it as sent first, and CoreHue asks you to confirm.
Setting an expiry
Set expiry gives the request a closing date. After it, the client can't submit, and the request reads Expired.
Useful when you need answers before a deadline. It helps you too: a questionnaire with no end sits open indefinitely and never quite gets chased.
Edit expiry adjusts it on a request that's already out.
What the client sees
The form opens on your branded client page. No sign-in.
Their answers save as they go, with a small marker reading Saving, then Saved. Someone can start on a phone, get interrupted, and come back later without losing anything. That alone gets more forms finished.
A progress line shows how many questions they've answered. Any questions you hid behind conditions appear as their answers make them relevant.
At the end, Review answers shows everything they've entered, with Back to edit if they want to change something, and Submit answers to send it.
Once submitted they see a thank-you and a read-back of their answers. If the request came from a booking or a proposal, they're taken back to it instead.
After they submit
They can't change their answers afterwards, and you can't reopen it for them. If something needs correcting, send a fresh request, or just ask them.
Asking directly is usually faster than a second form.
If you edit a live questionnaire
You can still edit the questions on a request that's out, using Edit, until it's answered or its closing date passes. If someone is part-way through, their answers to the questions you didn't change are kept.
Better to avoid it. Edit between sends rather than during one.
Chasing
Unanswered questionnaires can be chased automatically. See Chasing documents.
Worth turning on. Questionnaires go unanswered because people mean to do them later and forget, not because they object.
Cancelling a request
Cancel request stops one you sent by mistake or no longer need. The client can't submit it afterwards, and the page tells them you no longer need their answers.