Verified Customer Consent & Portal Assistants
Connect POS labels, consent acquisition and scoped SupaGent assistance to shared business records.
Open interactive lesson and quizWhat you will learn
- Use stable product identifiers and barcode labels
- Collect verified channel-specific consent
- Assign SupaGent without crossing portal permissions
A retailer serves a new walk-in customer and wants optional cross-channel subscriptions, reliable scanning and private employee assistance.
Lesson 1
Consent follows the person’s choice
POS, commerce and inbound messaging create or match shared Contacts with source lineage. A purchase does not grant marketing consent. The configurable form verifies email for email subscriptions, reusing the Subscriber ID. Phone-only customers can register without email by completing signed inbound phone verification. WhatsApp subscriptions activate only after the same phone sends the verification message through a signed provider webhook. Existing opt-out and suppression controls remain authoritative.
Lesson 2
Invitations use the existing delivery services
Eligible new-order customers can receive a transactional email invitation, deduplicated over 30 days. Existing subscriptions, opt-outs, bounces and complaints are skipped. A business can enable a preferences link on the first customer-initiated WhatsApp reply. Welcome emails can use {{ConsentFormURL}}. No unsolicited promotional send is used to obtain consent.
Lesson 3
One engine, distinct portal agents
POS, storefront and employee assistants assign existing SupaGent agents. Prompts, approved knowledge and provider settings stay in SupaGent. POS context uses the selected register’s catalog. Store customer records require email verification. Employee context is resolved from the authenticated employee, excluding colleagues, bank/PF details and salary. The assistant supplies answers and guidance while existing modules enforce actions.
Lesson 4
Business-owned WhatsApp setup
Each BU owns its Meta business portfolio, WABA and phone numbers. Connect those assets using the business’s own Meta app and token, or use optional quick-connect Embedded Signup when offered. A platform Meta app is required only for that shared onboarding flow; it is not the BU’s WhatsApp account.
Practice · Connect a customer journey
- Print a product label and scan the existing product into a register basket
- Open the BU consent form and verify an email choice using a test recipient you control
- Assign a separate employee agent and inspect its private history with two test employee accounts