> ## Documentation Index
> Fetch the complete documentation index at: https://docs.digifist.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Gather Context Before Contacting Support
> What to capture from the Galantis dashboard before opening a support ticket — the information that turns a 'something is broken' message into a fix in the same day.
Most issues that aren't resolved by the troubleshooting guides become a support ticket. The single biggest factor in how fast that ticket gets resolved is the **context you include**. A ticket with a clear reproduction path, the right identifiers, and the visible error message gets triaged immediately; a ticket that just says "messages aren't sending" sits in a queue while we ask the same follow-up questions back.
This page is the checklist of what to capture before you hit Send on the support form.
## The five things every ticket should have
The full URL of your Galantis dashboard (`https://app.galantis.com/` or similar). This identifies which account is affected.
"Campaigns → Send" or "Automations → New Order trigger" — not just "messaging." The more specific, the faster we find it.
The exact sequence of clicks that triggers the issue. If it's intermittent, note how often it happens.
Copy-paste the exact text Galantis shows you. Screenshots are perfect for this — capture both the error and the screen state.
When did it happen? Include your timezone. We use this to locate the relevant operation on our side.
What did you expect to happen, and what happened instead? This often surfaces miscommunications faster than the error message.
## Where to find each piece of context
### Workspace URL
Your workspace URL is in your browser address bar when you're logged into Galantis. The full URL — not just `app.galantis.com` — uniquely identifies your account.
### Feature and action
Be specific about the Galantis section and the specific action:
* ✅ "Campaigns → 'Summer Sale 2026' campaign → Send button"
* ✅ "Automations → 'Abandoned Cart' → New customer not being enrolled"
* ✅ "Inbox → Reply not delivered to customer Maria Santos"
* ❌ "Sending doesn't work"
* ❌ "Automation broken"
### Reproduction steps
Walk through the exact actions that reliably trigger the issue. Numbered steps work best:
> 1. Open Campaigns
> 2. Click "Summer Sale 2026"
> 3. Click "Send"
> 4. Confirmation dialog appears, click "Confirm"
> 5. Error appears: "Send failed, please try again"
If the issue is intermittent (happens sometimes), note that explicitly: "This succeeded the first 4 times today, failed on attempts 5 and 6 about 2 minutes apart."
### Error messages
Capture exactly what Galantis shows you:
* **Inline error banners** — the red/yellow text at the top of a page
* **Toast notifications** — the temporary pop-ups in the corner
* **Per-record errors** — failure reasons shown next to a specific message, customer, or template
* **Browser console errors** (only if support asks for these specifically — see [Browser console errors](#when-support-asks-for-browser-console-errors))
A screenshot of the error in context is more valuable than a text description. Most browsers can take screenshots with `Cmd+Shift+4` (Mac) or `Win+Shift+S` (Windows).
### Timestamps and timezone
Note when the issue happened, including your timezone:
* "2026-05-12 14:23 (Europe/Brussels)"
* "About 10 minutes ago, around 4:15 PM ET"
For repeated failures, the timing of the first occurrence matters — that's when we look for the originating event.
### Expected vs actual
Two short lines, side by side:
> **Expected:** Campaign sends to all 1,247 opted-in customers, status moves to "Sent."
>
> **Actual:** Campaign moves to "Sending" but stops at 312 messages, status stuck on "Sending" for 20 minutes.
This format catches misunderstandings about how a feature is supposed to work — sometimes "broken" turns out to be "working as designed but unexpectedly."
## Quick diagnostics you can run first
Before opening a ticket, three checks resolve a surprising share of issues:
Many message failures trace back to the customer record itself. Open **Audience → Contacts → \[Customer Name]** and verify:
* **Consent status** — is it Subscribed? Customers in other states are correctly blocked from marketing sends.
* **Phone number** — is it in full international format (with `+` and country code)? Numbers without a country code can't be delivered.
* **Recent message history** — does the most recent send show a failure reason?
For campaign or automation issues: open **Templates → \[Template Name]** and confirm the template status is **Approved**. Templates in Pending, Rejected, or Paused state cannot send. See [Template Rejection](/galantis/whatsapp/support/troubleshooting/template-rejection) if it's Rejected.
Open **Settings → WhatsApp Connection** and confirm your WhatsApp Business Account shows as connected with a valid phone number. If you see "Reconnect" or an error state, that's likely the root cause — see [Connect WhatsApp](/galantis/whatsapp/getting-started/whatsapp-connection).
Open **Billing → Usage**. If your Conversation credits are at or near zero, that explains any current send failures. Top up or upgrade your plan — see [Billing overview](/galantis/whatsapp/billing/overview).
If any of these checks identifies the issue, the [troubleshooting guides](#related-guides) cover the resolution. If everything looks fine and the issue persists, it's time for a support ticket — with all the context above included.
## When support asks for browser console errors
For widget display issues or unusual UI behavior, support may ask you to capture browser console errors. These help us diagnose issues that happen client-side (in your browser) rather than server-side.
Visit your live store URL (e.g. `https://your-store.com`) — not the Shopify theme editor preview, which doesn't run third-party scripts.
Press `F12` (Windows/Linux), `Cmd+Option+I` (Mac), or right-click → Inspect.
The Console tab shows runtime messages and errors. Reload the page.
Take a screenshot of the Console with the errors visible, or copy the error text. Include the URL of the page where the errors appeared.
## A complete ticket template
If you'd like a template to fill in before opening a ticket:
```
Workspace: https://app.galantis.com/
Feature: Campaigns → "Summer Sale 2026"
Action: Click Send
When: 2026-05-12 14:23 (Europe/Brussels)
Steps to reproduce:
1. Open Campaigns
2. Click "Summer Sale 2026"
3. Click "Send"
4. Confirm in the dialog
5. Error: "Send failed, please try again"
Expected: Campaign sends to all 1,247 opted-in customers.
Actual: Error appears, no messages are dispatched.
Already checked:
- Customer consent statuses look correct
- Template "summer-sale-promo" shows Approved
- WhatsApp connection is healthy
- Credit balance: 5,200 (sufficient for the send)
Screenshot attached.
```
A ticket like this gets resolved fastest. The more of the five context items you include, the less back-and-forth between you and support.
## Related guides
* [Support](/galantis/whatsapp/support) — Contact channels, response times, and escalation process
* [Message Delivery](/galantis/whatsapp/support/troubleshooting/message-delivery) — Common delivery error types and their resolution
* [Catalog Sync Errors](/galantis/whatsapp/support/troubleshooting/catalog-sync-errors) — Resolving Catalog sync failures
* [Template Rejection](/galantis/whatsapp/support/troubleshooting/template-rejection) — Why templates get rejected and how to resubmit
* [Widget Not Displaying](/galantis/whatsapp/support/troubleshooting/widget-not-displaying) — Storefront widget troubleshooting