AfterCheck support
Email AfterCheck support
Send us the workspace, issue type, what happened, and any support-safe request or webhook IDs. We will use your message to help troubleshoot your workspace, billing, feedback links, or integrations.
AfterCheck does not include a ticket portal or service-level agreement yet. Do not include passwords, API keys, payment card details, third-party access tokens, or private customer data.
Contact support
Use this intake for normal setup and operational help.
Your email app will open with a short checklist for the context support needs.
Choose an issue category
Include the closest category in your email so support can route the request and check the right workspace, billing, feedback, or integration context.
Login or account access
Sign-in, email codes, profile setup, workspace access, and account details.
Billing or plan
Plan questions, billing status, payment support, receipts, and Customer Portal access.
Feedback link problem
A campaign or tracked request link is expired, unavailable, opening oddly, or not recording as expected.
Campaigns or requests
Campaign setup, tracked requests, imports, request email, branding, or public pages.
Responses or follow-up
Feedback inbox, follow-up status, notes, exports, analytics, or response visibility.
Shopify private beta
Private-beta Shopify connection, order sync, webhook delivery, or sync questions.
API keys or webhooks
API keys, lost key recovery, API request IDs, webhook endpoints, delivery IDs, or Zapier setup.
Team access
Invites, roles, permissions, seats, or someone not seeing the right workspace.
Something else
Anything else that does not fit the categories above.
What to include
Good context helps narrow down import failures, email delivery questions, API errors, and webhook delivery issues faster.
- Workspace or organization name
- Account email
- Issue type
- Page URL or feature area where the issue happened
- Relevant link, request ID, import ID, webhook endpoint ID, webhook delivery ID, or API request ID when available
- What you expected to happen and what happened instead
- A screenshot only if it does not show private customer data or secrets
Keep secrets out of support
Do not send API key secrets, webhook signing secrets, third-party access tokens, payment card details, customer lists, or full exported files unless a secure support process is explicitly arranged.
Use the right contact for sensitive requests
Most setup and workflow questions should go to support. Use these addresses only when the request belongs to a more specific lane.
Billing and payments
Use for plan, invoice, payment, and Customer Portal questions.
Security reports
Use for vulnerabilities, suspicious access, or security concerns.
Abuse reports
Use for misuse, abusive feedback links, or abuse reports.
Legal and privacy
Use for privacy requests, terms questions, and formal notices.