@meetelise/chat 1.20.68 → 1.20.69
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
|
@@ -0,0 +1,61 @@
|
|
|
1
|
+
# Issue Checklist
|
|
2
|
+
|
|
3
|
+
**this is important because webchat goes down far too frequently from a variety of sources (i.e. bad merges, chat provider issues, backend changes)**
|
|
4
|
+
|
|
5
|
+
## Basic Popup Checks
|
|
6
|
+
|
|
7
|
+
- [ ] On click 'Chat with us', talkjs popup opens
|
|
8
|
+
- [ ] On click 'Email an Agent', email form pops up
|
|
9
|
+
- [ ] On click 'Call or text us', call and/or text us popup opens
|
|
10
|
+
- [ ] On click 'Book a tour', booking tour popup with calendar view opens
|
|
11
|
+
|
|
12
|
+
## Email an Agent Form
|
|
13
|
+
|
|
14
|
+
**Applies only if Email widget is enabled for building**
|
|
15
|
+
|
|
16
|
+
- [ ] The form should require the lead's name, email address, and phone number. Message is optional.
|
|
17
|
+
- [ ] Upon submission, the form should create a Guest Card (GC) with the lead's information.
|
|
18
|
+
- [ ] The marketing source should be correctly logged on the GC (the source should ‘property-website’ AND whatever attribute the lead selected in the dropdown)
|
|
19
|
+
|
|
20
|
+
## Web conversation
|
|
21
|
+
|
|
22
|
+
**Applies only if webchat applied to building**
|
|
23
|
+
|
|
24
|
+
- [ ] Chat widget should be responsive to questions asked
|
|
25
|
+
- [ ] Chat widget should accept a text input
|
|
26
|
+
- [ ] AI should provide appropiate responses based on the user's message
|
|
27
|
+
- [ ] Typing indicator should appear while lead is waiting back for response
|
|
28
|
+
|
|
29
|
+
## Booking a Tour
|
|
30
|
+
|
|
31
|
+
**Applies only if scheduling widget is enabled for the building**
|
|
32
|
+
|
|
33
|
+
- [ ] Chat widget should provide an option to book a tour
|
|
34
|
+
- [ ] The available tour types should be displayed based on the community offerings.
|
|
35
|
+
- [ ] If there is only a single tour type offered, then that should be automatically selected
|
|
36
|
+
- [ ] The lead should be able to select a tour type, date, and time.
|
|
37
|
+
- [ ] The lead's layout and unit preferences should be recorded and passed through on the GC.
|
|
38
|
+
|
|
39
|
+
## Marketing Source Attribution
|
|
40
|
+
|
|
41
|
+
**Behavior depends on this flag: https://app.launchdarkly.com/default/production/features/webchat-marketing-source-dropdown-configuration/targeting**
|
|
42
|
+
|
|
43
|
+
- [ ] We grab the source from `utm_source` in the url’s query parameters. So if you want it to be “Zillow” add `utm_source=zillow` to query parameters
|
|
44
|
+
- [ ] If flag set to “never”, marketing source dropdown should never appear
|
|
45
|
+
- [ ] If flag set to “always”, marketing source dropdown should always appear
|
|
46
|
+
- [ ] If flag set to “on-attribution-failure”, marketing source dropdown should appear if we fail to attribute the originating source.
|
|
47
|
+
|
|
48
|
+
## Dynamic Number Insertion
|
|
49
|
+
|
|
50
|
+
**Behavior depends on this flag: https://app.launchdarkly.com/default/production/features/webchat-marketing-source-dropdown-configuration/targeting**
|
|
51
|
+
|
|
52
|
+
- [ ] We grab the source from `utm_source` in the url’s query parameters. So if you want it to be “Zillow” add `utm_source=zillow` to query parameters
|
|
53
|
+
- [ ] If flag set to “never”, marketing source dropdown should never appear
|
|
54
|
+
- [ ] If flag set to “always”, marketing source dropdown should always appear
|
|
55
|
+
- [ ] If flag set to “on-attribution-failure”, marketing source dropdown should appear if we fail to attribute the originating source.
|
|
56
|
+
|
|
57
|
+
## Misc Checks
|
|
58
|
+
|
|
59
|
+
- [ ] The chat widget should adapt to various screen sizes and devices without compromising functionality or user experience.
|
|
60
|
+
- [ ] The chat widget should follow web accessibility guidelines (WCAG and ADA) to ensure that users with disabilities can interact with it effectively.
|
|
61
|
+
- [ ] The widget should support customization to match the company's branding and website design.
|