Comment Feed - Comment type and client bug
1. When creating a process from a Viber message, the system groups them into the "Letters" group, although in the settings it is possible to group channels separately (Changes, Letters, Viber, Telegram, etc.). Since there is an option in the settings to display different types of comments, it is expected that they will be grouped by type in the comment feed. If this is a bug, then please fix this grouping.
In any case, thanks to this grouping by event type, the user will be 100% clear which event he received in the process. Otherwise, they are mixed and it is inconvenient to use.
2. Immediately there is a second problem. For some reason, the client does not pull up when we create a new process from the event.
Please help fix these. Video attached.
In any case, thanks to this grouping by event type, the user will be 100% clear which event he received in the process. Otherwise, they are mixed and it is inconvenient to use.
2. Immediately there is a second problem. For some reason, the client does not pull up when we create a new process from the event.
Please help fix these. Video attached.
OneBox OS → 01. Обращения → Новое обращение - Входящее 2.webm
OneBox OS → 01. Обращения → #11128 - Входящее 2 (Новое обращение).webm
Original question is available on version: ru
Answers:
1. Ustimenko Igor doing?
2. Same question
2. Same question
15.07.2022, 14:24
Original comment available on version: ru
yes we do it as an improvement
I will expose
I will expose
30.07.2022, 15:36
Original comment available on version: ru
Good afternoon.
1. Changed
2. If the sender of the event (who) is an employee, he should not be substituted as a client in the task. Only non-employee users are substituted.
1. Changed
2. If the sender of the event (who) is an employee, he should not be substituted as a client in the task. Only non-employee users are substituted.
02.08.2022, 17:27
Original comment available on version: ru
Da Hong Pao
OneBox production wrote:
Good afternoon.
2. If the sender of the event (who) is an employee, he should not be substituted as a client in the task. Only non-employee users are substituted.
I don't understand the second point? if from an event, for example, a call, create an order where the employee will be the client, then this will not work, the employee will not be substituted in the client field?
02.08.2022, 17:37
Original comment available on version: ru
Da Hong Pao
OneBox production wrote:
right
but it's weird. our own employees sometimes buy products from us, this should be done as a setting in the process, and not as a mandatory item. 1b is still a constructor for various solutions.
02.08.2022, 18:03
Original comment available on version: ru
It so happened that you are a unique company that creates a task from an event for its own employee who buys products from you via viber. Before that, we did not come across such companies, everyone just created an application for themselves with pens or in some other way, but did not write via viber or letter to create a task. It's the strangest thing, don't you think?
02.08.2022, 18:29
Original comment available on version: ru
Da Hong Pao
OneBox production wrote:
It so happened that you are a unique company that creates a task from an event for its own employee who buys products from you via viber. Before that, we did not come across such companies, everyone just created an application for themselves with pens or in some other way, but did not write via viber or letter to create a task. It's the strangest thing, don't you think?
in this topic, we described the result of testing the viber bot, if you are talking about it.
but it turns out that even a task for an employee cannot be created from an event? Or are we talking specifically about Viber? from other events is it possible?
02.08.2022, 18:47
Original comment available on version: ru
The system is made to suit 99% of users. 99% of users do not create events for themselves so that later they can create a task from an event for their employee where he will be a client. These are some strange things, why do you need this? In what real world example would you use this?
02.08.2022, 20:03
Original comment available on version: ru
Da Hong Pao
OneBox production wrote:
The system is made to suit 99% of users. 99% of users do not create events for themselves so that later they can create a task from an event for their employee where he will be a client. These are some strange things, why do you need this? In what real world example would you use this?
Well, in our case, a real example was a system health check. but why cut off the functionality and make it so that the employee could not be a client .... okay, apparently you know better.
03.08.2022, 07:56
Original comment available on version: ru
I also wanted to clarify. It turns out that even a task or any other process cannot be created from an event so that an employee pulls himself up as a client?
04.08.2022, 10:55
Original comment available on version: ru
Da Hong Pao
OneBox production wrote:
2. If the sender of the event (who) is an employee, he should not be substituted as a client in the task. Only non-employee users are substituted.
04.08.2022, 10:57
Original comment available on version: ru
Da Hong Pao
OneBox production wrote:
Good afternoon.
1. Changed
Please tell me why calls are not highlighted in a separate tab? What needs to be configured to make tabs work?
06.08.2022, 14:21
Original comment available on version: ru
https://ergo.crm-onebox.com/11773/ I can't get into the task to see
22.08.2022, 15:10
Original comment available on version: ru
https://ergo.crm-onebox.com/12179/
try this one.
I just wanted to write that comments are also not highlighted in a separate tab
try this one.
I just wanted to write that comments are also not highlighted in a separate tab
22.08.2022, 17:01
Original comment available on version: ru
Please join the conversation. If you have something to say - please write a comment. You will need a mobile phone and an SMS code for identification to enter.
Log in and comment
Copyright © OneBox 2024
