exp_invite

To send an experience group invite, this skill verifies the customer's business_status in the database and triggers an awada control message routed by their external user id. It ensures the invite is sent exactly once after demo completion.

Duplicate invite prevention works by checking the customer database for an existing exp_invited business_status. If the customer is already invited, the process halts and outputs an ALREADY_INVITED message with a non-zero exit code.

Yes, you can use database routing to trigger an awada control message. The skill inserts or updates a customer record, sets the business_status to exp_invited, and then emits the control message for the experience group.

Automating experience group invitations requires the customer database peer identifier and the awada sender id. These inputs allow the script to locate the customer record and route the invite control message correctly.

The ALREADY_INVITED error with a non-zero exit code occurs because the customer's business_status in the database is already set to exp_invited. The skill intentionally skips sending duplicate awada control messages to already onboarded peers.

Trigger an experience group invite when a customer completes a demo and explicitly agrees to join for hands-on exploration. This ensures the awada control message is sent only to qualified leads seeking deeper product understanding.