Automate your communications to customers and staff with Web Forms in Workflows by Whispir. Recipients simply respond to an web form sent via your workflow and that content is captured and can be dynamically used to trigger and route further communication automations.

Like web pages, web forms use the same intuitive drag & drop interface so that anyone in your business can easily build custom forms for information capture.

Web forms are then delivered via a link sent through an SMS or Email messages.

Drag and Drop Editor

Web Forms support all existing components (see Web Pages) and Web Form Triggers.

Capturing responses

SMS or Email Messages sent via workflows support the ability to capture additional information by including a web form with your message. Recipients simply respond to a web form sent via your workflow and that content is captured and can be dynamically used to trigger and route further communication automations.

This allows you to:

  • Use Webform response capture to power auto replies based on keywords or phrases
  • Conveniently automate responses to messages (highly customisable for a wide variety of marketing, operational and crisis use cases)
  • Promote conversational messaging with recipients without the need for additional apps required to be installed

How to add Web Forms

Start by adding a new step in your workflow and selecting Web Form under the communication category.

This will add a new Web Form step to your workflow with 2 new paths. One for when a recipient submits the web form and one for when no submission is received.

Click new Web Form step that has been added and select the channel you would like to send it via.

Add recipients for your SMS or Email message.

Click the Web Form content button to start creating your webform in the Drag and Drop builder.

You can add all existing Display Components and Form components to your Webform.

You can also use variables in form fields as the default value. This allows you to essentially pre-fill webforms with contact information or with variables generated from above steps.

Once you have created your webform, click the save and close button.

Next, create your message content by clicking the channel of your choice in the content section of the Webform step.

Ensure you add a web_link variable to your message. This will be turned into a unique link to your webform per recipient.

Finally, configure how long a recipient has to complete and submit your webform before it expires.

💡 Please note: The minimum collection time is 15 minutes and the maximum collection time is 99 days. By default, collection is set to 1 day.

Webform Submitted Branch

This branch is triggered when a recipient submits the webform that has been sent to them.

Details of their submission are captured and become available as additional variables in subsequent steps in the workflow stemming from that branch.

Below is a list of the variables that are collected when a recipient responds to a Webform message and where they can be used.

Variable

Summary

Content

Recipient

Condition

Initial Message

Recipient: First Name

If the initial message has been sent to a Whispir contact, either via a contact or distribution list, this variable will display the contacts First Name.

If the initial message has been sent to an ad-hoc mobile number, this variable will not render.

🚫

Recipient: Last Name

If the initial message has been sent to a Whispir contact, either via a contact or distribution list, this variable will display the contacts Last Name.

If the initial message has been sent to an ad-hoc mobile number, this variable will not render.

🚫

Recipient: Phone No.

This is the phone number of the recipient the initial message was sent to.

Message: Time Sent

This is time the initial message was sent to the recipient.

Format: DD/MM/YYY
e.g. 18/11/2020

🚫

Response

Response: Time Received

This is time the initial message was sent to the recipient.

  • Type: String
  • Format: YYYY-MM-DDTHH:mm:ssZ

E.g .

2020-11-18T16:35:56.914+11:00

🚫

Form Components

Text Input

Type: String

Example:

Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Long Text Input

Type: String

Example:

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. A erat nam at lectus. Ac feugiat sed lectus vestibulum mattis ullamcorper velit.

Date Input

Type: String

Example:

23/04/1989

Multi-Choice

Type: String

Example:

First option, Second option, Third option

We will enhance this in the future so it renders as a list in html content and a comma separated string in single line field inputs.

Single-Choice

Type: String

Example:

Single Choice

Dropdown

Type: String

Example:

Drop Down

Webform not Submitted Branch

This branch is triggered when a recipient does not submit the webform within the given expiry time that has been sent to them.

No further details are collected as no submission has been recorded, so only the initial message recipient details are added as variables to this branch.

Variable

Summary

Content

Recipient

Condition

Initial Message

Recipient: First Name

If the initial message has been sent to a Whispir contact, either via a contact or distribution list, this variable will display the contacts First Name.

If the initial message has been sent to an ad-hoc mobile number, this variable will not render.

🚫

Recipient: Last Name

If the initial message has been sent to a Whispir contact, either via a contact or distribution list, this variable will display the contacts Last Name.

If the initial message has been sent to an ad-hoc mobile number, this variable will not render.

🚫

Recipient: Phone No.

This is the phone number of the recipient the initial message was sent to.

Message: Time Sent

This is time the initial message was sent to the recipient.

Format: DD/MM/YYY
e.g. 18/11/2020

🚫

Did this answer your question?