How to Get Help — Tickets, AI Assistant, and Live Chat

iWebVault offers several ways to get help — and picking the right one for your situation gets you a faster answer. AI assistant handles common questions instantly any time of day. Live chat (Mon-Fri business hours) is for real-time conversations. Tickets are for anything technical, anything requiring server-side investigation, or anything outside chat hours. This guide explains when each channel is the right choice and how to write effective requests.

The three channels at a glance

When to use the AI assistant

The AI assistant on iwebvault.com and at auth.iwebvault.com can answer most general questions immediately:

• “How do I add an email account in cPanel?”
• “What’s the SSH port?”
• “How long does DNS propagation take?”
• “Where do I find my invoices?”
• “Can I use Cloudflare with my plan?”

For these, the AI gives an instant answer drawing from our knowledge base and documentation. If the AI’s answer is incomplete or doesn’t match your situation, escalate to a human channel.

When to use live chat

Available Mon-Fri during business hours. Good for:

• Pre-sales questions (“Will this plan work for my use case?”).
• Quick account questions (“Is my payment received?”).
• Clarifications on responses you’ve already gotten.
• Things that benefit from quick back-and-forth.

Live chat isn’t ideal for technical issues that need server-side investigation — those route to tickets either way. Skip chat and submit a ticket directly when you’ve already got error logs or specific technical detail to share.

When to submit a ticket

Almost any technical issue. Tickets are the right tool for:

• Anything that needs server-side investigation (mail issues, IP blocks, server resource concerns).
• Setup tasks requiring backend access (PTR records, custom firewall rules, account-level configuration).
• Abuse-related issues (DMCA responses, account suspension discussions).
• Complex troubleshooting where you need a thread of conversation.
• Anything you want documented in writing.
• Anything during off-hours (chat is offline; tickets are 24/7).

Submit at auth.iwebvault.com/submitticket.php.

Writing a ticket that gets fast resolution

The difference between a 5-minute resolution and a 5-message back-and-forth is the information in your first message. Include:

1. What you’re trying to do

“I’m trying to send a test email from my domain to my Gmail” beats “email isn’t working”. The goal frames everything else.

2. What’s actually happening

“The email arrives in spam folder with this header: …” or “The email never arrives, sender’s mail log shows: …” — concrete observations beat vague ones.

3. Exact error messages

Copy-paste the exact text. “It says permission denied” is less useful than “Permission denied (publickey,gssapi-keyex,gssapi-with-mic).”

4. What you’ve already tried

“I’ve already verified DNS is propagated and disabled the Cloudflare proxy” saves us from suggesting things you’ve ruled out.

5. Relevant identifying info

• Domain name affected.
• cPanel/DA username.
• Server IP (for VPS/dedicated).
• Time/date of the issue (if intermittent).

Tickets submitted from your client area account already have your account info attached — but include the specific domain affected if your account has multiple.

Example: a well-written ticket

Subject: Email from contact form failing to arrive at customer’s Gmail

Body:

I have a contact form on yourdomain.com submitting through PHP mail() to contact@yourdomain.com (mailbox on same server). The mailbox does receive the messages successfully. The issue is when the form ALSO tries to send an auto-confirmation to the visitor’s Gmail address.

Track Delivery for the destination Gmail shows: “Failure – 550-5.7.26 This message does not pass authentication checks (SPF and DKIM both do not pass).”

I’ve checked Email Deliverability — SPF and DKIM both show green for yourdomain.com. But it occurred to me the contact form sends “From: visitor’s email”, not from yourdomain.com — could that be why?

Domain: yourdomain.com. Affected since: yesterday morning, started after I updated the contact form plugin.

That ticket has goal, error, hypothesis, context, and time. Average resolution time: one reply.

After submitting

• Check your email. Replies are emailed to the address on your account.
• View tickets in client area: Support → My Tickets for full thread history.
• Reply via email or via client area — both update the thread.
• Don’t open a new ticket for follow-ups on the same issue — reply to the existing one. New tickets break context.

Ticket departments / priorities

When submitting:

• Department: pick the closest match. Technical Support for hosting issues; Billing for invoices/payments; Sales for pre-purchase questions; Abuse for ToS-related matters.
• Priority: be honest. “Server is down” is High. “I have a styling question on my WP theme” isn’t.

Setting everything to “Critical” makes the priority field meaningless and slows real emergencies. Reserve high priorities for actually high-impact issues (site down, mail down for the whole domain, billing issue blocking access).

Common support questions

“How long until I get a response?” Most tickets get a first response within an hour, often much faster. Complex issues may take longer for full resolution but you’ll get an acknowledgment that we’re working on it.

“Can I call?” Not currently — text-based support gets the issue documented and traceable. For most hosting issues, text channels are also more efficient than phone (we need to see configs, logs, error messages).

“My ticket was marked ‘closed’ but my issue isn’t fully resolved.” Reply to it — closed tickets reopen automatically on customer reply.

“I forgot my client area password.” Use the reset link on the login page; check spam folder for the reset email. If you’ve lost access to the email on file too, open a ticket from any other email — we verify identity through alternate means.

“Can someone screen-share with me?” For complex setup walkthroughs, occasionally — but most issues are faster in writing. We rarely need real-time visual.

When you need a contact at a specific company (not iWebVault)

If your issue involves a third-party service, sometimes the right resolution is contacting them directly:

• Cloudflare issues — Cloudflare’s own support, dashboard.
• Domain registrar problems — your registrar (if not iWebVault).
• External mail relay issues — the relay provider (SendGrid, Mailgun, etc.).
• WordPress plugin bugs — the plugin author.

We can help diagnose where the issue is, but resolution of third-party issues requires the third party.

What’s next

• Knowing where to look first: Client area tour.
• Reading errors yourself: Mail logs, DNS troubleshooting.
• Self-serve documentation: Knowledge base.

The best support interaction is one that ends quickly with the right answer. Both sides benefit from clear, complete information up front. Write tickets the way you’d want to receive them — context first, observations second, hypotheses last — and resolution is usually a single reply away.