Product Documentation Product Documentation
Developer Documentation (opens new window)
Developer Documentation (opens new window)
  • Ticket System Overview

  • Ticket Access

  • Ticket Settings

    • Agent and Group Guide
    • Ticket Category and Ticket Template Guide
    • Ticket Processing Setting Guide
    • Ticket Flow Setting Guide
    • SLA Guide
    • Ticket Filter Setting Guide
    • Docking Page Setting Guide
    • Field Setting Guide
    • Ticket Flow Trigger Example
    • Ticket Scheduled Trigger Example
    • Usage description of Feishu docking
      • Ticket satisfaction setting guide
      • Usage description of Amazon docking
      • Q&A Bot Setting Guide
      • Status Setting Guide
      • Walmart Docking Instructions
      • SLA Statistics Guide
    • Ticket Processing

    • Ticket Statistics

    • Ticket
    • Ticket Settings
    Sobot
    2024-07-05
    Menus

    Usage description of Feishu docking

    # Usage description of Feishu docking

    ——Learn about the scenarios and specific operation steps of Feishu docking through this article

    # Preparations

    ● An account with Sobot system admin permissions. ● An account with admin permissions for Feishu admin backend.

    # Create Feishu app

    # ● Log in to Feishu admin backend

    Log in to the Feishu admin backend (opens new window) go to the Workplace - App Management, click "Create App" to enter the Feishu developer backend.

    image

    Figure 1: Feishu Admin Backend

    # ● Create enterprise self-built app

    Click "Create Custom App", fill in the name, description, and select an icon for the app.

    image

    Figure 2: Create Enterprise Self-built App

    image

    Figure 3: Set App Params

    # ● Add app

    Add bot app.

    image

    Figure 4: Add Bot App

    Add web app.

    image

    Figure 5: Add Web App

    If the access domain name of your current system is sg.sobot.com, then your URL configuration is as follows: The homepage URL configuration of the desktop end is as follows: https://sg.sobot.com/auth/sign_in

    If the access domain name of your current system is us.sobot.com, then your URL configuration is as follows: The homepage URL configuration of the desktop end is as follows: https://us.sobot.com/auth/sign_in

    image

    Figure 6: Configure Web App

    # ● Configure security setting

    In the Development Configuration - Security Setting of the app:

    If the access domain name of your current system is sg.sobot.com, then your URL configuration is as follows: Redirect URL: https://sg.sobot.io/ws-h5-client/

    If the access domain name of your current system is us.sobot.com, then your URL configuration is as follows: Redirect URL: https://us.sobot.io/ws-h5-client/

    image

    Figure 7: Redirect URL

    # ● Configure Permissions

    Make sure to open the following API permissions, otherwise the app will not be able to be used.

    In the Development Configuration - Permission & Scopes of the app, search and open:

    Obtain apps information

    Get basic information in contacts

    Manage app visibility

    Obtain department's basic information

    Obtain department's organizational structure in contacts

    Obtain user groups information

    Obtain user's basic information

    Obtain user's organization information

    Obtain user's email information

    Obtain user's employment information

    Obtain user ID

    Obtain user's mobile number

    Read and send messages in private and group chats

    Obtain tenant information

    Get employee's phone number

    image

    Figure 8: Add Permission
    Click "Confirm" when enabling (release the version in the next step)

    image

    Figure 9: Confirm Permission

    # ● Release version

    In the App Versions - Version Management & Release of the app

    Fill in the version number, such as 1.0.1

    Default feature on mobile: Bot

    Default feature on dekstop: Web App

    Update description: Fill in according to the actual situation

    image

    Figure 10: Version Details

    Fill in the Availability: It is recommended to select all members. When adjustments are made later, the number of versions released can be reduced.

    image

    Figure 11: Available Range

    # ● Review

    After the app is released, it might be reviewed by the admin before it can be used.

    # Bind Feishu channel

    # ● Fill in the app credential

    Fill in the App ID and App Secret of the app to the Sobot system. In the basic information - credential and basic information of the Feishu app, find the App ID,and App Secret.

    image

    Figure 15: App Credential

    Fill them into the Sobot system, in ticket center - docking center - docking app - docking Feishu app

    image

    Figure 16: Fill in the App Credential

    # ● Bind agent

    Click the "+ Add Member" button

    image

    Figure 17: Add Employee Button

    Select Feishu employees to be bound to Sobot agent

    image

    Figure 18: Select Feishu Employee

    Select binding method

    Manually bind existing agent: It is recommended to use this method for daily individual scenario account binding (such as employee onboarding);

    Add agent and bind it: When Sobot has not created the agent for this Feishu employee (such as the first time using Sobot system, and there is already relevant information of the employee on Feishu), this method can be used;

    Automatically bind existing agent: Automatically match Feishu employee and Sobot agent by mobile no. or email (this method is suitable for scenarios where there are a large number of agents in the Sobot system that have not bound Feishu);

    image

    Figure 19: Select Feishu Employee

    After successful binding, the agent already bound to Feishu will be displayed here.

    image

    Figure 20: Select Feishu Employee

    # ● Application of Feishu in ticket

    In the ticket center - setting - ticket processing setting - notification reminder, check Feishu reminder. When the notification conditions are met, an app message will be sent to the corresponding Feishu employee.

    image

    Figure 21: Message Notification

    image

    Figure 22: Message Notification-PC

    Last Updated: 11/18/2024, 7:17:07 PM

    ← Ticket Scheduled Trigger Example Ticket satisfaction setting guide→

    Update Date
    01
    AI Assistance User Guide
    02-26
    02
    Communication Network Log User's Guide
    02-26
    03
    SLA Guide
    01-25
    More Articles>
    Theme by Vdoing
    • Follow Sys
    • Line
    • Dark
    • Read