We need your input!

[danielfriis]

Hi all,

My name is Daniel and I’m working with @jenssogaard on Conversational Form (CF).

We are very curious to learn a few things about what you think of CF.

If you can spare 2 min, we would love to know:


1. What you are using CF for and where you've implemented it?
2. Why did you choose to go with CF?
3. How can we improve CF?

Feel free to reply here, or write me an email ([email protected]).

All the best,
Daniel

[callistusasir]

Hi @danielfriis

I am using this in a application that makes the engagement of Facebook ads better for a client.

Had a few issues when trying to compile this with GULP but got around it now.

It's great where there is a decision tree to get an answer. Especially for support tools.

I am mainly using it in survey questionnaires as well.

Really looking forward to a proper release version.

I think a great help would be including in the docs about using auto builders such as web pack and gulp.

Datepickers would be a great addition as well

[jenssogaard]

@CallistusWD thank you for taking the time to provide us with your experience and use cases. That is really valuable to us. As for the datepicker, I do not think we will add it as a core feature since datepicker ui depends a lot on the specific scenario at hand. However I have created a crude example of how you can implement a third party datepicker, have you seen it?

[stormsson]

hi @danielfriis , @jenssogaard : on a backend environment we are using cf.
We use it to gather data from the user, and often the user needs to change page in its profile area in order to check informations that are need for the answer,tehrefore...

As a further feature i would suggest persistence between page changes: a way to save / inject the current state of the conversation in order to allow the user to check different pages without losing his form completion progress

[jenssogaard]

@stormsson I am very happy to hear that you are using CF. And I absolutely understand the need for persistence in the use case you describe. I can think of a few solutions on how to go about this but also some challenges with state management (eg. should state always supersede form field value...).

If you want to do this outside of CF and you use a form tag as the basis for you CF instance, you could easily write some JS listeners that updates localstorage onChange and delete localstorage onsubmit.

If needed I could put together an example using vanilla Javascript?

[callistusasir]

Wow i never thought of doing that, would it not be better to compile it into a 30 day cookie of some sort instead? I have used this with cookies before, may just depend on how much data you would need to save and retrieve.

@jenssogaard Defniitely would love the example if you have time :)

[stormsson]

@jenssogaard thank you it would be very appreciated if you have the time! i actually didn't find which cf variables contain the current "state" of the conversation

[RJCAM]

I'm using CF to implement a dynamic registration page for my company's app

It was their choice to use it but personally I think it's an awesome API and I think it's better for user communication

Perhaps adding more tutorials about how we can make a few changes. Like in my case when I start using it I didn't know how to use the userInterfaceOptions and other things.

[jenssogaard]

@RJCAM thank you for sharing your feedback, greatly appreciated. I understand what you are saying. Being able to customize the look and feel to match your needs is very important and there is still work we can do in that area to make that more transparent. I will put it on the roadmap.

[texxs]

#3
I think it would be awesome if you added a couple of sentences so that people who AREN'T JavaScript experts could use the basic version of the conversational form.

[texxs]

The "Getting Started" section of the documentation implies that all you have to do is include the js from the cdn and then name your form properly and then:

That's it! Your form is now conversational 👍

Clearly, it takes more than that,

[texxs]

The Conditional flow example has this comment in the source code:
<!-- Conversational Form will auto-run because of attribute "cf-form" -->
Yet a ctrl-F search of the entire source code shows that comment is the only time that the text "cf-form" is used.

Things like this and the above comment are making this really hard to get started. At least for me. It's a shame because this project sounds REALLY promising.

[jenssogaard]

@texxs thank you for the feedback. Documentation and the ability to quickly get started is key. With that being said cf-form is mentioned in the source:
// auto start the conversation let formElements: NodeListOf<Element> = document.querySelectorAll("form[cf-form]");

Basically. If you load Conversational Form and add cf-form as an attribute to your HTML form tag then an instance of Conversational Form will automatically be appended and shown.

I hope this can help clear up any misunderstanding and I hope you will give our project a try.

[AnirudhaGohokar]

Did we just removed the voice input in latest 1.0 release?

[jenssogaard]

Hi @AnirudhaGohokar. No, should still work. I'll follow up later today.

EDIT: did a quick test - and it works here.

[buesing]

Would be great if you could make this work with SSR - when using next.js for example, I'm getting a "window is not defined" error. I can work around it but a more seamless experience would be cool.

[talusannni]

Hi,
I recently found this repo and it looks awesome.

We are trying to build an AI Chatbot platform for our customers
We have a product in Pipeline

I am trying to use for the customers who need button-based conversation chatbot

I am planning to do following in future

1. embed AI modules like duckling , TF or chatbot_ner and recognize wherever visitor enter free text
2. use it alternative to AI-based bot
3. Build a GUI for creating bots easily

[jenssogaard]

@talusannni sounds cool. I might throw an AI chatbot example together soon as it could be cool.

[SamuelGHill]

Hi @jenssogaard, I am interested in using this cdn for my site, but I know my team would not get far without a feature that can cookie/cache of visitors that have filled it out previous. Is this an option in the conversational form? I am having trouble finding this feature.

[jenssogaard]

Hi @SamuelGHill. That feature is not part of CF core. You could sponsor the feature and I could help bake it into CF. Also, do you see it happening with or without user consent?

[ambrose-leung]

@danielfriis and @jenssogaard thanks so much for making this available as an open source project.

1 I'm using it to conduct a survey about career development
2 I was looking for alternatives to typeform and this was much better - I could host it myself and have more control over the conditionals
3 It would be nice if there was also html/css example on how to display the form nicely like how you have it on the landing page (where there is padding on the left and right if the screen width is larger than whatever pixels). I ended up cloning the landing page and replacing the form, but that's not really a good solution.

Thanks again for the great project!

[SamuelGHill]

Hi Jens, This sounds like a great project! I have never contributed to such a large open-source platform. I assume I would fork the project, add the cookie feature, and push it for review. Let me know if I am missing any steps or need to do anything specific to contribute.Bests,Sam -------- Original message --------From: Jens Soegaard <[email protected]> Date: 11/4/19 3:40 PM (GMT-05:00) To: space10-community/conversational-form <[email protected]> Cc: Samuel Hill <[email protected]>, Mention <[email protected]> Subject: Re: [space10-community/conversational-form] We need your input! (#276) Hi @SamuelGHill. That feature is not part of CF core. You could sponsor the feature and I could help bake it into CF. Also, do you see happening with or without user consent? —You are receiving this because you were mentioned.Reply to this email directly, view it on GitHub, or unsubscribe. [ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "#276?email_source=notifications\u0026email_token=AKR56ZAOVZKED4POPVU5UBDQSCCFPA5CNFSM4GM255UKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEDAULIY#issuecomment-549537187", "url": "#276?email_source=notifications\u0026email_token=AKR56ZAOVZKED4POPVU5UBDQSCCFPA5CNFSM4GM255UKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEDAULIY#issuecomment-549537187", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": "https://github.com" } } ]

[sashareds]

It's sad this product is dead now

[leonib]

It's been very used lately. It helped me a lot.

[danielfriis]

I feel bad for neglecting this project, but we simply don't have the resources to maintain it. If anyone is interested in picking it up, please reach out!

[maurogar]

Hi Daniel!