routing-inbound-conversations-to-asa
Pass
Audited by Gen Agent Trust Hub on Oct 22, 2026
Risk Level: SAFECOMMAND_EXECUTIONINDIRECT_PROMPT_INJECTION
Full Analysis
- [COMMAND_EXECUTION]: The skill utilizes Salesforce CLI (
sf) commands such assf data queryandsf project deployto manage org configuration and metadata. These are standard tools for Salesforce developers and are used here for querying agent IDs and deploying flow metadata.\n- [INDIRECT_PROMPT_INJECTION]: The provided Flow templates ingest external inputs (phone numbers and messaging identifiers) to resolve Contact records before routing the conversation to an Agentforce agent.\n - Ingestion points: Incoming phone numbers and messaging user IDs are read from MessagingSession and VoiceCall objects in assets/inbound-asa-messaging.flow-meta.xml and assets/inbound-asa-voice.flow-meta.xml.\n
- Boundary markers: The templates do not explicitly include sanitization or boundary markers for the data passed to the Agentforce Service Agent, relying on platform-level routing logic.\n
- Capability inventory: The skill uses sf CLI for environment interaction and defines flows with record lookup and update capabilities within the Salesforce metadata.\n
- Sanitization: No specific sanitization of external phone or ID strings is performed before record matching, which is typical for standard Salesforce routing implementations.
Audit Metadata