The Feedback form provides a direct way to communicate with Peach Suite Pro support and development teams.
Use the form to report a problem, describe a bug, request assistance, suggest an improvement, identify a navigation or user-experience issue, or submit general feedback about Peach Suite Pro.
All feedback submissions are monitored and reviewed.
When to Use the Feedback Form
Use the Feedback form when you need to submit information about:
- General feedback
- Program support
- Developer support
- Application issues
- Software bugs
- User-experience or UX issues
- Navigation issues
- Feature requests
- Unexpected behavior
- Display or formatting problems
- Performance problems
- Urgent operational issues
- Questions about how a feature works
Select the category that most accurately describes the reason for your submission.
Feedback Categories
The available category options may include:
- General Feedback
- Program Support
- Developer Support
- Issue or Problem
- Bug Report
- UX Issue
- Navigation Issue
- Feature Request
- Urgent Issue
- Other
Choosing the correct category helps route the feedback to the appropriate review process.
General Feedback
Use General Feedback to share comments, observations, or suggestions that do not require immediate technical assistance.
General feedback may include:
- What is working well
- What feels confusing
- Ideas for improving a page
- Suggestions for clearer wording
- Comments about the overall Peach Suite Pro experience
- Feedback about business workflows
Positive feedback is also valuable because it helps identify the features and workflows that are most useful to Peach Suite Pro businesses.
Program Support
Use Program Support when you need help understanding or using a Peach Suite Pro feature.
Program Support requests may include:
- Questions about how to complete a task
- Help locating a page or feature
- Questions about a report or status
- Assistance with business setup
- Help understanding a workflow
- Questions about user permissions
- Questions about subscription features
Before submitting a Program Support request, review the related Help page when available.
Include the page name and the task you were trying to complete.
Developer Support
Use Developer Support when the issue appears to involve application processing, integrations, imports, automation, or other technical behavior.
Developer Support requests may include:
- An automation did not run as expected
- An appointment import failed
- A page produced an application error
- Information did not save correctly
- A calculation appears incorrect
- A connected service did not respond
- A feature works differently across devices
- A technical error message appeared
Include the exact error message when one is displayed.
Do not include passwords, verification codes, security credentials, or private access keys.
Reporting an Issue or Problem
Use Issue or Problem when something is preventing you from completing a business task or when Peach Suite Pro is not behaving as expected.
Describe:
- What you were trying to do
- What page you were using
- What you expected to happen
- What actually happened
- Whether the issue happened once or repeatedly
- Whether another user experienced the same problem
A clear description helps support determine whether the issue is related to data, settings, permissions, a browser, a device, or the Peach Suite Pro application.
Reporting a Bug
A bug is a repeatable software problem that causes a feature to behave incorrectly.
Examples may include:
- A button does not respond
- A page does not load
- A form does not save
- A total is calculated incorrectly
- A status does not update
- The wrong record appears
- A page displays an error
- The same action produces inconsistent results
When reporting a bug, include the exact steps that caused the problem.
For example:
- Opened the Appointments page
- Selected an appointment
- Changed the provider
- Selected Save
- The original provider remained assigned
Step-by-step information makes it easier to reproduce and investigate the bug.
User-Experience and UX Issues
UX refers to the user experience of working with Peach Suite Pro.
A UX issue may not be a technical bug. The feature may work, but it may be difficult to understand or use.
Examples include:
- A button is difficult to find
- Instructions are unclear
- A page feels overcrowded
- A workflow requires too many steps
- A label is confusing
- A warning does not explain what action is needed
- A page is difficult to use on a phone
- The next step is not obvious
Explain what made the experience difficult and what you expected the page or feature to do.
Navigation Issues
Use Navigation Issue when it is difficult or impossible to move to the correct Peach Suite Pro page.
Navigation issues may include:
- A link opens the wrong page
- A button does not return to the expected page
- A menu item is missing
- A page becomes difficult to exit
- The Back option does not work as expected
- A View or Review action opens an unrelated page
- A page cannot be found from the main navigation
Include the page you started from, the link or button selected, and the page that opened.
Feature Requests
Use Feature Request to suggest a new capability or an improvement to an existing feature.
A helpful feature request explains:
- The business problem
- Who would use the feature
- How the current process works
- What the requested feature should do
- Why the feature would be useful
- Whether the need is occasional or frequent
For example:
Business problem: Staff members need to scan inventory while the Inventory page remains open on a desktop computer.
Requested feature: Allow a smartphone to connect to the desktop Inventory session and send scanned product codes back to the computer.
Feature requests are reviewed for usefulness, security, compatibility, development effort, and fit with the Peach Suite Pro roadmap.
Submitting a feature request does not guarantee that the feature will be developed or provide a specific completion date.
Urgent Issues
Use Urgent Issue when a serious Peach Suite Pro problem is actively preventing important business operations.
An urgent issue may include:
- Authorized users cannot sign in
- A critical business page is unavailable
- Appointments cannot be accessed
- Business information appears under the wrong account or workspace
- Private information appears accessible to an unauthorized user
- A major data or security concern is discovered
- A critical workflow is failing for multiple users
All feedback submissions, including urgent issues, are monitored.
Marking a submission as urgent helps identify its operational importance, but it does not guarantee an immediate response or a specific resolution time.
Clearly explain why the issue is urgent, who is affected, and which business operations are unavailable.
Security and Privacy Issues
Report a security or privacy issue immediately when:
- You see information from another business
- You can access a page or record that should be restricted
- An unauthorized person may have accessed an account
- A password or credential may have been exposed
- Private client, employee, provider, or financial information appears in the wrong workspace
- A lost or stolen device was signed in to Peach Suite Pro
Do not copy unnecessary private information into the Feedback form.
Provide enough information to identify the issue while limiting the personal or confidential information included.
Information to Include
A complete feedback submission should include:
- A clear subject or title
- The feedback category
- The name of the Peach Suite Pro page
- A description of the issue or request
- The steps that led to the issue
- The expected result
- The actual result
- The date and approximate time
- The device being used
- The browser being used
- Whether the issue can be repeated
- The number of users affected
The more specific the submission is, the easier it is to review and investigate.
Helpful Issue Description
A helpful description might say:
On the Daily Briefing page, I selected View under Appointments Tomorrow. The Appointments page opened, but it did not show only tomorrow’s appointments. This happened twice using Safari on a Mac.
A less helpful description might say:
The page does not work.
Include enough detail so support can understand the problem without having to guess which page, button, record, or action was involved.
Screenshots and Supporting Information
When available, a screenshot may help explain a visual, navigation, or error-message issue.
A useful screenshot may show:
- The page title
- The error message
- The button or link involved
- The unexpected result
- The date or status shown on the page
Before submitting a screenshot, review it for private information.
Do not submit screenshots containing unnecessary:
- Passwords
- Verification codes
- Full payment-card numbers
- Bank information
- Private access keys
- Unrelated client information
Browser and Device Information
Some issues may occur only on a particular device or browser.
When possible, include whether you were using:
- Desktop computer
- Laptop computer
- Tablet
- Smartphone
- Safari
- Chrome
- Edge
- Another browser
Also explain whether the problem occurs on another device or browser.
Reproducing the Issue
An issue that can be repeated is often easier to investigate.
Before submitting, note:
- Whether the issue occurs every time
- Whether refreshing the page changes the result
- Whether signing out and signing in changes the result
- Whether another authorized user has the same issue
- Whether the issue occurs on another device
Do not repeatedly perform an action when it may create duplicate appointments, messages, payments, expenses, inventory adjustments, or other records.
Before Submitting Feedback
Before reporting an issue, review the following when it is safe to do so:
- Confirm that the correct business is selected
- Confirm that the correct workspace is selected
- Confirm that the related information was saved
- Refresh the page
- Review the related Help page
- Check whether the same record already exists
- Confirm that your user account has the required permission
Do not make repeated changes merely to test a problem involving financial or client records.
Submission Confirmation
After submitting the Feedback form, Peach Suite Pro may display a confirmation that the submission was received.
Do not repeatedly submit the same feedback merely because a response has not yet been received.
When providing additional information about an existing issue, refer to the original subject, date, or feedback reference when available.
How Feedback Is Reviewed
All feedback submissions are monitored and may be reviewed for:
- Support needs
- Business impact
- Urgency
- Security or privacy concerns
- Ability to reproduce the issue
- Number of users affected
- Development requirements
- Possible connection to an existing issue
- Possible inclusion in the Peach Suite Pro roadmap
Some submissions may require additional information before the issue can be investigated or resolved.
Response and Resolution
A feedback submission may result in:
- A support response
- A request for more information
- Instructions for resolving the issue
- A software correction
- A future application update
- A documentation or Help-page update
- Review for possible roadmap inclusion
- No application change when the current behavior is working as designed
Response and resolution times may vary based on urgency, complexity, available information, and development requirements.
Duplicate Feedback Submissions
Avoid submitting the same issue multiple times unless important new information becomes available.
Duplicate submissions can make it more difficult to follow the investigation and determine the current status.
When an issue affects several users, submit one detailed report and include the number of users affected when possible.
Feedback Status
When available, feedback may use statuses such as:
- Submitted
- Received
- Under Review
- Additional Information Needed
- Planned
- In Development
- Resolved
- Closed
A status such as Planned or In Development does not guarantee a specific release date.
Follow-Up Questions
Support or developer support may request additional information, such as:
- Exact steps to reproduce the issue
- An error message
- A screenshot
- The date and time of the issue
- The affected page or record
- The browser or device used
- Whether the problem continues
Respond with the requested information while continuing to protect client, employee, provider, financial, and security information.
Privacy of Feedback Submissions
Feedback submissions may contain business, user, or application information.
Only include information necessary to explain the feedback, issue, bug, feature request, or support need.
Do not include:
- Passwords
- Employee verification codes
- Full payment-card information
- Bank-account credentials
- Private security keys
- Unnecessary health or treatment information
- Unrelated client records
Feedback information may be retained for support, troubleshooting, security, development, quality review, and audit purposes.
Feedback Best Practices
- Select the most accurate feedback category
- Use a clear subject
- Identify the affected page
- Explain what you were trying to do
- Describe the expected and actual results
- Include repeatable steps
- Include the exact error message
- Identify the browser and device
- Explain why an issue is urgent
- Avoid duplicate submissions
- Protect private and security information
- Provide follow-up information when requested
Important
All feedback submissions are monitored and reviewed.
The Feedback form may be used for general feedback, program support, developer support, issues, bugs, UX issues, navigation issues, feature requests, problems, and urgent operational concerns.
Submitting feedback does not guarantee an immediate response, a specific resolution time, or that a requested feature will be developed.
Clear and complete information helps Peach Suite Pro support and development teams understand, prioritize, investigate, and respond to each submission.