Tools and Terminals
Make the AI connection actually work and also get into your end product.
Organize approved business interfaces into tools to bring query and execution results back to the workbench; combine voice, role, memory, and device interactions according to terminal conditions.
Your product, why do you need it?
Your product, why do you need it?
Assistants that only answer questions cannot replace data queries and business operations. Enterprises also need to connect existing interfaces and equipment and allow different terminals to share business capabilities.
How to access your business?
How to access your business?
The following is an illustration of the implementation path. The business interface will not be called or commands will be executed on the official website.
- 01
Encapsulate existing business capabilities
Select a callable interface or tool and explain the parameters, usage and scope of application to avoid the model guessing the device capabilities based on the name.
Check the outputTool definition, input parameters and authorization conditions - 02
Connect to a workbench or terminal
The workbench provides a call entrance; the voice terminal completes input, agent processing and response according to the configuration, and does not obtain device control permission just because of voice.
Check the outputExplicit session and execution links - 03
Check execution and feedback
Check for true returns, failures and timeouts; check device status when there are control operations, rather than just relying on success text in the dialog.
Check the outputBusiness results, status feedback and execution records
Use with other base capabilities
Use with other base capabilities
These capabilities belong to the same basic platform and can be combined according to business needs.