Threetone can store tool definitions and agent references. A working WhatsApp conversation cannot execute them today. Account assignment, enabled messaging, and saved approval intent do not prove runtime enforcement.
Prepare an order-status action
You need a documented order service, a permitted test account, a workspace member allowed to manage tools, and an explicit rule for verifying the customer.1
Define the minimum lookup
Return only the status and delivery information needed for the request. Do not return payment details or another customer’s address. The service should resolve the authorized customer independently of the agent’s generated arguments.
2
Keep channel identity separate from access
Plan how your application verifies the relationship between a WhatsApp sender and a customer account. Meta’s message-object reference describes incoming message data; receiving a sender identifier does not grant permission to read private orders. Do not use an unverified phone-number match as the entire access check.
4
Define failure and confirmation behavior
A failed lookup should report unavailable information without revealing whether another customer’s order exists. Any later cancellation or address change needs a separate action that confirms the exact order and proposed change. Preserve action identifiers and reconcile uncertain results before retrying.
Frequently asked questions
Can I put an order-service API key into a dynamic variable?
Can I put an order-service API key into a dynamic variable?
Do not put credentials into message text, prompts, or ordinary variable values. Use supported credential references in the applicable tool fields.
Can a saved approval policy replace a confirmation step?
Can a saved approval policy replace a confirmation step?
No. The service performing the action must enforce authorization and the required confirmation. Stored policy alone does not demonstrate that behavior.