Console 2.6 User Guide
This guide is primarily intended to give a comprehensive understanding of the Console.
The Console is the company's most basic service. Users can create and manage companies, subscribe to services, manage inventory, etc. On this module, user can operate all matters of the company, and it connects a series of ThingsMatrix services, eg. TMX Access™, TMX Insight™, CMP and FOTA.
3.1 Create Company
Company is the basic unit of ThingsMatrix’s services. Before exploring these services, the user needs to create a company at first.
By clicking Create a company, the user can apply for a company with Company Name and Billing Address.
After the user submits the application, the user can view the company in the company list of the header, and view the company's basic information on the page. After completing the application to create a company, users can subscribe to services and access them.
In the order menu, the user can view the application order of the creating company, or cancel the order to interrupt order processing and resubmit a new application.
3.2 My Company
On this page, the user can view the information of the company to which the user belongs. It includes Basic Info, Billing Address, Billing Discount, Billing Cycle, and service-related information.
3.3 End Customers
The End Customer page shows the end customer companies belonging to the distribution company. The authorized user can apply new end customer company, modify the information of end customer company and apply service for them.
3.3.1 Add End Customer
Add End Customer, the user can configure a new end customer company. On this page, the company name, billing address, and custom domain are required. After the user fills in the necessary information, the user can click
Add to apply for a new client company.
On this page, authorized users can view the entire list of orders. Order types include service, company, equipment, SIM card, upgrade and modification.
Users can access the detailed information of each order in the bottom window. There are two tabs, "Order Details" and "Logistics Records". If there is an device type order, it means that the device has been purchased, and the user can check the logistics status in the "logistics record".
On Billing page, users can view monthly bills. Each columns show the component usage, such as online device, reports, commands, data flow usage, api usage, storage space, etc. The Amount Payment shows the total cost.
The normal company and distributor company can generate invoice, which can be downloaded.
Users can view devices of the company from the inventory categories. On this page, users can view information of devices, RMA records in the bottom window. Users can also manage the status of the devices and assign the devices to different end customer companies (under the distribution company).
6.1 Purchase Device
For purchasing devices users can click Action - Purchase Device Button. Users need to fill the form, which includes device model, quantity, unit price, delivery time, shipping method, contact number and delivery address. This information should be confirmed with our sales department before applying.
After the user submits, an order will be generated. By clicking
here, the user will jump to the order list and will see this order.
6.2 Edit Ownership & Distribute
These functions are available under the distributor company. Users can upload excel files from the downloaded template to transfer the devices to the end customer company or distributor in batches.
The user can also select multiple devices and change the ownership to a specified company.
6.3 Edit Status
To control devices status, users can click Action - Edit Status button. Then users can upload excel files from the downloaded template to change status of the devices in batches.
7 SIM Cards
On SIM Cards inventory page, users can view the basic information of SIM Cards on the list.
7.1 Purchase SIM cards
For purchasing SIM cards, users can click Action - Purchase SIM Card Button. Users need to fill the form, which includes operator, SIM card size, quantity, unit price, delivery time, shipping method, contact number and delivery address. This information should be confirmed with our sales department before applying.
7.2 Edit Ownership
This function is available under the distributor company. Users can upload excel files from the downloaded template to transfer the SIM cards to the end customer company or distributor in batches.
This service is mainly used for after-market services such as technical support, maintenance, and replacement of device. Users can leave a message to the support staff to inquire about product-related issues under Ticket, or ask for repair/replacement of the warranty device. When the support staff confirms the need for repair/replacement, an RMA order will be initiated to the user. After the user receives the RMA order and completes the order information, the device can be sent back to the repair/replacement process according to the return address.
Support staff will keep the historical data of Ticket and RMA, and users can check the support progress of related device at any time.
In this Ticket Section, users can add Ticket to inquire about technical-related issues, or ask for repair/replacement. The general process is as follows:
The users can obtain the brief information of the Ticket from the list: Ticket ID, Submitted time, Synopsis, Company, Status, number of related RMAs, and last activation time.
8.1.1 Add Ticket
By clicking the Add Ticket button on the top of list, a new Ticket form will be popped out. If users submit Ticket under a distributor, company field needs to be selected. When the information is filled, users click Submit to add a ticket.
During the ticket processing, users can enter content and click Reply to comment and communicate with staff.
Users can only ask for repair/replacement of the device under Ticket. When the support staff confirms the need for repair/replacement, an RMA order will be initiated to user.
The general process is as follows:
8.2.1 Verification RMA
When support staff initiate a RMA order to user, user will receive an unverified order in RMA list.
Click Verify your RMA information, this will pop up the basic information of the RMA order, including return address, contact information, shipping address and Device List. The user needs to Confirm this information.
8.2.2 Shipping device to FAE
After devices in device list are packaged and sent, user should upload shipment information by clicking Ship to FAE. Shipment Number, Logistics Company, Delivery Time and Recipient are required.
After the support staff confirms the receipt, the received status in the device list will change from
It is allowed to divide the devices into several packages and send them separately.
8.2.3 Outbound List
In this section, all received devices are synced to this list. After the device aftermarket processing is completed, users can see Return Comment, RMA Type and New SN / Content and know what happened.
When the RMA order is completed, the RMA record of the device will be synchronized to each device.
8.2.4 Receive repaired/replaced devices
After the package is delivered to the user, the user can confirm the receipt in the Shipment Info (to Company).
9.1 SMS Records
Users can view every SMS pushed to company users. Whether the SMS has been successfully sent, it will be listed on this page. By clicking the ">" on the left, users can read the content of this SMS record.
9.2 Email Records
Users can view every email pushed to company users. Whether the email has been successfully sent, it will be listed on this page. By clicking the ">" on the left, users can read the content of this email record.
10 API Applications
API application is used to manage API authorization. Users can access to API service with API key.
10.1 Add App
To add API application, the user can click
+ Add App button.
In this window, App name and service access are required. Service access limits the authorization of API key. IP whitelist declares the IP addresses that the user can request through the API service.
After filling out this form, an API key will be generated. No matter how the user reconfigures applications, API key will not change.
10.2 Configure Application
To change the authorization of an API application or set the IP whitelist, the user can configure the application in the API application list.
10.3 Delete Application
The API key will never be expired. When the user wants to invalidate the API key, the user can delete the related application from the API application list.