Overview #
Every plan includes access to our support team. This article explains the channels available, the response times you can expect per plan, and how to get the fastest possible resolution.
How to Reach Us #
| Channel | Use for | Available on |
|---|---|---|
| Email ticket: su*****@********co.za | All requests and questions | All plans |
| Contact Us form (inside your Xpulse dashboard) | General questions and support, without leaving WordPress | All plans |
| Xvault request system | Plugin activation requests (inside your WordPress admin) | X2, X3, X4-X6 |
| Dedicated channel (WhatsApp/Slack + phone) | Urgent issues and direct line to your account team | X4-X6 (dedicated) |
Response Times by Plan #
Response time means first human response: the time until a support engineer acknowledges your ticket, not necessarily full resolution. We’ll always confirm the fix or the next step within this window.
| Plan | Uptime target | First response | Site-down response |
|---|---|---|---|
| X1 | Best effort | Next business day | Next business day |
| X2 | 99.5% | Next business day | Next business day |
| X3 | 99.9% | Same day (within 8 hours) | 4 hours |
| X4-X6 (dedicated) | 99.9%+ | 4 hours | 30 minutes |
Target Stack vs. External Plugins #
Target Stack plugins (Elementor Pro, JetEngine, Fluent Forms, FluentCRM, and the rest of the Xponent Stack) are fully licensed by Xponent and receive priority support: we own the configuration, the license, and the troubleshooting.
Plugins outside the Target Stack (alternative builders, or plugins you’ve requested that aren’t in our stack) are supported on a best-effort basis. Response times may take longer, because we need to test and validate third-party tools against our managed environment before making changes. You’re welcome to use them: just expect extended turnaround.
What to Include in Your Ticket #
To get the fastest response, include:
- Your site URL
- What you were doing when the issue occurred
- What you expected vs. what actually happened
- Any error messages (screenshot or text)
- When it started: is it new, or has it always been this way?
What Response Time Does NOT Cover #
- Custom development or new feature work (quoted separately)
- Issues caused by plugins outside the Target Stack (best-effort)
- Content creation, copywriting, or design work