Describe a problem clearly to help resolve it
Support guides help you identify a problem, collect useful information and verify a fix. Start by separating the expected behavior from what actually happened. Record the steps and whether the issue repeats.
Check whether it affects one user, one channel or the whole operation. Reproduce the issue with test information when possible. An error screenshot and approximate time can help, provided private information is removed. Do not share credentials.
After applying a fix, repeat the original journey and check the next step too. For a conversation, seeing a message is not enough: check assignment, response and continuity. Keep a note of the change to support future reviews.
- Review your customer service process
- Organize service across multiple agents
- Browse the WhatsApp guides for businesses
Prepare an issue report that can be investigated
A useful report makes the problem reproducible without guessing what the user did. Describe the screen, the action you were trying to complete and the approximate time. State whether it affects one person, a team or every conversation. If it happens intermittently, explain which circumstances seem to trigger it and which scenarios still work.
- Write the steps in order and separate the expected outcome from the observed result.
- Check another authorized session or a sample that contains no customer information.
- Record the browser and any error message without including passwords or credentials.
- Document the temporary workaround and name the person who will verify the original scenario after a fix.
After a correction, repeat the same test and check the related tasks. Fixing one screen is not enough if the next step remains broken. Keep the report open until the entire workflow has been verified, then leave a short note so your team can recognize the issue if it returns.
Piyion support: issues, fixes and changes
This log brings together information about Piyion support, fixes and changes. It helps you understand the context of an issue and distinguish a published improvement from behaviour that still needs investigation in your account. Before reporting a problem, identify the affected screen, the steps needed to reproduce it and the expected outcome. Describe what happened without including passwords or private customer information. Those details support a clear request and make it easier to check whether a fix resolves your team’s specific case.
English 
Español