SupaGent
Assign SupaGent to POS, storefronts and employees
Reuse dedicated SupaGent agents with portal-specific records and conversations.
How to do it
- Create or assign an existing agent in the SupaTill Configuration, SupaCommerce store Settings or SupaPeople Portal settings. Module configuration and SupaGent management permissions are required.
- Use Create dedicated agent to create a separate SupaGent configuration for that portal. Enable the binding and set its daily message allowance. Manage its prompts, knowledge and topics in the existing SupaGent console.
- The POS assistant uses products and available stock from the selected register. It provides guidance; sales, stock, tax and payments remain controlled by the existing checkout.
- The employee assistant authenticates the current employee and reads only that person’s permitted profile, time, leave, benefits, requests and assigned published policies or courses. Bank details, PF details and colleague records are excluded.
- The storefront assistant uses the existing public customer inbox and human handover. Private customer questions require the existing customer verification flow.
Check your result
Switch employees or BUs and confirm histories and records remain isolated. Disable the agent binding to remove it from the portal.
Good to know
Generative replies require SupaGent AI access and an enabled provider. Approved knowledge lookup remains the fallback. The assistant never claims to have processed a payment or changed a record.
Still need help?
Tell us your BU code and the step where you got stuck. Do not include passwords, BU PINs, tokens or recovery codes.
Contact SupaChrome support