SupaGent AI & Governed Actions
Use the BU assistant, verified customer actions and safe lookup formulas.
Open interactive lesson and quizWhat you will learn
- Prepare and confirm a SupaGent workspace action
- Configure an agent case lookup and Event Hub rule
- Apply numeric lookup filters and channel stock limits
A team needs a Contact, a draft welcome email and a customer support bot that can see only verified cases. Inventory must remain correct when Orders are placed.
Lesson 1
Work with the floating assistant
The SupaGent button stays available across BU screens when its AI feature is enabled. You can ask it to find a workspace, prepare a Contact with name and email, prepare an email draft from a natural-language brief, or create a draft Send Flow for an exact active audience name. It shows a proposal before saving. Each save uses the same BU permissions and validation as the regular editor. Draft emails do not send, and draft flows cannot activate without their usual review. When Cloudflare AI is connected it can explain tasks in natural language. An agent’s BU data access toggle is off by default; when enabled, the floating assistant can retrieve relevant business records and readable knowledge for the signed-in user’s permissions. It retrieves excerpts as needed, not a whole database dump. Customer chat remains limited to its verified Contact, and WhatsApp redirects private requests to secure verification. Sign-in and integration secrets are excluded. With Cloudflare connected, the assistant can prepare create, edit and delete proposals for Contacts, Companies, Deals, Tasks, Cases, Campaigns, Products, communication notes and custom object records. It asks for missing required fields and uses existing save validation. Editing or deleting requires BU data access; ambiguous record names require an exact ID. Deleting requires review of a specific record. BU managers can switch the staff assistant off and customize its name, welcome message, accent and guidance in SupaGent. Supa Actions, Supa Topics and Supa Prompts are reusable destinations.
Lesson 2
Verify identity before exposing cases or running actions
In SupaGent, shared topics, knowledge and actions can be assigned to several agents without copying their definitions. A case lookup action lets only a verified Contact view that Contact’s own case numbers, subjects, statuses and resolutions. An unassigned agent cannot disclose cases. A chat automation action emits a supagent.requested Event Hub event only after an explicit request and email verification. Filter Business Rules by the shared action ID so one agent’s intent does not trigger another action. Routes can call an approved flow or webhook or alert a BU user; Business Rules can create a Task, Case or notification. WhatsApp directs account-specific requests to secure web verification.
Lesson 3
Use numeric lookup formulas without executable code
A custom object relationship can have its existing equality filter plus a numeric expression, for example target.stockQty >= source.quantity or target.stockQty >= source.quantity + 1. Choose numeric fields on the source and target objects. The lookup chooser applies the comparison and the server rechecks it when the record is saved through CRM, import or object ingestion. Missing numeric values do not pass. This filter limits eligible related records; it does not reserve inventory or authorize a purchase.
Lesson 4
Keep channel inventory and BU sign-in accurate
An Order uses the selected channel’s stock rather than the global Product count. Its quantity input shows the available limit; the commerce backend and database prevent saving more units than available, including competing API requests. Editing an Order can reuse its own previously allocated units in the same channel, but cannot use another location’s stock. For faster sign-in on a personal device, opt to remember only BU code and email after successful login or use a BU-specific sign-in link. Password and BU PIN are never saved in that hint; both are still required. Do not enable the hint on a shared computer.
Lesson 5
Compare draft and published pages
Save your HTML, CSS and JavaScript as a draft, preview it at desktop, tablet and mobile widths, and publish when ready. Open the published page in a new tab using the standard SupaChrome URL, and copy the link from the published page card. The public page can differ from an unsaved draft. Form submissions use the published field mapping to create BU-scoped Contact or custom-object records. Trial orgs can keep two custom pages; delete an unused page from its card to free space. Try the form with a test record and inspect its mapped fields in the target object. If you edit a published page later, save and publish again so visitors see the updated content; open the public URL to confirm that the new version is live.
Lesson 6
Check a custom domain before sharing it
A published page always has its standard SupaChrome URL. Enter a custom hostname on the saved page and configure that hostname to route to the SupaChrome site over HTTPS using your DNS and hosting provider. Choose Check status. SupaChrome marks the domain verified only when it can fetch this exact published page at the custom address. Once verified, Pages shows both URLs with open and copy actions; verified custom URLs also appear as email CTA destinations. If the domain is pending, continue to share the standard URL and check the DNS, TLS certificate and routing configuration. Verification checks the full page path, not just the hostname or a DNS record. Recheck after a hosting change or certificate renewal. Open the resulting address in a browser before placing it in a live campaign.
Lesson 7
Customize the unsubscribe centre separately
Open Pages → Unsubscribe centre to set the confirmation page title, explanation and optional HTML independently from the Profile centre. Use its preview to check how the page will look. The secure link in a sent email identifies the individual recipient; a sample preview does not change consent. SupaChrome controls the confirmation button and records the global unsubscribe, even when the decorative content is customized. The page also offers a link to manage topics instead. Keep the explanation direct and avoid inserting another form in the optional HTML. Scripts and unsafe markup are rejected. When a person confirms, the email address is suppressed for subsequent marketing sends, including messages waiting in a Send Flow. The contact record stays in the business unit, and the consent event appears in the subscriber timeline.
Lesson 8
Use the standard URL or your own hostname
A published custom page works immediately at its standard SupaChrome URL. Custom domain is optional: use a hostname your business controls, for example pages.yourbusiness.com. Configure its DNS, HTTPS certificate and routing so that the same published SupaChrome page is served at that hostname, then choose Check status. Entering an unrelated site such as google.com cannot make SupaChrome control it; it will remain pending. Until verification succeeds, share the standard URL. Use Open in a new tab to inspect the live page. The editor Preview draft at desktop, tablet and mobile widths is for layout checks and does not submit forms.
Practice · Build a checked customer workflow
- Open the floating SupaGent button in the BU. Ask it to create a Contact with a name and email, inspect the proposal, then confirm it.
- Ask for an email draft in ordinary language, for example a welcome email for new subscribers. Confirm Save draft, then open Emails to review the saved draft; it has not been sent.
- Create a shared case lookup action in SupaGent, assign it to an agent and verify a customer by email before asking about their cases.
- Add a shared automation action and an Event Hub Business Rule filtered by its action ID. Have the rule create a Task or Case for the verified Contact.
- Ask SupaGent to prepare an Order of four units when only three are available in the selected channel. Review the stock message, then try three; confirm the order and verify the channel stock. Stock a Product with three available units in one channel. Try an order for four, then for three; observe the available quantity and the backend rejection.
- On a custom object lookup, set a numeric filter such as target.stockQty >= source.quantity. Confirm the chooser and import API both reject nonmatching records.