Submit a feature request when you need a workflow, setting, integration, report, or improvement that PloverCRM does not currently provide. A useful request explains the problem and desired outcome rather than prescribing only a button or screen.
Prepare a request #
- Search the Help Center to confirm that the capability is not already available.
- Check whether an existing setting, automation, list, tag, custom field, or integration can achieve the same result.
- Describe the task your team is trying to complete.
- Identify what makes the current process difficult, slow, or incomplete.
- Define the result you need.
- Prepare a fictional or redacted example.
Do not include passwords, tokens, private URLs, or identifiable customer information.
Submit the request #
- Sign in to the PloverCRM Web Dashboard.
- Open the Help, Updates, or account menu.
- Select Request a Feature or the matching option.
- Enter a short, specific title.
- Identify the affected PloverCRM area.
- Describe the current steps and limitation.
- Explain the expected result and why it matters.
- State how often the need occurs and which users or teams are affected.
- Submit the request.
The request option and form fields may vary by version or account access.
Write a strong request #
A strong request answers four questions:
- What are you trying to accomplish?
- How do you do it today?
- What prevents the current workflow from being sufficient?
- What would a successful result look like?
Avoid combining several unrelated requests in one submission. Separate requests are easier to understand and evaluate.
What happens next #
A feature request is feedback, not a guarantee of development or a release date. PloverCRM may ask follow-up questions, suggest an existing feature, or record the request for future planning. Review What’s New for future announcements.
