Plan requirement
| Subscription | Any plan |
| Access | Admin |
Yes, in three different ways, and they suit different situations. The widget is usually the right one.
The three options
- The messaging widget. A button on your site that opens a conversation, and can hand over to an AI agent or a person.
- A link to your help centre's request form. No embedding, and the customer leaves your site.
- Your own form, posting through the API. Full control over the design, and development work.
Start with the widget
It handles identity, attachments, validation and follow-up, and the customer stays on your page. For most sites that is the answer, and it takes minutes.
When your own form is justified
A form that has to sit inside an existing flow, look exactly like your site, or collect something the standard form cannot. That is real, and it is a build with an owner and a maintenance cost.
The link is underrated
Sending people to the help centre form means they see the articles on the way. A share of them never submit, because they found the answer, and that is the outcome you wanted.
Whatever you choose, ask for less
Every field is a reason for somebody to give up. Name, email, and what is wrong covers most cases; everything else is a question you can ask in the reply.
Say what happens next
On the form and in the confirmation: that you have it, and roughly when they will hear back. That single line prevents most follow-up messages.
Test on a phone
Most people fill in contact forms on a phone. A form that works on a laptop and not on a phone is a form most of your customers cannot use.
Comments
0 comments
Article is closed for comments.