Even with comprehensive documentation and troubleshooting guides, you might encounter issues that require direct support from the DigiConsent team. Knowing when to seek help, how to gather diagnostic information, and how to effectively communicate problems ensures you receive quick, effective assistance. This guide explains the support process, what information to prepare before contacting support, and how to maximize the value of support interactions.
Good support requests are specific, detailed, and include relevant diagnostic information. The difference between “the banner doesn’t work” and “the consent banner doesn’t appear on mobile devices after clearing cache, here are the error messages and screenshots” is the difference between extended back-and-forth troubleshooting and quick problem resolution. This guide shows you how to prepare excellent support requests.
When to Contact Support
Contact support when you’ve exhausted self-service troubleshooting options and the issue persists. Specifically, seek support when:
You’ve tried documented solutions without success: If you’ve worked through relevant troubleshooting articles, followed all steps, and the problem remains, it’s time for support. Mention which articles you’ve consulted and which steps you’ve tried. This prevents support from suggesting steps you’ve already attempted.
You believe you’ve found a bug: If DigiConsent behaves in ways that seem objectively wrong—error messages appear during normal operations, features don’t work as documented, or problems reproduce consistently in clean installations—you might have discovered a bug. Report it to support with detailed reproduction steps.
You need implementation guidance: Complex configurations like advanced geolocation rules, custom script blocking, or integration with specific platforms might require expert guidance. Support can advise on best practices for your particular use case.
You have pre-sales questions: Before purchasing DigiConsent Pro, contact support to confirm it meets your requirements. Ask about specific features, compatibility with your setup, or licensing questions. This ensures you make an informed purchase decision.
License and account issues: Problems with license activation, renewal, payment, or account access require support assistance. These administrative issues cannot be resolved through troubleshooting.
Before Contacting Support
Gather diagnostic information before reaching out. Having this information ready when you contact support speeds up resolution dramatically. Support can often diagnose issues immediately with proper information rather than requesting it through multiple back-and-forth messages.
System information to collect:
- DigiConsent version (found in Plugins menu)
- WordPress version (Dashboard → Updates shows current version)
- PHP version (Tools → Site Health → Info → Server)
- Active theme name and version
- List of all active plugins with versions
- Hosting provider name
- Browser and device where issue occurs
Many plugins include a system information page that compiles this automatically. Check DigiConsent settings for a “System Info” or “Debug Info” section you can copy and paste into support requests.
Document the exact issue: Write a clear description of what’s wrong. Include:
- What you expected to happen
- What actually happened instead
- When the issue started (after an update, when installing a new plugin, randomly, etc.)
- Whether it affects all users or only specific browsers/devices
- Whether it occurs on all pages or only specific pages
For example: “Expected: Consent banner appears at bottom of screen on mobile devices. Actual: Banner doesn’t appear at all on iPhone Safari. Started: After updating to DigiConsent 2.1. Scope: Only affects iOS devices, works on Android and desktop.”
Error messages: Capture complete error messages. Open browser console (F12 → Console tab) and take screenshots of any errors. Copy the full text of error messages from WordPress debug logs. Include error message text in support requests—these often reveal exactly what’s wrong.
For database errors or PHP errors, enable WordPress debug mode (covered in the Database Errors article) and include relevant portions of the debug.log file. Redact sensitive information like passwords or API keys before sharing logs.
Screenshots and Screen Recordings
Visual documentation is incredibly valuable for support. Screenshots show exactly what you’re seeing, and screen recordings demonstrate issues that involve interaction or timing.
Taking effective screenshots: Capture the entire browser window, not just a small portion. Include the address bar showing the URL and enough context to understand what page you’re on. On Windows, use Windows Key + Shift + S to open the snipping tool. On Mac, use Command + Shift + 4 to select an area to capture, or Command + Shift + 3 for the full screen.
For browser console errors, capture screenshots showing the entire Console tab including error messages, file names, and line numbers. Expand collapsed error details (click the arrow next to errors) before taking screenshots to capture the full stack trace.
Annotate screenshots to highlight the problem. Use image editing tools or browser extensions like Awesome Screenshot to add arrows, circles, or text callouts indicating exactly what’s wrong. This saves time explaining what to look at in the image.
Screen recordings for complex issues: For issues involving sequences of actions or timing-dependent problems, record a short video. Show yourself reproducing the issue from start to finish. Services like Loom, CloudApp, or built-in OS screen recording tools (Windows Game Bar, Mac’s Screenshot app) make this easy.
Keep recordings concise—under 2 minutes ideally. Narrate what you’re doing: “I’m clicking the accept button, and you can see it doesn’t respond.” This provides both visual and verbal context.
Providing Access for Testing
Some issues can only be diagnosed by logging into your site directly. Be prepared to provide temporary admin access if needed, following security best practices.
Creating temporary admin accounts: Instead of sharing your personal admin account, create a temporary admin account specifically for support access. Go to Users → Add New, create a new user with a generic username like “digiconsent-support,” assign the Administrator role, and use a strong temporary password.
Share these credentials only through secure channels. Don’t post login credentials in public support forums. Use private support tickets, encrypted email, or password-sharing services like OneTimeSecret that provide links that self-destruct after viewing.
After support resolves your issue, immediately delete the temporary admin account. Go to Users → All Users, find the support account, and delete it. This security practice ensures temporary access doesn’t become a long-term vulnerability.
Staging site access is preferable: If possible, replicate the issue on a staging site and provide access to that instead of production. Staging sites allow support to test solutions without risk to your live site. Many managed WordPress hosts provide one-click staging site creation.
If you don’t have a staging environment, consider creating one using plugins like WP Staging or through your hosting control panel. This is valuable beyond support interactions—staging sites let you test updates and changes safely.
Writing Effective Support Requests
Structure support requests for clarity and completeness. A well-written request gets faster, more accurate responses than vague descriptions.
Use a clear, specific subject line: “Problem with DigiConsent” is vague. “Consent banner not appearing on mobile Safari after 2.1 update” is specific and immediately tells support what the issue involves. Subject lines should summarize the issue in one sentence.
Effective request structure:
- Summary: Brief overview of the problem in 1-2 sentences
- Expected behavior: What should happen in normal circumstances
- Actual behavior: What’s actually happening instead
- Steps to reproduce: Exact steps to make the problem occur
- Impact: How this affects your site and users
- Troubleshooting already attempted: What you’ve tried to fix it
- System information: WordPress version, plugin versions, hosting, etc.
- Error messages and screenshots: Visual and textual evidence
Example of a good support request:
“Summary: The consent banner doesn’t display on iPhone Safari, though it works on all other browsers and devices.
Expected behavior: The banner should appear at the bottom of the screen on all devices including iPhones.
Actual behavior: On iPhone Safari (tested on iPhone 12 and 13 with iOS 16), the banner is completely invisible. Inspecting with Safari developer tools shows the HTML is present but not rendering visually.
Steps to reproduce: 1) Visit example.com on iPhone Safari. 2) Observe that banner doesn’t appear. 3) Check inspector—banner HTML exists but has no height.
Impact: iPhone users (about 30% of our traffic) cannot provide consent, which is a compliance issue.
Already tried: Cleared all caches, disabled other plugins, switched to default theme—issue persists. Read the Mobile Display Issues article and tried suggested CSS fixes with no success.
System info: DigiConsent 2.1, WordPress 6.4, Astra theme 4.2, WP Rocket (with DigiConsent excluded from optimization). Hosted on SiteGround.
Screenshots attached: Banner-desktop.png showing it working, banner-iphone-missing.png showing the blank space, console-errors-iphone.png showing browser console.”
This request gives support everything needed to diagnose the issue immediately. Compare this to “Banner doesn’t work on iPhone” which would require multiple follow-up questions.
Support Channels
DigiConsent likely offers multiple support channels. Choose the appropriate channel for your situation.
Documentation and knowledge base: Always check documentation first. Many questions are answered in guides like this one, saving you time waiting for support responses. Search the knowledge base for keywords related to your issue before submitting tickets.
Community forums: If available, community forums connect you with other DigiConsent users who might have encountered similar issues. Searching forum archives often reveals solutions to common problems. When posting to forums, use the same detailed format as support tickets.
Forums are public, so never share credentials, license keys, or sensitive information in forum posts. Use forums for general questions and private support tickets for account-specific or security-sensitive issues.
Email support: Direct email support provides private communication for account issues, license problems, or sensitive technical issues. Email allows attaching screenshots, logs, and detailed information. Response times vary by support tier but expect responses within 24-48 hours for standard support.
Priority support: If you have DigiConsent Pro or premium support, you may have access to faster response times, live chat, or phone support. Use these premium channels for urgent issues affecting live sites.
WordPress.org support forum: If using the free version from WordPress.org, official support happens through the plugin’s WordPress.org support forum. Note that free plugin support is provided by the community and developers on a best-effort basis. Response times and availability aren’t guaranteed.
Following Up on Support Requests
After submitting a support request, monitor for responses and provide requested follow-up information promptly.
Check spam folders: Support responses might be filtered to spam. Check spam/junk folders if you haven’t received responses within expected timeframes. Add support email addresses to your contacts to prevent filtering.
Respond promptly to information requests: If support asks for additional details, logs, or access, provide them quickly. Extended delays in your responses lengthen resolution time. Some support systems automatically close tickets after periods of inactivity, requiring you to reopen them.
Test proposed solutions: When support suggests solutions, test them thoroughly and report back with detailed results. “It didn’t work” isn’t helpful feedback. Instead: “I applied the CSS fix you suggested, cleared all caches, and tested on iPhone 12 (iOS 16) and iPhone 13 (iOS 16.1). The banner now appears on the iPhone 12 but still doesn’t show on the iPhone 13.”
This level of detail helps support refine solutions or identify edge cases.
Confirm resolution: When the issue is resolved, reply confirming it’s fixed and thank the support agent. This closes the ticket properly and provides positive feedback. If applicable, briefly describe what solved it for documentation purposes and to help others with similar issues.
Escalating Issues
If initial support interactions don’t resolve your issue or you’re unsatisfied with responses, you can escalate appropriately.
Request escalation: Politely ask for your ticket to be escalated to senior support or development team if:
- The issue persists after trying all suggested solutions
- You believe you’ve discovered a bug that developers should investigate
- The issue is urgent and affecting your production site significantly
- Responses seem to be generic/automated rather than addressing your specific situation
When requesting escalation, summarize the ticket history: “I’ve been working with support for two weeks, tried solutions A, B, and C as suggested, but the issue persists. This appears to be a bug affecting [specific scenario]. Could this be escalated to the development team for investigation?”
Refund requests: If DigiConsent doesn’t meet your needs or advertised functionality doesn’t work, contact support about refund policies. Most reputable plugins offer satisfaction guarantees within certain timeframes. Approach refund requests professionally, explaining specifically why the plugin doesn’t meet your needs.
Reporting Bugs Effectively
If you believe you’ve found a bug, report it comprehensively to help developers fix it quickly.
Verify it’s actually a bug: Before reporting, confirm the behavior is genuinely wrong, not a misunderstanding of how features work. Review documentation to ensure expected behavior matches reality. Test with all other plugins disabled and a default theme to rule out conflicts.
Reproduce consistently: Document exact steps that reproduce the bug 100% of the time. If the bug only happens occasionally or unpredictably, note the conditions when it appears. Inconsistent bugs are harder to fix but should still be reported with as much context as possible about when they occur.
Minimal reproduction case: If possible, reproduce the bug in the simplest environment—fresh WordPress installation, only DigiConsent active, default theme. This proves the bug is in DigiConsent itself rather than interactions with your specific setup. If you can only reproduce it with certain other plugins active, note which plugins are necessary for reproduction.
Bug report template:
- Bug description: What’s wrong in one sentence
- Steps to reproduce: Numbered step-by-step reproduction instructions
- Expected behavior: What should happen
- Actual behavior: What happens instead
- Environment: System information (versions, hosting, etc.)
- Error messages: Complete error text and screenshots
- Frequency: Always happens, sometimes happens (estimate %), only in specific conditions
Being a Great Support Customer
Good communication and professional interactions lead to better support experiences.
Be patient: Support teams handle many requests. Response times vary based on support tier, time zones, and ticket volume. Don’t submit duplicate tickets—this slows down response times for everyone.
Be respectful: Support agents are people trying to help you. Frustrated users sometimes take out frustration on support staff. Remember that agents didn’t create the bug or issue—they’re there to help solve it. Politeness and respect lead to better, more motivated support.
Be detailed: As covered throughout this article, detailed information saves time and leads to faster resolution. Take the extra 10 minutes to write a comprehensive initial request rather than exchanging days of follow-up messages gathering information piecemeal.
Learn and improve: Pay attention to solutions support provides. If similar issues arise later, you’ll know how to resolve them yourself. This makes you more self-sufficient and reduces your dependency on support for repeat issues.
Contribute back: If you discover solutions to problems, consider sharing them in community forums or contributing to documentation. This helps other users and reduces support burden, leading to better support for everyone.
Self-Service Resources
Maximize self-service resources before contacting support. This gets you faster answers and reserves support capacity for complex issues that truly require expert assistance.
Search documentation thoroughly: Use documentation search features with various keywords. If searching for “banner not showing” doesn’t yield results, try “banner invisible,” “banner missing,” or “display problems.” Different phrasings reveal different articles.
Check version changelogs: If issues started after an update, review the changelog for that version. Sometimes known issues are documented with workarounds. Changelogs also explain breaking changes that might require configuration updates.
Community resources: Search general WordPress forums, Stack Overflow, or web development communities for solutions. Many WordPress issues have common solutions documented broadly beyond plugin-specific documentation.
Video tutorials: If available, watch video tutorials showing configuration and troubleshooting. Visual demonstrations often clarify steps that text descriptions don’t convey as clearly.
Effective support interactions are partnerships between you and the support team. By providing comprehensive diagnostic information, communicating clearly, following up responsively, and approaching interactions professionally, you ensure quick resolution to issues and build positive relationships with the team maintaining the software your site depends on. Support is there to help you succeed—make the most of it by being an informed, prepared, and collaborative customer.