Summary
Within the scope described in ACC's materials, work updates pass through the business's Zalo OA. This should not be understood as permission to automatically read every personal Zalo group. Pricing, participant numbers, and pilot conditions must be reconfirmed before registration.

A common situation
Illustrative scenario: The buyer assumes the solution will automatically collect every personal conversation. The operator wants it to receive only intentional work updates. Clarifying the channel from the start helps avoid mistaken expectations and data intrusion.
Three steps you can try
- Confirm the Zalo OA channel.
- Agree on participant numbers and the work-update template.
- Test the process before expanding.
What to remember
Within the scope described in ACC's materials, work updates pass through the business's Zalo OA. This should not be understood as permission to automatically read every personal Zalo group. Pricing, participant numbers, and pilot conditions must be reconfirmed before registration.
This is a hypothetical illustration, not an ACC customer testimonial or project result.




