Operations Support Tickets
The session is closed.Things can go on.
Real-time dialogue solves unsolved after-sales issues and is translated into follow-up lists: recording customer problems, handling and results. Computer stations and mobile phones are visible. The item that is not closed over time ends automatically by station setting.
Reception
Same table as the session, no system fillout.
On the left side of the watch station is "sold after". Real-time sessions can be followed up with a follow-up form, which can be followed up with comments. A mobile phone page can also read and write a follow-up. The client files were still under customer management after the tickets were closed and the list continued to be used for outreach visits.
- Type of business classification for post-sale issues, etc. to facilitate ex post screening
- Follow-up in the list without opening a separate chat window
- The number to be followed appears in the operating overview to avoid sinking
- Dialogue timeout and worksheet timeout are two sets of hours, filled separately in reception settings
Open
I'm going to take my own worksheet.
Open API to provide after-sale lists, new ones and follow-up. Webhook can subscribe to worksheet events. Keys are issued in the system setting, not on the web page. If the message closes, send the reviewed template at the customer service centre, not directly from API.
GET/POST /work With follow-up writing, A station key does not read the list of B stations.open / pending / waiting / resolved / closedSame as the duty station.
Next